Creating a Cluster
FlexNet Manager Suite 2019 R1 (On-Premises Edition)
A cluster of computers may affect the terms of software licensing, especially when the cluster includes virtual hosts, and there is the possibility of virtual machines moving between these hosts as part of load balancing within the cluster. To track licensing impacts, it's useful to represent your organization's physical cluster(s) within FlexNet Manager Suite. You can represent multiple hierarchies of clusters, hosts, pools, and virtual machines.
To create a cluster:
Important: Changing the type of a
cluster has an impact on license compliance calculation for the applications
installed on the virtual machines hosted on the cluster. Consider the
following outcomes of changing a cluster type:
- FlexNet Manager Suite assumes that affinity for the virtual machines in Hyper-V clusters is disabled.
- FlexNet Manager Suite considers the actual affinity-enabled values for virtual machines in vMotion clusters.
- For Hyper-V clusters, FlexNet Manager Suite does not import host affinity rules. When you change a vMotion cluster to a Hyper-V cluster, the host affinity rules are deleted.
- For vMotion clusters, FlexNet Manager Suite imports host affinity rules with cluster definition. When you change a Hyper-V cluster to a vMotion clusters, the host affinity rules are retained.