HP Insight Management 7.2 Update 2 Support Matrix

Unsupported items in a CMS cluster configuration
• Brocade Network Advisor, HP P6000 Command View Software, HP Operations Orchestration,
VMware vCenter Server, and similar applications are not permitted in a CMS cluster
• Multi-site Windows cluster: a CMS cluster is a single site cluster.
Matrix KVM Private Cloud in a HA environment
The Matrix KVM Admin Console appliance can be configured as a single-site, two-node physical
server RHEL KVM 6.3 or RHEL KVM 6.4 cluster to create a highly-available environment.
Four networks are required for the cluster Management hosts and Matrix KVM Admin Console
appliance:
Table 24 Matrix KVM Private Cloud clustering network requirements
DescriptionNetwork
A public network for user management and Matrix OE
access.
Matrix Operating Environment Access network (Private
subnet for instances) and Matrix KVM Private Cloud
Production network (Cloud connectivity subnet)
1
A private network for the Matrix KVM Private Cloud to
communicate with the OpenStack managed KVM hosts.
Matrix KVM Private Cloud Management network (Host
management subnet)
A private Matrix OE network for deployment of operating
systems on the physical KVM hosts.
Matrix Operating Environment Deployment network
A private network for the cluster communication and
heartbeat.
Cluster Heartbeat network
1
The two networks can be separate if isolation is needed.
NOTE: After deploying the management KVM Host operating system onto each of the cluster
nodes, the Matrix OE Deployment network connection is repurposed to become one of the
connections in the Cluster Heartbeat network bonded pair.
Three pieces of storage are used in the cluster:
• Matrix KVM Private Cloud root storage
• Glance OS image storage
• Cluster quorum disk
Matrix KVM Private Cloud in a HA environment 25