414a2235e6
When we reach the storage screens on the installer, if the devices probing operation has not finished, we: * display a temporary "Probing" screen. * create an asynchronous task (a.k.a., probing task) that will eventually show the "Guide Storage" screen when the probing operation finishes. The probing task checks, when it finishes, that the screen currently visible is the "Probing" screen. This is the expectation and is true in most scenarios. But in case a different screen is visible, we skip refreshing the display. Unfortunately, sometimes, a "Progress" screen is shown for some time before the "Probing" screen appears. Consequently, we do not refresh the screen if the probing operation finishes whilst the Progress screen is visible. In order to keep the view returned by make_ui() up-to-date and make sure that the right screen is shown even if the probing operation finishes early, we use the level indirection that was implemented in make_ui. https://bugs.launchpad.net/subiquity/+bug/1968161 Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com> |
||
|---|---|---|
| .github/workflows | ||
| bin | ||
| console_conf | ||
| debian | ||
| examples | ||
| fake_deps | ||
| font | ||
| kbds | ||
| po | ||
| scripts | ||
| snap/hooks | ||
| subiquity | ||
| subiquitycore | ||
| system_setup | ||
| .flake8 | ||
| .gitignore | ||
| DESIGN.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| apt-deps.txt | ||
| autoinstall-schema.json | ||
| autoinstall-system-setup-schema.json | ||
| languagelist | ||
| requirements.txt | ||
| reserved-usernames | ||
| setup.py | ||
| snapcraft.yaml | ||
| tox.ini | ||
| users-and-groups | ||
README.md
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.
Our localization platform is Launchpad, translations are managed at https://translations.launchpad.net/ubuntu/+source/subiquity/
To update translation template in launchpad:
- update po/POTFILES.in with any new files that contain translations
- execute clean target, i.e. $ debuild -S
- dput subiquity into Ubuntu
To export and update translations in subiquity:
- Wait for new subiquity to publish
- Request fresh translation export from Launchpad at https://translations.launchpad.net/ubuntu/focal/+source/subiquity/+export
- wait for export to generate
- download, unpack, rename .po files into po directory, and commit changes
Acquire subiquity from source
git clone https://github.com/canonical/subiquity
cd subiquity && make install_deps
Testing out the installer Text-UI (TUI)
Subiquity's text UI 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/simple.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:
-
Build your change into a snap:
$ snapcraft snap --output subiquity_test.snap -
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 -
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 -
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 -
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.