Hypervisor Cluster Profiles resource associations
A hypervisor cluster profile is a logical resource that defines consistent compute, network, and storage configuration for a cluster of hypervisors. A hypervisor cluster profile enables you to import and manage a cluster of hypervisors running on servers, which support HPE Virtual Connect and managed by HPE OneView. Hypervisor Cluster profiles ensure consistent configuration across the cluster of server nodes to hypervisors, sharing workload.
Using the hypervisor cluster profiles you can manage lifecycle operations such as grow or shrink the hypervisor cluster, modify configurations, perform consistency checks, rolling updates, and conduct nondisruptive firmware updates on the server nodes.
The hypervisor cluster profile uses a server profile template to define the configurations for server nodes and hypervisors, which are a part of the hypervisor cluster. The hypervisor cluster profile orchestrates consistent configurations from the server nodes to hypervisors.
The configurations for the server nodes are derived from the configurations in the associated server profile template. You can specify shared storage volumes in the hypervisor cluster profile, and the storage volumes that are configured in the server profile template.
The network and storage configurations for the hypervisors are derived from the associated server profile template. The hypervisor network configuration defines the virtual switches and port groups. The virtual switch configuration is automatically built based on the connections in the associated server profile template and the hypervisor settings of the hypervisor cluster profile. The hypervisor storage configuration comprises the hypervisor cluster volumes, and you can format the volumes with Virtual Machine File System (VMFS).
Hypervisor cluster profile uses only the default TCP/IP stack configurations to create a VMkernel port on VMware vSphere ESXi hosts. To configure the VMkernel port with different TCP/IP stack configurations, use tools external to HPE OneView and retain the same VMkernel port name and VLAN as defined in the hypervisor cluster profile.
While enabling the Multi-NIC vMotion setting in a hypervisor cluster profile, during inconsistency remediation, ensure that the ESXi host has vMotion VMkernel port configured with default TCP/IP stack configuration. For other TCP/IP stack configurations in the vMotion VMkernel port, use tools external to HPE OneView.
While disabling the Multi-NIC vMotion setting in hypervisor cluster profile, provide the vMotion VMkernel port name that has to be retained.
You can grow the cluster by creating the server profiles, deploying and adding hypervisors to the cluster using external tools, importing the hypervisors into hypervisor cluster profile, and by remediating inconsistencies.
Relationship to other resources
UI screens and REST API resources
One or more networks
Zero or one OS deployment plan
Zero or more shared storage volumes
Zero or more hypervisor profiles