Ubuntu Server Installer, and backend for Ubuntu Desktop Installer
Go to file
Michael Hudson-Doyle a54100d85d more things you need to build probert now 2017-01-26 12:06:05 +13:00
bin more unused stuff 2017-01-26 11:18:35 +13:00
console_conf remove references to firstboot (an old name for console-conf?) 2017-01-26 11:18:03 +13:00
debian prevent system-debug@tty1 from running 2017-01-25 14:20:13 +13:00
examples fix blockdev_align_up to actually round up by 1M, not 1G 2017-01-05 14:45:14 +13:00
installer streamline installer stuff a bit 2017-01-26 11:37:34 +13:00
subiquity remove references to firstboot (an old name for console-conf?) 2017-01-26 11:18:03 +13:00
subiquitycore remove references to firstboot (an old name for console-conf?) 2017-01-26 11:18:03 +13: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 more things you need to build probert now 2017-01-26 12:06:05 +13:00
README.md streamline installer stuff a bit 2017-01-26 11:37:34 +13:00
requirements.txt and with that, we no longer depend on tornado 2017-01-18 12:02:34 +13: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

Acquire subiquity from source

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

cd subiquity && make install_deps

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 checking out subiquity you can start it:

make dryrun

All of the features are present in dry-run mode. The installer will emit its 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 repository at ./examples/ and can be loaded via the MACHINE make variable:

make dryrun MACHINE=examples/desktop.json

Generating machine profiles

Machine profiles are generated from the probert tool. To collect a machine profile:

PYTHONPATH=probert ./probert/bin/probert --all > mymachine.json

Making an install image.

To try out subiquity for real, it is necessary to make an image and run it in a VM. See installer/README.md for instructions on how to do this.