Register Clients to a Proxy
Proxy servers can act as a broker and package cache for both Salt and traditional clients. Registering clients to a proxy is similar to registering them directly to the Uyuni Server, with a few key differences.
These sections contain information on registering Salt clients to a proxy using the Web UI, commands on the command line, or a bootstrap script. There is also information on registering traditional clients using a bootstrap script. There are also procedure how you can move clients from one Uyuni Proxy to another one or to the Uyuni Server.
Within the Web UI, proxy pages show information about both Salt and traditional clients.
You can see a list of clients that are connected to a proxy by clicking the name of the proxy in
Proxy subtab of the
A list of chained proxies for a Salt client can be seen by clicking the name of the client in
Connection subtab of the
You can move Salt and Salt SSH push clients between proxies without the need to repeat the registration process.
You cannot move chained proxies. Instead of moving a chained proxy, create a new proxy, move the clients, and delete the old proxy.
If you want to move a traditional client between proxies, you must repeat the registration process from the beginning.
In the Uyuni Web UI, navigate to the
System Detailspage for the client you want to move between proxies.
Navigate to the
Connectiontab. Then follow the
Change proxylink to see the drop-down menu.
New Proxydrop-down menu select the proxy you want the client to move to, and click Change Proxy.
In the Uyuni Web UI, navigate toand check each client to move, this adds the clients to the system set manager.
Navigate to, and go to the `` tab.
New Proxydrop-down menu select the proxy you want the clients to move to, and click Change Proxy.
The same functionality is also available with the
system.changeProxy API call.
The effect of this function differs between normal Salt clients and Salt SSH push clients.
The function schedules a Salt state action, which modifies
master: setting in the
susemanager.conf Salt client configuration file to point to the new proxy.
Then the function restarts the Salt client.
When the minion restarts and reconnects via the new proxy, the server updates the proxy path in the database and schedules another action for refreshing the channel URLs.
The function updates the proxy path immediately in the database and new action for refreshing the channel URLs is scheduled.
If you want to move a Salt client from a proxy to the server, select
None from proxy list.
If you want to move a traditional client to the server you must repeat the registration process from the beginning.