Registering Open Enterprise Server Clients

This section contains information about registering clients running Open Enterprise Server operating systems.

1. Add Software Channels

In the following section, descriptions often default to the x86_64 architecture. Replace it with other architectures if appropriate.

Before you register Open Enterprise Server clients to your Uyuni Server, you need to add the required software channels, and synchronize them.

The products you need for this procedure are:

Table 1. OES Products - WebUI
OS Version Product Name

Open Enterprise Server 24.4

Open Enterprise Server 24.4 x86_64

Open Enterprise Server 23.4

Open Enterprise Server 23.4 x86_64
Procedure: Adding Software Channels

  1. In the Uyuni Web UI, navigate to Admin  Setup Wizard  Products.

  2. Locate the appropriate products for your client operating system and architecture using the search bar, and check the appropriate product. This will automatically check all mandatory channels. Also all recommended channels are checked as long as the include recommended toggle is turned on. Click the arrow to see the complete list of related products, and ensure that any extra products you require are checked.

  3. Click Add Products and wait until the products have finished synchronizing.

Alternatively, you can add channels at the command prompt. The channels you need for this procedure are:

Table 2. OES Products - CLI
OS Version Base Channel Name

Open Enterprise Server 24.4

oes24.4-pool-x86_64

OES24.4-Pool for x86_64

Open Enterprise Server 23.4

oes23.4-pool-x86_64"

OES23.4-Pool for x86_64

To find channel names of older products, at the command prompt on the Uyuni Server, as root, use the mgr-sync command:

mgr-sync list --help

Then specify the argument you are interested in. For example, channels:

mgr-sync list channels [-c]
Procedure: Adding Software Channels at the Command Prompt

  1. At the command prompt on the Uyuni Server, as root, use the mgr-sync command to add the appropriate channels:

    mgr-sync add channel <channel_label_1>
mgr-sync add channel <channel_label_2>
mgr-sync add channel <channel_label_n>

  2. Synchronization starts automatically. If you want to synchronize the channels manually, use:

    mgr-sync sync --with-children <channel_name>

  3. Ensure the synchronization is complete before continuing.

To add the client tools, add these channels from the command prompt:

Table 3. Open Enterprise Channels - CLI
OS Version Client Channel Updates

Open Enterprise Server 24.4

oes24.4-sle-manager-tools15-pool-x86_64

oes24.4-sle-manager-tools15-updates-x86_64

Open Enterprise Server 23.4

oes23.4-sle-manager-tools15-pool-x86_64

oes23.4-sle-manager-tools15-updates-x86_64
Procedure: Adding Software Channels at the Command Prompt

  1. 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>

  2. If automatic synchronization is turned off, synchronize the channels:

    spacewalk-repo-sync -p <base_channel_label>

  3. Ensure the synchronization is complete before continuing.

2. Check Synchronization Status

Procedure: Checking Synchronization Progress From the Web UI

  1. In the Uyuni Web UI, navigate to Software  Manage  Channels, then click the channel associated to the repository.

  2. Navigate to the Repositories tab, then click Sync and check Sync Status.

Procedure: Checking Synchronization Progress From the Command Prompt

  1. 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

  2. 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.

SUSE Linux Enterprise 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.