DRS rules for license affinity

To save license costs, administrators may create DRS rules to ensure that VMs with a specific operating system run on a specific host.

Before you begin:

1. In Abiquo, set the operating system types of the VM templates. See Modify a VM template | Edit template advanced tab. Usually, for the latest version, select the operating system type without selecting a version.

To deploy VMs to groups based on their operating systems:

1. In a vCenter cluster, create a Cluster VM Group with the following naming convention for each operating system. Note that the osname could represent more than one version or flavor of an operating system.

   Lic_{clustername}_{osname}_VMs

   Abiquo supports the operating systems in the table at Guest operating system definition for VMware | Table of operating system types. Here are some possible examples:

   1. For Windows

      Lic_vcloudcluster_Windows_VMs

   2. For Linux

      Lic_vcloudcluster_Linux_VMs

2. On the Remote Services server, in the abiquo.properties file, create properties to map the VM operating system types to the VM clusters. The properties should have the following format

   The list of identifiers can be found in the table at Guest operating system definition for VMware | Table of operating system types. The prefixes are in the vSphere GuestOsIdentifier column for the names that are in the Abiquo operating system / osType column.

   1. To add Windows guests of all versions to a Windows group

   2. To add RHEL guests of all versions to a Rhel

   3. To add SUSE and SLES guests of all versions to a Suse group

   4. To add all Ubuntu and CentOs guests of all versions to a Linux group

3. To activate the properties, restart the Tomcat server.

Abiquo will deploy these VMs with a DRS rule to assign them to the appropriate group.

Open

vCenter cluster with VM groups