Skip to content

SME review: scope check for 16.0 Agama docs #764

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sounix000 merged 9 commits into from
Aug 26, 2026
Merged

SME review: scope check for 16.0 Agama docs #764

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
a3c143b
SME review: scope check for 16.0 Agama docs
sounix000 Aug 12, 2026
bf72380
agama: remove unsupported options in SLE 16.0 (#765)
imobachgs Aug 12, 2026
09bc00b
updated revision history
sounix000 Aug 12, 2026
a6d4556
Fixes for the SLE 16.0 release (#773)
lslezak Aug 20, 2026
537b767
Updated client-server architecture for Agama
sounix000 Aug 26, 2026
5f42655
Remove 16.1-only storage search conditions from 16.0 docs, per SME co…
sounix000 Aug 26, 2026
01622b9
Resolved comments from Ancor
sounix000 Aug 26, 2026
58f6fff
Remove file-system-label search-condition example, unsupported on 16.0
sounix000 Aug 26, 2026
672b7a3
Merge remote-tracking branch 'origin/maintenance/SLE16.0' into ssarka…
sounix000 Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 9 additions & 20 deletions articles/agama-automated-installation.asm.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,15 @@
<revhistory xml:id="agama-automated-unattended-installation">
<revision><date>2026-08-26</date>
<revdescription>
<para>
Removed the additional storage search conditions section
(<literal>filesystem</literal>, <literal>id</literal>, <literal>driver</literal>,
<literal>boss</literal>, <literal>partitions</literal>, and the
<literal>and</literal>/<literal>or</literal>/<literal>not</literal> operators), and
the example matching existing partitions by file system label: only
<literal>name</literal>, <literal>size</literal>, and partition number are supported
on &productname; 16.0.
</para>
<para>
Removed the Network Time Protocol and access configuration profile sections: they
are not supported on &productname; 16.0.
Expand All @@ -106,11 +115,6 @@
</revision>
<revision><date>2026-08-20</date>
<revdescription>
<para>
The <literal>access</literal> section's <literal>webConsole</literal> field now
correctly identifies &cockpit; as what it enables, instead of a nonexistent
&agama; Web console.
</para>
<para>
Documented enabling services from a post-installation script, including why the
script must use <literal>systemctl enable</literal> rather than
Expand All @@ -137,14 +141,6 @@
</para>
</revdescription>
</revision>
<revision><date>2026-08-19</date>
<revdescription>
<para>
The <literal>id</literal> storage search condition reference now lists every valid
partition id, along with the partition table types each one applies to.
</para>
</revdescription>
</revision>
<revision><date>2026-08-12</date>
<revdescription>
<para>
Expand All @@ -157,13 +153,6 @@
configurations that use <command>linuxrc</command> parameters.
</para>
</listitem>
<listitem>
<para>
Additional storage search conditions&mdash;file system type or label, partition
type, kernel driver, and BOSS controller&mdash;that can be combined with
<literal>and</literal>, <literal>or</literal>, and <literal>not</literal>.
</para>
</listitem>
<listitem>
<para>
Finding the values needed to configure iSCSI, DASD, and zFCP storage, such as
Expand Down
9 changes: 7 additions & 2 deletions articles/agama-autoyast-profiles.asm.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,15 @@
<merge>
<title>Using &ay; Profiles with &agama;</title>
<revhistory xml:id="agama-autoyast-profiles-history">
<revision><date>2026-08-26</date>
<revision><date>2026-08-12</date>
<revdescription>
<para>
Removed the <literal>ntp-client</literal> 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.
</para>
<para>
The <literal>ntp-client</literal> compatibility section was removed; Network Time
Protocol configuration through &ay; profiles is not supported on &productname;
16.0.
</para>
Expand Down
Binary file modified images/agama-server-client-architecture.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
132 changes: 0 additions & 132 deletions references/agama-advanced-storage-configuration.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -401,95 +401,6 @@
</screen>
</example>
</section>
<section xml:id="additional-search-conditions-agama-storage">
<title>Additional search conditions</title>
<para>
Besides matching by name, size, or partition number, a <literal>search</literal> section's
<literal>condition</literal> also accepts the following conditions. Availability depends on
the kind of device: <literal>driver</literal> and <literal>boss</literal> apply only to
<literal>drives</literal>; <literal>id</literal> applies only to <literal>partitions</literal>;
<literal>filesystem</literal> and <literal>partitions</literal> apply to
<literal>drives</literal>, <literal>partitions</literal>, and <literal>mdRaids</literal>
(except that a <literal>partitions</literal> condition on a <literal>partitions</literal>
entry does not make sense, since partitions do not themselves contain partitions).
</para>
<variablelist>
<varlistentry>
<term><literal>filesystem</literal></term>
<listitem>
<para>
Matches by the presence, type, or label of a file system. Use the shortcut string
<literal>"any"</literal> to match formatted devices, or <literal>"none"</literal> to
match unformatted ones; otherwise provide an object with <literal>type</literal> or
<literal>label</literal>.
</para>
<screen>{ "search": { "condition": { "filesystem": "any" } } }
{ "search": { "condition": { "filesystem": { "type": "xfs" } } } }
{ "search": { "condition": { "filesystem": { "label": "DATA" } } } }</screen>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>id</literal></term>
<listitem>
<para>
Matches a partition by its libstorage-ng partition id, such as <literal>esp</literal>,
<literal>bios_boot</literal>, <literal>linux</literal>, <literal>swap</literal>,
<literal>lvm</literal>, or <literal>raid</literal>.
</para>
<screen>{ "search": { "condition": { "id": "esp" } } }</screen>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>driver</literal></term>
<listitem>
<para>
Matches drives handled by the given kernel driver, as reported by
<command>hwinfo</command>. A drive can be handled by several drivers; the condition
matches if any of them is the given one.
</para>
<screen>{ "search": { "condition": { "driver": "ahci" } } }</screen>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>boss</literal></term>
<listitem>
<para>
Boolean. Whether the drive is a BOSS (Boot Optimized Storage Solution) device, a
technology introduced by Dell. Use <literal>false</literal> to match any other drive.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>partitions</literal></term>
<listitem>
<para>
Matches a drive or MD RAID by the presence or properties of its partitions. Use the
shortcut string <literal>"any"</literal> or <literal>"none"</literal> for presence
alone, or an object with <literal>any</literal>, <literal>none</literal>,
<literal>all</literal>, or <literal>count</literal> to match against a nested
condition.
</para>
<screen>{ "search": { "condition": { "partitions": "any" } } }
{ "search": { "condition": { "partitions": { "any": { "size": { "greater": "10 GiB" } } } } } }
{ "search": { "condition": { "partitions": { "count": { "min": 2, "max": 3 } } } } }</screen>
</listitem>
</varlistentry>
</variablelist>
<para>
Combine conditions with <literal>and</literal>, <literal>or</literal>, and
<literal>not</literal> operators, each taking one or more nested conditions:
</para>
<screen>{
"search": {
"condition": {
"and": [
{ "boss": false },
{ "size": { "greater": "100 GiB" } }
]
}
}
}</screen>
</section>
<section xml:id="reference-other-devices-agama-storage">
<title>Referencing other devices</title>
<para>
Expand Down Expand Up @@ -723,49 +634,6 @@
]
}
</screen>
<para>
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 <command>e2label</command> or during a prior installation), using the
<literal>filesystem</literal> search condition's <literal>label</literal> field.
</para>
<example>
<title>Deleting and shrinking of existing devices matched by file system label</title>
<screen>
"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" }
}
]
}
]
}
</screen>
</example>
<para>
When the size limits are specified as a combination of <literal>current</literal> and a fixed
value, ensure that the resulting <literal>min</literal> is not bigger than the resulting
Expand Down
52 changes: 6 additions & 46 deletions references/agama-boot-options.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -259,6 +259,12 @@ inst.dud=<replaceable>label://UPDATES/package.rpm</replaceable></screen>
<literal>inst.self_update_import_key=1</literal>, and
<literal>inst.self_update_gpg=0</literal>.
</para>
<para>
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
<literal>inst.install_url=<replaceable>http://selfupdaterepo</replaceable></literal>.
</para>
</listitem>
</varlistentry>
</variablelist>
Expand Down Expand Up @@ -304,18 +310,6 @@ live.password_dialog=1</screen>
live.password_systemd=1</screen>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>inst.remote</literal></term>
<listitem>
<para>
Available since &suselinux; 16.1. By default, the &agama; installer can be
accessed remotely from other machines or mobile devices. Set
<literal>inst.remote=0</literal> 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 <literal>systemd.mask</literal> boot option instead.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section xml:id="agama-boot-options-advanced">
Expand All @@ -332,40 +326,6 @@ live.password_systemd=1</screen>
<screen>fips=1</screen>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>inst.solver_testcase</literal></term>
<listitem>
<para>
Available since &suselinux; 16.1. By default, the dependency solver test case is
saved only on failure. Set <literal>inst.solver_testcase=1</literal> to also save it
on success, which is useful for debugging package dependency problems. Saved to
<filename>/run/agama/testcase</filename>, and included in the logs created by
<command>agama logs store</command>. If the <literal>ZYPP_FULLLOG=1</literal> boot
option is set, the solver test case is instead created automatically by
<literal>libzypp</literal> (the library behind &zypper; and &agama;'s own package
resolution) under
<filename>/var/log/YaST2/autoTestcase</filename>, and this option is ignored.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>inst.systemd_boot_preview</literal></term>
<listitem>
<note>
<title>Preview feature</title>
<para>
This is a preview feature for testing <literal>systemd-boot</literal> 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
<literal>systemd-boot</literal> support ends.
</para>
</note>
<para>
Available since &suselinux; 16.1. Set to <literal>1</literal> to enable the
<literal>systemd-boot</literal> boot loader as a preview feature.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>systemd.unit</literal></term>
<listitem>
Expand Down
40 changes: 1 addition & 39 deletions references/agama-installation-profile-details.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,18 +75,6 @@
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>mode</term>
<listitem>
<para>
Optional installation mode. Some products support more than one mode, changing how the
installed system behaves. For example, &productname; supports
<literal>standard</literal> and <literal>immutable</literal> (an immutable OS using
transactional updates). If omitted, the product uses its traditional default behavior;
it is preferred to specify the mode explicitly.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>registrationCode</term>
<listitem>
Expand Down Expand Up @@ -268,7 +256,6 @@
<filename>~/.ssh/authorized_keys</filename> file. This allows passwordless &rootuser;
login over SSH. The key must be in OpenSSH format. For example, starting with
<literal>ssh-rsa</literal> or <literal>ssh-ed25519</literal>.
<literal>sshPublicKeys</literal> is an accepted alias with identical behavior.
</para>
<para>
You can generate an SSH public key by running the following command:
Expand Down Expand Up @@ -297,8 +284,7 @@
"hashedPassword": false,
"fullName": "<replaceable>FULL_NAME</replaceable>",
"userName": "<replaceable>LOGIN_NAME</replaceable>",
"password": "<replaceable>USER_PASSWORD</replaceable>",
"sshPublicKey": "<replaceable>SSH_PUBLIC_KEY</replaceable>"
"password": "<replaceable>USER_PASSWORD</replaceable>"
}
</screen>
</example>
Expand Down Expand Up @@ -344,18 +330,6 @@
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>sshPublicKey</term>
<listitem>
<para>
An optional SSH public key, or list of keys, to be added to the user's
<filename>~/.ssh/authorized_keys</filename> file, in the same format as
&rootuser;'s <literal>sshPublicKey</literal> (see
<xref linkend="root-authentication-agama-installation-profile"/>).
<literal>sshPublicKeys</literal> is an accepted alias with identical behavior.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section xml:id="localization-configuration-agama-installation-profile">
Expand Down Expand Up @@ -717,17 +691,6 @@
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>updateNvram</term>
<listitem>
<para>
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 <literal>false</literal>, the NVRAM is left untouched, which is
useful for preserving an existing boot manager or specific firmware configuration.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section xml:id="network-configuration-agama-installation-profile">
Expand Down Expand Up @@ -1757,7 +1720,6 @@
"channel": "<replaceable>0.0.fb00</replaceable>",
"wwpn": "<replaceable>0x500507630300c563</replaceable>",
"lun": "<replaceable>0x4010403300000000</replaceable>",
"active": false
}
]
}
Expand Down
4 changes: 2 additions & 2 deletions references/autoyast-agama-compatibility-reference.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@
<tbody>
<row><entry><literal>append</literal></entry><entry>Supported</entry><entry><literal>bootloader.extraKernelParams</literal></entry><entry/></row>
<row><entry><literal>timeout</literal></entry><entry>Supported</entry><entry><literal>bootloader.timeout</literal></entry><entry>A negative value maps to <literal>bootloader.stopOnBootMenu: true</literal> instead.</entry></row>
<row><entry><literal>update_nvram</literal></entry><entry>Supported</entry><entry><literal>bootloader.updateNvram</literal></entry><entry/></row>
<row><entry><literal>update_nvram</literal></entry><entry>Unsupported</entry><entry/><entry/></row>
</tbody>
</tgroup>
</table>
Expand Down Expand Up @@ -587,7 +587,7 @@
<row><entry><literal>fullName</literal></entry><entry>Supported</entry><entry><literal>user.fullName</literal></entry><entry/></row>
<row><entry><literal>password</literal></entry><entry>Supported</entry><entry><literal>user.password</literal> or <literal>root.password</literal></entry><entry>Applies to whichever of <literal>user</literal> or <literal>root</literal> the entry represents.</entry></row>
<row><entry><literal>encrypted</literal></entry><entry>Supported</entry><entry><literal>user.hashedPassword</literal> or <literal>root.hashedPassword</literal></entry><entry>If set to <literal>true</literal>, &agama; uses <literal>hashedPassword</literal> instead of <literal>password</literal>.</entry></row>
<row><entry><literal>authorized_keys</literal></entry><entry>Supported</entry><entry><literal>user.sshPublicKeys</literal></entry><entry/></row>
<row><entry><literal>authorized_keys</literal></entry><entry>Supported</entry><entry><literal>root.sshPublicKey</literal></entry><entry>Applies to the <literal>root</literal> and it only considers the first value of the list.</entry></row>
</tbody>
</tgroup>
</table>
Expand Down
Loading