[Env]
$ snap list maas
Name Version Rev Tracking Publisher Notes
maas 3.4.1-14343-g.a552d2522 34087 3.4/stable canonical✓
[Definition]
The customization image: it’s a preinstallation format that includes partition layout, EFI boot assets, kernel, and the rootfs.
[Full question]
How to deploy a customization preinstallation image to the x86 device and keep any settings from the image? Only some configurations to sync the status with the MAAS server can be added. Is it possible?
[Problems]
-
We try to import the image with ddxz type, but the deployment process (PXE boot) shows the shim signature error (secure-boot is enabled) or magic number error (secure-boot is disabled).
- Looks like the image’s original boot assets are destroyed after the image is imported to the MAAS.
- Could the image importing process keep the original boot assets and make Curtin just deploy them to the device?
-
We also try to only import our rootfs with txz type
-
The boot assets are deployed by curtin and boot up to rootfs correctly.
-
However, we found the rootfs forced to add some cloud-init configurations after the rootfs is imported to MAAS.
- For example, we already land a specific kernel into the image, no need to install a generic kernel by cloud-init again.
- Another example is we already configured a user account into the rootfs, but the account was destroyed by MAAS. Looks like the MAAS make system only can log in by SSH key.
-
Therefore, could we make MAAS skip to add any extra cloud-init configuration?
Because we already put the necessary cloud-init configurations into our image.
-