Ubuntu Server Installer, and backend for Ubuntu Desktop Installer

Go to file

Mathieu Trudel-Lapierre 9558c1a357 Update and clean up packaging to build separate binaries		2016-07-08 16:46:16 -04:00
bin	Don't filter logs at all.	2016-06-30 14:51:46 -04:00
console_conf	console_conf: make sure we're recognized as a package	2016-07-08 15:56:26 -04:00
debian	Update and clean up packaging to build separate binaries	2016-07-08 16:46:16 -04:00
examples	Update example probe data to include info from latest probert	2015-11-06 10:38:03 -06:00
installer	add check for empty loopdev to geninstaller	2016-06-22 13:30:27 -05:00
subiquitycore	Deal with the fact there may be no default route for an IP family.	2016-07-06 18:30:43 -04:00
tests	Use virtualenv to make use of urwid 1.3.0 and the asyncio library	2015-06-30 13:02:39 -04:00
.gitignore	debian: merge packaging in main subiquity tree.	2016-06-28 14:02:33 -04:00
.gitmodules	Update topdir Makefile targets	2015-09-01 10:04:24 -05:00
LICENSE	Initial commit	2015-06-08 17:57:45 -04:00
Makefile	Makefile: use xenial branch for Makefile builds	2016-07-06 18:27:26 -04:00
README.md	Add info on how to enable multiverse for UEFI support	2015-09-30 14:01:17 -05:00
firstboot.md	Change subuiquity to run as firstboot for snappy.	2016-06-22 14:19:54 -05:00
firstboot.sh	Change subuiquity to run as firstboot for snappy.	2016-06-22 14:19:54 -05:00
firstboot@.service	Merge firstboot logic into subiquity proper; make it generic enough to work for both the installer and firstboot cases.	2016-06-23 23:27:09 +03:00
requirements.txt	Switch to Tornado's event loop	2015-08-23 18:48:52 -04:00
serial-firstboot@.service	Merge firstboot logic into subiquity proper; make it generic enough to work for both the installer and firstboot cases.	2016-06-23 23:27:09 +03:00
setup.py	setup.py: update to account for subiquitycore rename	2016-07-08 15:56:50 -04:00

README.md

subiquity

Ubuntu Server Installer

Acquiring the installer from PPA

Request access to https://launchpad.net/~subiquity
View your private PPA subscriptions: https://launchpad.net/~LP_USERID/+archivesubscriptions
Select subiquity-dev
Add your private ppa

sudo apt-add-repository -y https://LPUSER:LPPASS@private-ppa.launchpad.net/subiquity/subiquity-dev/ubuntu

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 3D2F6C3B

Update apt and install subiquity

sudo apt-get update && sudo apt-get install subiquity

Enable multiverse for UEFI testing in VM

sudo apt-add-repository multiverse

Testing out the Text-UI (TUI)

SUbiquity's text UI is is available for testing without actually installing anything to a system or a VM. Subiquity developers make use of this for rapid development. After installing subiquity you can start it:

subiquity --dry-run

All of the features are present in dry-run mode. The installer will emit it's backend configuration files to /tmp/subiquity-config-* but it won't attempt to run any installer commands (which would fail without root privileges). Further, subiquity can load other machine profiles in case you want to test out the installer without having access to the machine. A few sample machine profiles are available in the package at /usr/share/subiquity/examples/ and can be loaded via the --machine parameter:

subiquity --dry-run \ --machine /usr/share/subiquity/examples/desktop.json

Generating machine profiles

Machine profiles are generated from the probert tool. This package is also available in the Subiquity PPA. To collect a machine profile:

probert --all > mymachine.json

Acquire subiquity from source

git clone https://github.com/CanonicalLtd/subiquity

cd subiquity && make install_deps

Running the UI locally in dry-run mode (no VM)

make

Running the UI locally with a different machine profile (see examples/)

MACHINE=examples/desktop.json make

Building installer image

The build system will generate a bootable image. This image can be run inside a VM, or copied to an USB disk and booted directly.

make installer

The resulting build image is avaiable at installer/installer.img The installer image requires approximately 2G of space at this time.

Running installer locally in a VM

make run

Overide default values for installer build

make RELEASE=[wily, vivid, trusty] ARCH=[amd64, i386, armf, arm64, ppc64el] installer

make RELEASE=wily ARCH=arm64 run