AutoYaST support
We know that many AutoYaST users have invested quite some time in writing their profiles to perform unattended installations. For that reason, Agama offers a mechanism to reuse such profiles to some extent.
However, Agama and AutoYaST have different features. Unlike AutoYaST, Agama is focused on the installation and delegates further configuration to other tools. From this point of view, it is clear that many of the sections in an AutoYaST profile will not have an Agama counterpart.
This document describes how AutoYaST supports work, including the limitations you might find. For a full reference of all the sections and attributes of an AutoYaST profile and their level of support in Agama, check the AutoYaST compatibility reference.
Loading an AutoYaST profile
The typical way of starting an unattended installation in Agama is by passing the URL of an AutoYaST
profile through the inst.auto
argument in the kernel's
command-line. For example:
inst.auto=http://example.net/agama/tumbleweed.xml
AutoYaST profiles can also be processed with the generate
command as explained at the working
with profiles section.
In both cases, Agama takes care of pre-processing and converting the profile to an Agama equivalent. As part of this pre-processing, it supports handling of dynamic profiles, including:
- Rules and classes.
- Embedded Ruby (ERB).
- Pre-installation scripts.
- Ask lists (not implemented yet). Note for developers: fortunately, the code to parse and run the process is there but we need to adapt the user interface, which is not trivial.