StealthOS/subiquity
StealthOS
/
subiquity
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: clarify cloud-init interactions

This commit is contained in:
Dan Bungert 2022-10-20 17:13:25 -06:00
parent 75e727af4f
commit 01f2dee8ce
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
documentation/autoinstall.md
View File

@ -131,6 +131,26 @@ Many keys and values correspond straightforwardly to questions the installer ask
Progress through the installer is reported via the [`reporting`](autoinstall-reference.md#reporting) system, including errors. In addition, when a fatal error occurs, the [`error-commands`](autoinstall-reference.md#error-commands) are executed and the traceback printed to the console. The server then just waits.
# Interactions between Autoinstall and Cloud-init
## Delivery of Autoinstall
Cloud-config can be used to deliver the Autoinstall data to the installation environment. The [autoinstall quickstart](autoinstall-quickstart.md) has an [example](autoinstall-quickstart.md#write-your-autoinstall-config) demonstrating this.
Note that Autoinstall is processed by Subiquity (not Cloud-init), so please direct defects in Autoinstall behavior to [Subiquity](https://bugs.launchpad.net/subiquity/+filebug).
## The installation environment
At install time, the live-server environment is just that, a live but ephemeral copy of Ubuntu Server. This means that Cloud-init is present and running in that environment, and existing methods of interacting with Cloud-init can affect the live-server. For example, if a cloud-config is presented to the live-server containing [`ssh_import_id`](https://cloudinit.readthedocs.io/en/latest/topics/modules.html?highlight=ssh#ssh-import-id), then ssh keys will be added to the authorized_keys list for the installation environment.
## First boot configuation of the target system
Autoinstall data may optionally contain a [user-data](autoinstall-reference.md#user-data) section, which is cloud-config data that is configuring the target system.
Subiquity itself delegates some configuration items to Cloud-init, and these items are processed on first boot.
Starting with Ubuntu 22.10, once Cloud-init has performed this first boot configuration, it will disable itself.
# Possible future directions
We might want to extend the 'match specs' for disks to cover other ways of selecting disks.