Ubuntu Server Installer
Clone or download
mwhudson Merge pull request #387 from sil2100/agetty-i
agetty needs an explicit -i to not to display the /etc/issue file
Latest commit ee1a7b6 Aug 5, 2018
Failed to load latest commit information.
bin use a custom console font Jun 25, 2018
console_conf make scrollbar less intrusive Jun 18, 2018
debian agetty needs an explicit -i to not to display the /etc/issue file bef… Aug 3, 2018
examples add answers file that takes the guided-lvm option Jul 7, 2018
fake_deps tox: Support running tests and flake8 in tox. Jun 5, 2018
po Drop removed file from POTFILES.in Jul 6, 2018
scripts fixup tests Jul 11, 2018
subiquity more pessimism Jul 25, 2018
subiquitycore prevent bonding of bonds Jul 22, 2018
.flake8 Make tox and Makefile more similar. Jun 6, 2018
.gitignore tox: Support running tests and flake8 in tox. Jun 5, 2018
.gitmodules Update topdir Makefile targets Sep 1, 2015
.travis.yml update travis jobs: test on cosmic, run make lint May 24, 2018
LICENSE Initial commit Jun 8, 2015
Makefile Add jsonschema dependency Jul 2, 2018
README.font.md use a custom console font Jun 25, 2018
README.md fix some lies in the README Feb 15, 2018
kbdnames.txt implement keyboard selection (#276) Feb 7, 2018
requirements.txt note new dependencies in a few places May 22, 2018
reserved-usernames do not let the user choose a reserved username Jul 16, 2018
setup.cfg Barebones i18n setup. Sep 18, 2017
setup.py fix snap build Jun 13, 2018
snapcraft.yaml do not let the user choose a reserved username Jul 16, 2018
subiquity.psf use a custom console font Jun 25, 2018
tox.ini fix snap build Jun 13, 2018
users-and-groups only add the user to groups that exist in the target system Jun 14, 2018


subiquity & console-conf

Ubuntu Server Installer & Snappy first boot experience

The repository contains the source for the new server installer (the "subiquity" part, aka "ubiquity for servers") and for the snappy first boot experience (the "console-conf" part).

We track bugs in Launchpad at https://bugs.launchpad.net/subiquity. Snappy first boot issues can also be discussed in the forum at https://forum.snapcraft.io.

Acquire subiquity from source

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

cd subiquity && make install_deps

Testing out the installer 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/mwhudson.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-server-$(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 -boot d -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.