2.5 KiB
Further configuration
TL;DR Agama will support running post-installation scripts after the first boot. No specific support for a CMS1, Combustion/Ignition, etc.
It is rather typical that users want to perform some additional configuration steps once the installation is finished. To cover those use cases, AutoYaST offers support for running user-defined scripts and the YaST2 Configuration Management module.
But what are the plans for Agama? This document describes Agama's take on this topic, including the rationale behind the decision.
Using user-defined scripts
Enabling users to run their own scripts is the minimal Agama could do. With that support, a user can decide what to do with them. Actually, SUMA and many customers already follow this approach with AutoYaST.
Furthermore, it looks like a must if we want to offer a good level of backward compatibility with
AutoYaST. However, whether we should unify the post-installation and init-scripts into a single
type of scripts is debatable.
Setting up a CMS
The YaST2 Configuration Management module can set up the system to connect to a CMS. It even supports Salt parametrizable formulas since 2017. However, we have the impression that no one uses them in the context of AutoYaST.
As this set up can be achieved by using a user-defined script, we will not implement specific support for any CMS (at least by now).
Using Combustion/Ignition
openSUSE MicroOS images rely on Combustion (or Ignition) to perform additional configuration steps, so we considered to use it in Agama too. However, you cannot use the root file system to provide the Combustion scripts (and additional assets). You need to provide an additional source (a URL, a USB stick, or specific QEMU and VirtualBox mechanisms).
For that reason, Agama will not rely on Combustion by now.
References
-
Configuration Management System ↩︎