VHM and SUSE CaaS Platform
You can use a Uyuni VHM to gather instances from SUSE CaaS Platform.
The VHM allows Uyuni to obtain and report information about your virtual machines. For more information on VHMs, see client-configuration:vhm.adoc.
You can register each SUSE CaaS Platform node to Uyuni using the same method as you would a Salt client. For more information, see client-configuration:registration-overview.adoc.
We recommend that you create an activation key to associate SUSE CaaS Platform channels, and to onboard the associated nodes. For more on activation keys, see client-configuration:clients-and-activation-keys.adoc.
If you are using
cloud-init, we recommended that you use a bootstrap script in the
For more on bootstrapping, see client-configuration:registration-bootstrap.adoc.
When you have added the SUSE CaaS Platform nodes to Uyuni, the registered system will be locked automatically. When a system is locked, the Web UI shows a warning and you can schedule actions using the Web UI or the API, but the action will fail.
The locking mechanism works only with plain Salt minions (locking is not supported with salt-ssh minions).
You can enable or disable the system lock using the System Lock formula. When the system lock is disabled, all operations are permitted.
The System Lock formula is enabled automatically if SUSE CaaS Platform is detected on the node.
Updates related to Kubernetes are managed using the
For more information, see https://documentation.suse.com/suse-caasp/4/html/caasp-admin/_cluster_updates.html.
When using Salt or Uyuni (either via UI or API) on any SUSE CaaS Platform nodes:
Issuing those operations could render your SUSE CaaS Platform cluster unusable. Uyuni will not stop you from issuing these operations if the system is not locked.