Registering openSUSE Leap Clients
This section contains information about registering clients running openSUSE operating systems. Uyuni supports openSUSE Leap 15 clients using Salt.
Bootstrapping is supported for starting openSUSE clients and performing initial state runs such as setting repositories and performing profile updates.
1. Add Software Channels
Before you register openSUSE clients to your Uyuni Server, you need to add the required software channels, and synchronize them.
The architectures currently supported are: x86_64
and aarch64
.
For full list of supported products and architectures, see Supported Clients and Features.
In the following section, descriptions often default to the |
For example, when working with x86_64
architecture, you need this product:
OS Version |
openSUSE Leap 15.6 |
openSUSE Leap 15.5 |
openSUSE Leap 15.4 |
Base Channel |
opensuse_leap15_6 |
opensuse_leap15_5 |
opensuse_leap15_4 |
Client Channel |
opensuse_leap15_6-uyuni-client |
opensuse_leap15_5-uyuni-client |
opensuse_leap15_4-uyuni-client |
Updates Channel |
opensuse_leap15_6-updates |
opensuse_leap15_5-updates |
opensuse_leap15_4-updates |
Non-OSS Channel |
opensuse_leap15_6-non-oss |
opensuse_leap15_5-non-oss |
opensuse_leap15_4-non-oss |
Non-OSS Updates Channel |
opensuse_leap15_6-non-oss-updates |
opensuse_leap15_5-non-oss-updates |
opensuse_leap15_4-non-oss-updates |
Backports Updates Channel |
opensuse_leap15_6-backports-updates |
opensuse_leap15_5-backports-updates |
opensuse_leap15_4-backports-updates |
SLE Updates Channel |
opensuse_leap15_6-sle-updates |
opensuse_leap15_5-sle-updates |
opensuse_leap15_4-sle-updates |
-
At the command prompt on the Uyuni Server, as root, use the
spacewalk-common-channels
command to add the appropriate channels:spacewalk-common-channels \ <base_channel_label> \ <child_channel_label_1> \ <child_channel_label_2> \ ... <child_channel_label_n>
-
If automatic synchronization is turned off, synchronize the channels:
spacewalk-repo-sync -p <base_channel_label>
-
Ensure the synchronization is complete before continuing.
2. Check Synchronization Status
-
In the Uyuni Web UI, navigate to
, then click the channel associated to the repository. -
Navigate to the
Repositories
tab, then clickSync
and checkSync Status
.
-
At the command prompt on the Uyuni Server, as root, use the
tail
command to check the synchronization log file:tail -f /var/log/rhn/reposync/<channel-label>.log
-
Each child channel generates its own log during the synchronization progress. You need to check all the base and child channel log files to be sure that the synchronization is complete.
openSUSE channels can be very large. Synchronization can sometimes take several hours. |
3. Manage GPG Keys
Clients use GPG keys to check the authenticity of software packages before they are installed. Only trusted software can be installed on clients.
Trusting a GPG key is important for security on clients. It is the task of the administrator to decide which keys are needed and can be trusted. Because a software channel cannot be used when the GPG key is not trusted, the decision of assigning a channel to a client depends on the decision of trusting the key. |
For more information about GPG keys, see GPG Keys.
4. Register Clients
To register your clients, you need a bootstrap repository. By default, bootstrap repositories are automatically created, and regenerated daily for all synchronized products. You can manually create the bootstrap repository from the command prompt, using this command:
mgr-create-bootstrap-repo
For more information on registering your clients, see Client Registration.