Scripting Support in Auto Installation #990
Replies: 6 comments 2 replies
-
I like the approach (we do not need explicit support for scripts) and I see you have covered all the prominent use cases. Thanks! However, I have a few comments. The Additionally, we should also protect the user from doing stupid things like:
I would like to propose something slightly different, but I do not have a strong opinion:
|
Beta Was this translation helpful? Give feedback.
-
Not at all, because
Yes, at some point we should allow installing packages through the profile. |
Beta Was this translation helpful? Give feedback.
-
ok, this part I should write more clear. It means do installation to deploy step. So it do everything before what is not yet done. So according to my proposal it should be possible to write agama install --partitioning
# scripting to modify partitioned system
agama install --deploy
# scripting to modify installed and configured system
agama install # to finish installation
|
Beta Was this translation helpful? Give feedback.
-
OK, now I understand that deploy "continues" or "finishes" the installation. Putting aside the discussion about better wording (you know, naming things is harder :-) ) the overall approach looks good to me. |
Beta Was this translation helpful? Give feedback.
-
Hi guys! After reading all the comments above, from a dummy user POV I found all the proposals confusing. You can argue that CLI is not for dummies like me 😜, but just in case it can help find below my rationale. Without reading your explanations, I would have assumed that I don't know if you're following the recommendations given at https://clig.dev. I haven't read it yet. But in any case, let me suggest some things.
Of course, we can use these ugly
In both cases, it would be nice if we could change the prompt when the user is in the middle of the installation. I.e., if the user prompt is Just my two cents. |
Beta Was this translation helpful? Give feedback.
-
So final decision after discussions was that we will use just three steps - agama install --until deploy
# edit /mnt
agama install --until finish # is same as `agama install` |
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
The goal of this discussion is to discover and document use cases for additional scripting support in agama autoinstall.
Use Cases
Activation of hardware before installation
In some cases it is necessary to manually activate tricky devices before the installation starts. Examples are two network cards, one for external and one for internal network.
Changing partitioning
Sometimes there is a tricky partitioning that needs to be modified after partitioning and before installing RPMs, such as changing fstab and mounting an additional partition.
Note: not supported now ( params to install is not possible )
Modifying the system
If there is a need to modify the system before rebooting, e.g. to provide ignition/combustion config, then it must be modified before umount. Another type of changes are changes that are mandatory for successful reboot like some kernel tuning or adding some remote storage that have to be mounted during boot.
Modify the installation profile
For various reasons, jsonnet may not be able to handle all of the profile changes that users may wish to make.
Modify Software and its Configuration
Users are just to do a lot of stuff using post install scripts in autoyast e.g. to call zypper with various modifications, modify configuration files or manipulate with systemd services. It is done after initial reboot.
Agama won't handle it and delegate it to combustion/ignition for initial setup. Especially calling zypper is problematic as agama holds libzypp lock.
Beta Was this translation helpful? Give feedback.
All reactions