When you have your Uyuni Server set up, you are ready to start registering clients.
You can use Uyuni to manage clients using either the Salt stack or the traditional stack (inherited from Spacewalk). Most new features and enhancements are only available for Salt-managed clients, which makes this stack the preferred one. For more details, see Supported Clients and Features
In the Uyuni Web UI, navigate to
Make sure you use stable FQDNs for the
Host field, or Uyuni will not be able to find your host when your Public Cloud gives you a different short-lived FQDNS.
If you are attempting to bootstrap traditional clients, check that you can resolve the host name of the server while you are logged in to the client.
You might need to add the FQDN of the server to
Public cloud images usually do not allow SSH login with username and password, but only SSH with a certificate. If you want to use bootstrap from the Web UI, you will need to enable SSH login with username and password. You can do this by navigating toand changing the authentication method.
When the bootstrap process has completed successfully, your client will be listed at.
If you want more control over the process, have to register many clients, or are registering traditional clients, we recommend that you create a bootstrap script. For more information, see Register Clients with a Bootstrap Script.
For Salt clients and even more control over the process, executing single commands on the command line can be useful. For more information, see Register on the Command Line (Salt).
Activation keys are used with traditional and Salt clients to ensure that your clients have the correct software entitlements, are connecting to the appropriate channels, and are subscribed to the relevant groups. Each activation key is bound to an organization, which you can set when you create the key.
In the Uyuni Web UI, as an administrator, navigate to.
Click the Create Key button.
Activation Key Detailspage, in the
Descriptionfield, enter a name for the activation key.
Keyfield, enter the distribution and service pack associated with the key. For example,
SLES12-SP4for SUSE Linux Enterprise Server 12 SP4.
Do not use commas in the
Keyfield for any SUSE products. However, you must use commas for Red Hat Products. For more information, see Activation Keys.
Base Channelsdrop-down box, select the appropriate base software channel, and allow the relevant child channels to populate. For more information, see reference:admin/setup-wizard.adoc#vle.webui.admin.wizard.products and Custom Channels.
Select the child channels you need (for example, the mandatory SUSE Manager tools and updates channels).
We recommend you leave the
Contact Methodset to
We recommend you leave the
Universal Defaultsetting unchecked.
Click Create Activation Key to create the activation key.
Configuration File Deploymentcheck box to enable configuration management for this key, and click Update Activation Key to save this change.
For more on activation keys, see Activation Keys.
System Set Manager (SSM) is used to administrate groups of systems, rather than performing actions on one system at a time. It works for both Salt and traditional clients.
For a complete list of the tasks that you can perform with the SSM, see System Set Manager.
You need to select which systems or system group you want to work with before you can use SSM to perform operations.
You can access SSM in three different ways:
Navigate to, select systems you want to work with, and navigate to .
Navigate to, and click Use in SSM for the system group you want to work with.
Navigate to, select the group you want to work with, and click Work with Group.
For more on SSM, see Using the System Set Manager.