Virtual Host Managers

Virtual Host Managers (VHMs) are used to gather information from a range of client types.

VHMs can be used to collect private or public cloud instances and organize them into virtualization groups. With your virtualized clients organized this way, Taskomatic collects data on the clients for display in the Uyuni{ Web UI. VHMs also allow you to use subscription matching on your virtualized clients.

You can create a VHM on your Uyuni Server, and use it to inventory available public cloud instances. You can also use a VHM to manage clusters created with Kubernetes and SUSE CaaS Platform.

For more information on using a VHM with Microsoft Azure, see client-configuration:vhm-azure.adoc. For more information on using a VHM with Amazon Web Services, see client-configuration:vhm-aws.adoc. For more information on using a VHM with Google Compute Engine, see client-configuration:vhm-gce.adoc. For more information on using a VHM with Kubernetes, see client-configuration:vhm-kubernetes.adoc.

SUSE Support and VM Zones

Public cloud providers use regions to define the physical geographic location of the datacenter providing virtual machines. For example, US-East, or Asia.

Regions are then further divided into zones. For example, the US-East region might contain zones called us-east-2a and us-east-2b, among others.

SUSE uses the zone of a virtual machine to determine the appropriate subscription to provide. If all of your VMs are provided by the same zone, you are within the terms and conditions of the 1-2 Virtual Machines subscription.

If your VMs are provided by different zones, even if they are within the same region, you might not meet the conditions of the 1-2 Virtual Machines subscription. In this case, check your subscription carefully.

For BYOS instances (bring your own subscription), all installed products are passed to the subscription matcher. If your public cloud instances are PAYG (pay as you go), their base products will be excluded from the subscription matcher counting.

The calculation about whether an instance is PAYG or BYOS is done at the time of registration or when a hardware refresh action is executed.

For more information, see or contact SUSE.