Ubuntu Server Installer, and backend for Ubuntu Desktop Installer
Go to file
Michael Hudson-Doyle 923044be7e move Selector widget to its own file and create a class for its Options
I wanted this so I can enable/disable options after creating the widget.
2017-09-05 09:43:45 +12:00
bin fix crash on startup with no ip address 2017-03-28 15:54:50 +13:00
console_conf stop being clever in handling of escape in network screens 2017-04-05 14:36:46 +12:00
debian releasing package subiquity version 0.0.29 2017-03-29 13:10:00 +13:00
examples fix blockdev_align_up to actually round up by 1M, not 1G 2017-01-05 14:45:14 +13:00
scripts fix subquity -> subiquity typos, including in script name 2017-08-23 10:26:09 +12:00
subiquity make the initial screen a bit more comprehensible 2017-04-11 14:08:36 +12:00
subiquitycore move Selector widget to its own file and create a class for its Options 2017-09-05 09:43:45 +12: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 add another helper script 2017-08-23 10:20:44 +12: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 fix subquity -> subiquity typos, including in script name 2017-08-23 10:26:09 +12: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
snapcraft.yaml use "git" for the snap version 2017-08-22 12:19:17 +12: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

Testing changes in KVM

To try out your changes for real, it is necessary to install them into an ISO. Rather than building one from scratch, it's much easier to install your version of subiquity into the daily image. Here's how to do this:

  1. Build your change into a snap:

    $ snapcraft snap --output subiquity_test.snap
    
  2. Grab the current version of the installer:

    $ urlbase=http://cdimage.ubuntu.com/ubuntu-server/daily-live/current
    $ isoname=$(distro-info -d)-live-$(dpkg --print-architecture).iso
    $ zsync ${urlbase}/${isoname}.zsync
    
  3. Run the provided script to make a copy of the downloaded installer that has your version of subiquity:

    $ sudo ./scripts/inject-subiquity-snap.sh ${isoname} subiquity_test.snap custom.iso
    
  4. Boot the new iso in KVM:

    $ qemu-img create -f raw target.img 10G
    $ kvm -m 1024 -cdrom custom.iso -hda target.img -serial stdio
    
  5. Finally, boot the installed image:

    $ kvm -m 1024 -hda target.img -serial stdio
    

The first three steps are bundled into the script ./scripts/test-this-branch.sh.