diff --git a/articles/agama-automated-installation.asm.xml b/articles/agama-automated-installation.asm.xml index cb8835bed..3671ef3e4 100644 --- a/articles/agama-automated-installation.asm.xml +++ b/articles/agama-automated-installation.asm.xml @@ -90,6 +90,15 @@ 2026-08-26 + + Removed the additional storage search conditions section + (filesystem, id, driver, + boss, partitions, and the + and/or/not operators), and + the example matching existing partitions by file system label: only + name, size, and partition number are supported + on &productname; 16.0. + Removed the Network Time Protocol and access configuration profile sections: they are not supported on &productname; 16.0. @@ -106,11 +115,6 @@ 2026-08-20 - - 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 @@ -137,14 +141,6 @@ - 2026-08-19 - - - The id storage search condition reference now lists every valid - partition id, along with the partition table types each one applies to. - - - 2026-08-12 @@ -157,13 +153,6 @@ 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 diff --git a/articles/agama-autoyast-profiles.asm.xml b/articles/agama-autoyast-profiles.asm.xml index 8a6240580..4012016d0 100644 --- a/articles/agama-autoyast-profiles.asm.xml +++ b/articles/agama-autoyast-profiles.asm.xml @@ -51,10 +51,15 @@ Using &ay; Profiles with &agama; - 2026-08-26 + 2026-08-12 - Removed the ntp-client compatibility section: Network Time + Corrected several &ay;-to-&agama; field mappings to match the current &agama; + release, including software repositories, network interfaces, zFCP devices, and + user SSH keys. + + + The ntp-client compatibility section was removed; Network Time Protocol configuration through &ay; profiles is not supported on &productname; 16.0. diff --git a/images/agama-server-client-architecture.png b/images/agama-server-client-architecture.png index 27bab0b37..9b0e771ab 100644 Binary files a/images/agama-server-client-architecture.png and b/images/agama-server-client-architecture.png differ diff --git a/references/agama-advanced-storage-configuration.xml b/references/agama-advanced-storage-configuration.xml index a6fa115bf..4856e2513 100644 --- a/references/agama-advanced-storage-configuration.xml +++ b/references/agama-advanced-storage-configuration.xml @@ -401,95 +401,6 @@ -
- Additional search conditions - - Besides matching by name, size, or partition number, a search section's - condition also accepts the following conditions. Availability depends on - the kind of device: driver and boss apply only to - drives; id applies only to partitions; - filesystem and partitions apply to - drives, partitions, and mdRaids - (except that a partitions condition on a partitions - entry does not make sense, since partitions do not themselves contain partitions). - - - - filesystem - - - Matches by the presence, type, or label of a file system. Use the shortcut string - "any" to match formatted devices, or "none" to - match unformatted ones; otherwise provide an object with type or - label. - -{ "search": { "condition": { "filesystem": "any" } } } -{ "search": { "condition": { "filesystem": { "type": "xfs" } } } } -{ "search": { "condition": { "filesystem": { "label": "DATA" } } } } - - - - id - - - Matches a partition by its libstorage-ng partition id, such as esp, - bios_boot, linux, swap, - lvm, or raid. - -{ "search": { "condition": { "id": "esp" } } } - - - - driver - - - Matches drives handled by the given kernel driver, as reported by - hwinfo. A drive can be handled by several drivers; the condition - matches if any of them is the given one. - -{ "search": { "condition": { "driver": "ahci" } } } - - - - boss - - - Boolean. Whether the drive is a BOSS (Boot Optimized Storage Solution) device, a - technology introduced by Dell. Use false to match any other drive. - - - - - partitions - - - Matches a drive or MD RAID by the presence or properties of its partitions. Use the - shortcut string "any" or "none" for presence - alone, or an object with any, none, - all, or count to match against a nested - condition. - -{ "search": { "condition": { "partitions": "any" } } } -{ "search": { "condition": { "partitions": { "any": { "size": { "greater": "10 GiB" } } } } } } -{ "search": { "condition": { "partitions": { "count": { "min": 2, "max": 3 } } } } } - - - - - Combine conditions with and, or, and - not operators, each taking one or more nested conditions: - -{ - "search": { - "condition": { - "and": [ - { "boss": false }, - { "size": { "greater": "100 GiB" } } - ] - } - } -} -
Referencing other devices @@ -723,49 +634,6 @@ ] } - - You can use other combinations to specify how a device could be resized, if possible. The - following examples match existing partitions by their file system label (set beforehand - with a tool such as e2label or during a prior installation), using the - filesystem search condition's label field. - - - Deleting and shrinking of existing devices matched by file system label - -"storage": { - "drives": [ - { - "partitions": [ - { - "search": { - "condition": { "filesystem": { "label": "shrinkIfNeeded" } } - }, - "size": { "min": 0, "max": "current" } - }, - { - "search": { - "condition": { "filesystem": { "label": "resizeToFixedSize" } } - }, - "size": "15 GiB" - }, - { - "search": { - "condition": { "filesystem": { "label": "resizeByRange" } } - }, - "size": { "min": "10 GiB", "max": "50 GiB" } - }, - { - "search": { - "condition": { "filesystem": { "label": "growAsMuchAsPossible" } } - }, - "size": { "min": "current" } - } - ] - } - ] -} - - When the size limits are specified as a combination of current and a fixed value, ensure that the resulting min is not bigger than the resulting diff --git a/references/agama-boot-options.xml b/references/agama-boot-options.xml index bfb57f08f..acb5e3432 100644 --- a/references/agama-boot-options.xml +++ b/references/agama-boot-options.xml @@ -259,6 +259,12 @@ inst.dud=label://UPDATES/package.rpm inst.self_update_import_key=1, and inst.self_update_gpg=0. + + The self update repository is provided only for the 16.0/QU0 release, all later QU + releases have the self update disabled. But you can still apply your custom updates by + specifying the self update repository URL + inst.install_url=http://selfupdaterepo. + @@ -304,18 +310,6 @@ live.password_dialog=1 live.password_systemd=1 - - inst.remote - - - Available since &suselinux; 16.1. By default, the &agama; installer can be - accessed remotely from other machines or mobile devices. Set - inst.remote=0 to disable remote access for increased security, - restricting access to the local machine only. To disable other network services, such - as SSH, use the standard systemd.mask boot option instead. - - -
@@ -332,40 +326,6 @@ live.password_systemd=1 fips=1 - - inst.solver_testcase - - - Available since &suselinux; 16.1. By default, the dependency solver test case is - saved only on failure. Set inst.solver_testcase=1 to also save it - on success, which is useful for debugging package dependency problems. Saved to - /run/agama/testcase, and included in the logs created by - agama logs store. If the ZYPP_FULLLOG=1 boot - option is set, the solver test case is instead created automatically by - libzypp (the library behind &zypper; and &agama;'s own package - resolution) under - /var/log/YaST2/autoTestcase, and this option is ignored. - - - - - inst.systemd_boot_preview - - - Preview feature - - This is a preview feature for testing systemd-boot support. It - automatically falls back to &grub; if the system does not meet the Boot Loader - Specification (BLS) requirements, and may be removed after the testing period for - systemd-boot support ends. - - - - Available since &suselinux; 16.1. Set to 1 to enable the - systemd-boot boot loader as a preview feature. - - - systemd.unit diff --git a/references/agama-installation-profile-details.xml b/references/agama-installation-profile-details.xml index e7d69120e..3a0943d1e 100644 --- a/references/agama-installation-profile-details.xml +++ b/references/agama-installation-profile-details.xml @@ -75,18 +75,6 @@ - - mode - - - Optional installation mode. Some products support more than one mode, changing how the - installed system behaves. For example, &productname; supports - standard and immutable (an immutable OS using - transactional updates). If omitted, the product uses its traditional default behavior; - it is preferred to specify the mode explicitly. - - - registrationCode @@ -268,7 +256,6 @@ ~/.ssh/authorized_keys file. This allows passwordless &rootuser; login over SSH. The key must be in OpenSSH format. For example, starting with ssh-rsa or ssh-ed25519. - sshPublicKeys is an accepted alias with identical behavior. You can generate an SSH public key by running the following command: @@ -297,8 +284,7 @@ "hashedPassword": false, "fullName": "FULL_NAME", "userName": "LOGIN_NAME", - "password": "USER_PASSWORD", - "sshPublicKey": "SSH_PUBLIC_KEY" + "password": "USER_PASSWORD" } @@ -344,18 +330,6 @@ - - sshPublicKey - - - An optional SSH public key, or list of keys, to be added to the user's - ~/.ssh/authorized_keys file, in the same format as - &rootuser;'s sshPublicKey (see - ). - sshPublicKeys is an accepted alias with identical behavior. - - -
@@ -717,17 +691,6 @@ - - updateNvram - - - Available since &suselinux; 16.1. Optional boolean. Determines whether the - installer modifies the system's NVRAM (Non-Volatile RAM) to update the boot order or - entries. If set to false, the NVRAM is left untouched, which is - useful for preserving an existing boot manager or specific firmware configuration. - - -
@@ -1757,7 +1720,6 @@ "channel": "0.0.fb00", "wwpn": "0x500507630300c563", "lun": "0x4010403300000000", - "active": false } ] } diff --git a/references/autoyast-agama-compatibility-reference.xml b/references/autoyast-agama-compatibility-reference.xml index c6ebaf5ee..9fc43364e 100644 --- a/references/autoyast-agama-compatibility-reference.xml +++ b/references/autoyast-agama-compatibility-reference.xml @@ -153,7 +153,7 @@ appendSupportedbootloader.extraKernelParams timeoutSupportedbootloader.timeoutA negative value maps to bootloader.stopOnBootMenu: true instead. - update_nvramSupportedbootloader.updateNvram + update_nvramUnsupported @@ -587,7 +587,7 @@ fullNameSupporteduser.fullName passwordSupporteduser.password or root.passwordApplies to whichever of user or root the entry represents. encryptedSupporteduser.hashedPassword or root.hashedPasswordIf set to true, &agama; uses hashedPassword instead of password. - authorized_keysSupporteduser.sshPublicKeys + authorized_keysSupportedroot.sshPublicKeyApplies to the root and it only considers the first value of the list. diff --git a/tasks/editing-agama-profile.xml b/tasks/editing-agama-profile.xml index 253378a36..74cf81c1e 100644 --- a/tasks/editing-agama-profile.xml +++ b/tasks/editing-agama-profile.xml @@ -40,15 +40,18 @@ only surface once an unattended installation is already running. Visual Studio Code and VSCodium are the most common editors with this support. - + Editor-only, not used by the installer The $schema value is used only by the editor, for validation while you - write the profile. The &agama; installer always validates against its own embedded schema, - regardless of what $schema points to, and completely ignores this key - at installation time. + write the profile. The &agama; installer always validates against its own embedded schema. - + + The &agama; installer in version 16.0 does not accept the $schema key and + complains that the profile is not valid. You have to remove the key before using the + profile. The later versions (16.1 and later) accept the key but still ignore its value. + +
Requirements @@ -72,7 +75,7 @@ { - "$schema": "https://raw.githubusercontent.com/agama-project/agama/refs/heads/master/rust/share/profile.schema.json" + "$schema": "https://raw.githubusercontent.com/agama-project/agama/refs/heads/SLE-16/rust/agama-lib/share/profile.schema.json" } @@ -89,8 +92,7 @@ Adding a $schema key to your profile gives you validation and autocompletion while editing, catching mistakes before you start an unattended installation. - Remove or ignore this key when you actually run the installation; the installer does not - use it. + Remove this key when you actually run the installation; the installer does not use it.