This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.
Flagged that activating a zFCP LUN not already known to the system, common with storage from vendors other than IBM DS8000, could fail.
The access section's webConsole field now
correctly identifies Cockpit as what it enables, instead of a nonexistent
Agama Web console.
Documented enabling services from a post-installation script, including why the
script must use systemctl enable rather than
systemctl start inside the chroot, and the
chroot field's actual default value.
An unattended installation can now also start without an
inst.auto boot parameter, by placing the profile at one of
Agama's predefined locations.
Also corrected: the custom-scripts stages (post, not
chroot), when legacyAutoyastStorage applies
(JSON or Jsonnet profiles only), what a minimal profile actually requires (only
product and root), and how the
onlyRequired software option works (Agama tells
libzypp to skip optional dependencies, rather than deciding
itself).
The id storage search condition reference now lists every valid
partition id, along with the partition table types each one applies to.
This article now covers:
Linuxrc-compatible boot options, for adapting existing PXE or boot
configurations that use linuxrc parameters.
Additional storage search conditions—file system type or label, partition
type, kernel driver, and BOSS controller—that can be combined with
and, or, and not.
Finding the values needed to configure iSCSI, DASD, and zFCP storage, such as the initiator name and device channel.
Profiles now use the l10n section for language, keyboard, and
time zone settings instead of the deprecated localization
section.
Compatibility and usage information for reusing AutoYaST profiles with Agama is now in its own article, Using AutoYaST Profiles with Agama.
This article now covers:
Agama boot options, supported URL schemes, and the command-line interface.
How to edit an installation profile safely, convert an existing AutoYaST profile, and enable Kdump from the first boot.
What Agama does when a profile omits the storage section:
it installs to a single disk by default, retrying on another disk up to five
times if needed.
How to deliver a profile through a Driver Update Disk, alongside the
inst.auto boot parameter.
Where to find PXE boot server setup instructions for unattended network installations.
The installation profile reference and AutoYaST compatibility reference were also corrected to match the current Agama release, including several field names and command examples.
Updated links to upstream Agama documentation
Initial version