Registering clients on a public cloud
When you have your Uyuni Server set up, you are ready to start registering clients.
An instance started from an on-demand image provided by SUSE is automatically registered, and the update infrastructure and SUSE Linux Enterprise modules are activated. To use your on-demand image as a Uyuni client, you need to disable this automation before you begin.
Log in to the on-demand instance.
At the command prompt, as root, remove the registration data and repositories:
zypper rm cloud-regionsrv-client
Remove additional packages specific to your cloud provider:
zypper rm regionServiceClientConfigEC2 regionServiceCertsEC2
Google Compute Engine:
zypper rm cloud-regionsrv-client-plugin-gce regionServiceClientConfigGCE regionServiceCertsGCE
zypper rm regionServiceClientConfigAzure regionServiceCertsAzure
For instructions on registering Uyuni to SUSE Customer Center, see installation:server-setup.adoc.
In the Uyuni Web UI, navigate to
Make sure you use stable FQDNs for the
Host field, or Uyuni cannot 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 need to enable SSH login with username and SSH key. You can do this by navigating toand changing the authentication method.
If your cloud provider is Microsoft Azure, you can log in with username and password.
To do this, you need to allow the AzureUser to run commands as root without a password.
To do this, open the
/etc/sudoers.d/waagent file, and add or edit this line:
AzureUser ALL=(ALL) NOPASSWD: ALL
Allowing the AzureUser to run commands as root without a password carries a security risk. Use this method for testing only. Do not do this for production systems.
When the bootstrap process has completed successfully, your client is listed at.
If you want more control over the process, have to register many clients, or are registering traditional clients, create a bootstrap script. For more information, see client-configuration:registration-bootstrap.adoc.
For Salt clients and even more control over the process, executing single commands on the command line can be useful. For more information, see client-configuration:registration-cli.adoc.
When registering clients launched from a public cloud image (for example, AWS AMI), you need to do some additional configuration to prevent them from over-writing each other. For more information about registering clones, see administration:tshoot-registerclones.adoc.
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.
For more on activation keys, see client-configuration:activation-keys.adoc.