Registering Salt Clients
There are three possible methods for registering Salt minions. You can use a bootstrap repository, a bootstrap script, or install using the Web UI.
This section describes using a bootstrap repository.
Registering Salt clients with a bootstrap client is the same as registering traditional clients, which is described at quickstart3_chap_suma_keys_and_first_client.adoc#registering.clients.traditional. When using this method, ensure you enable the Bootstrap using Salt and activation key options in Configuration File Deployment, so that highstate is applied automatically.
For information on using the Web UI, see reference-webui-systems.adoc#ref.webui.systems.bootstrapping.
You can also use these methods to change existing traditional clients into Salt minions.
|
GPG Keys and Uyuni Client Tools
The GPG key used by Uyuni Client Tools is not trusted by default. Either update your bootstrap repository to trust the key explicitly, or use the Web UI to manually trust the key from each client. |
To register Salt clients with a bootstrap repository, you will need to have already set up a SUSE Manager tools repository, which is described in quickstart3_chap_suma_keys_and_first_client.adoc#create.tools.repository.
You will also need to have fully synchronized a base channel for clients to obtain software packages (for example: SLES12-SP4-Pool_for_x86_64).
-
On your minion as root enter the following command:
zypper ar http://FQDN.server.example.com/pub/repositories/sle/12/4/bootstrap/ \ sles12-sp4
Do not use
HTTPS. UseHTTPinstead to avoid errors. -
After adding the repository containing the necessary Salt packages execute:
zypper in salt-minion
-
Modify the minion configuration file to point to the fully qualified domain name (
FQDN) of the SUSE Manager server (master):vi /etc/salt/minion
Find and change the line:
master: salt
to:
master: FQDN.server.example.com
-
Restart the Salt minion with:
systemctl restart salt-minion
Your newly registered minion should now show up within the Web UI under .
Accept the pending key to begin management.
If you have used your hypervisor clone utility, and attempted to register the cloned Salt client, you might get this error:
We're sorry, but the system could not be found.
This is caused by the new, cloned, system having the same machine ID as an existing, registered, system. You can adjust this manually to correct the error and register the cloned system successfully.
For more information and instructions, see xref:FILENAME.adoc#bp.chapt.suma3.troubleshooting.registering.cloned.salt.systems[].