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 4 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
37 changes: 37 additions & 0 deletions articles/agama-automated-installation.asm.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,43 @@
<merge>
<title>Automated Installation Using &agama;</title>
<revhistory xml:id="agama-automated-unattended-installation">
<revision><date>2026-08-12</date>
<revdescription>
<para>
This article now covers:
</para>
<itemizedlist>
<listitem>
<para>
Linuxrc-compatible boot options, for adapting existing PXE or boot
configurations that use <command>linuxrc</command> parameters.
</para>
</listitem>
<listitem>
<para>
Additional storage search conditions&mdash;file system type or label, partition
Comment thread
sounix000 marked this conversation as resolved.
Outdated
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
the initiator name and device channel.
</para>
</listitem>
</itemizedlist>
<para>
Profiles now use the <literal>l10n</literal> section for language, keyboard, and
time zone settings instead of the deprecated <literal>localization</literal>
section.
</para>
<para>
The Network Time Protocol and access configuration profile sections are not
supported on &productname; 16.0 and have been removed from the profile reference.
</para>
</revdescription>
</revision>
<revision><date>2026-07-31</date>
<revdescription>
<para>
Expand Down
14 changes: 14 additions & 0 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,6 +51,20 @@
<merge>
<title>Using &ay; Profiles with &agama;</title>
<revhistory xml:id="agama-autoyast-profiles-history">
<revision><date>2026-08-12</date>
<revdescription>
<para>
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>
</revdescription>
</revision>
<revision><date>2026-07-31</date>
<revdescription>
<para>
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
206 changes: 1 addition & 205 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 @@ -1741,7 +1704,6 @@
"channel": "<replaceable>0.0.fb00</replaceable>",
"wwpn": "<replaceable>0x500507630300c563</replaceable>",
"lun": "<replaceable>0x4010403300000000</replaceable>",
"active": false
}
]
}
Expand Down Expand Up @@ -1793,172 +1755,6 @@
<literal>lun</literal>: the Logical Unit Number of the disk volume.
</para>
</listitem>
<listitem>
<para>
<literal>active</literal>: optional boolean to explicitly enable or disable the
disk. If a device is listed here without its controller also listed under
<literal>controllers</literal>, &agama; activates that controller automatically.
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
</section>
<section xml:id="ntp-configuration-agama-installation-profile">
<title>Network Time Protocol configuration for an &agama; installation profile</title>
<para>
Having the correct date and time during installation matters: an incorrect clock can
cause unexpected errors. The &agama; installation medium ships <literal>chrony</literal>,
which synchronizes the system clock automatically. The optional <literal>ntp</literal>
section lets you force &agama; to synchronize using specific NTP sources instead, and copies
that configuration to the installed system.
</para>
<example>
<title>Sample <literal>ntp</literal> configuration for an &agama; installation profile</title>
<screen>
"ntp": {
"sources": [
{
"type": "pool",
"address": "<replaceable>2.opensuse.pool.ntp.org</replaceable>",
"iburst": true,
"offline": false
}
]
}
</screen>
</example>
<para>
The <literal>sources</literal> list defines the systems to synchronize with. Each source
supports the following fields:
</para>
<variablelist>
<varlistentry>
<term>address</term>
<listitem>
<para>
The host name or IP address of the NTP source.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>type</term>
<listitem>
<para>
The type of NTP source:
</para>
<itemizedlist>
<listitem>
<para>
<literal>pool</literal>: a pool of NTP servers (for example,
<literal>pool.ntp.org</literal>); the pool name resolves to multiple servers and
<literal>chrony</literal> picks the best ones.
</para>
</listitem>
<listitem>
<para>
<literal>server</literal>: a specific NTP server to synchronize with.
</para>
</listitem>
<listitem>
<para>
<literal>peer</literal>: an NTP peer for symmetric (bidirectional) time exchange.
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>iburst</term>
<listitem>
<para>
Optional boolean. If <literal>true</literal>, <literal>chrony</literal> sends a burst
of packets at startup to speed up the initial synchronization. Defaults to
<literal>false</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>offline</term>
<listitem>
<para>
Optional boolean. If <literal>true</literal>, the source is initially marked offline.
Useful for sources that require network connectivity that may not be present at boot
time. Defaults to <literal>false</literal>.
</para>
</listitem>
</varlistentry>
</variablelist>
<note>
<title>Synchronizing time before &agama; starts</title>
<para>
If you need to synchronize the date and time before &agama; itself starts (for example, if
the system has no working clock), use the <literal>rd.ntp</literal> boot option instead of
the profile's <literal>ntp</literal> section.
</para>
</note>
</section>
<section xml:id="access-configuration-agama-installation-profile">
<title>Access configuration for an &agama; installation profile</title>
<para>
The <literal>access</literal> section configures how the installed system can be accessed
remotely, over SSH and the &agama; web console.
</para>
<example>
<title>Sample <literal>access</literal> configuration for an &agama; installation profile</title>
<screen>
"access": {
"ssh": "enabled",
"webConsole": "default"
}
</screen>
</example>
<para>
This section contains the following fields:
</para>
<variablelist>
<varlistentry>
<term>ssh</term>
<listitem>
<para>
Whether SSH access is enabled. If omitted, SSH access is enabled automatically when
either the <literal>user</literal> or <literal>root</literal> section defines
<literal>sshPublicKeys</literal>. Supported values:
</para>
<itemizedlist>
<listitem>
<para>
<literal>enabled</literal>: ensures SSH is accessible. Root login using a password
can still be restricted by the product's default configuration.
</para>
</listitem>
<listitem>
<para>
<literal>default</literal>: keeps the product's default behavior.
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>webConsole</term>
<listitem>
<para>
Whether access to the &agama; web console is enabled. Supported values:
</para>
<itemizedlist>
<listitem>
<para>
<literal>enabled</literal>: ensures the web console is accessible. Root login can
still be prevented by the product's default configuration.
</para>
</listitem>
<listitem>
<para>
<literal>default</literal>: keeps the product's default behavior.
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
Expand Down
Loading