HP Insight Management 7.2 Update 2 Support Matrix

The target directory must be on a local hard disk drive. Some products might not install if the target directory is a mapped

or a shared drive.

Table 10 Compute nodes (KVM hosts) for Matrix KVM Private Cloud

Enterprise, intensive

use (large)

Department, moderate

use (medium)

Workgroup,

occasional use (small)POC/DemoHardware component

8422Initial Servers

32323232Maximum Servers

16 CPU cores16 CPU cores16 CPU cores4 CPU coresProcessor

96 GB RAM96 GB RAM96 GB RAM32 GB RAMMemory

200 GB200 GB200 GB25 GBBoot disk

1 TB1 TB1 TB300 GBDatastore disk

Table 11 (page 13) lists the solution limits and scalability requirements for the Matrix KVM Private

Cloud.

Table 11 Matrix KVM Private Cloud solution limits and scalability

ValueSolution limits and scalability

If the Matrix configuration is federated, it must be attached to the primary CMSMatrix KVM Private Cloud per

Matrix CMS

Up to 100Tenants

Up to 2500 managed VM guestsVMs

Up to 1000Images

Up to 100Flavors

Up to 4096IP addresses

Insight Control server provisioning hardware

Insight Control server provisioning is a VM appliance that runs on a separate VMware vSphere

(ESXi) or Microsoft Hyper-V host. It requires two IP addresses; a management address that is used

to connect to the appliance web interface and REST API, and a deployment IP that is used for

communicating with the target servers. The appliance can be configured in either single NIC

configuration where the two IPs share the same NIC, or a dual NIC configuration where each IP

is on a separate NIC.

In a single NIC configuration, both IP addresses must be in the same subnet and must have

connectivity to the target servers, the target server iLOs, and the media server. In a dual NIC

configuration, NIC1 is considered the management NIC and is used to connect to the appliance.

NIC2 is considered the deployment NIC and must have connectivity to the deployment NIC on

each target server and the media server. Connectivity to the target server iLOs can be through

either the deployment or management NIC.

Insight Control server provisioning and Insight Control server deployment cannot be active on the

same network at the same time because they both make use of PXE. They should be configured

on separate networks or only one can be actively configured for booting at a time. Table 12

(page 14) lists the hardware requirements for Insight Control server provisioning based on the size

of the configuration (demo, small or large). At a minimum, the Insight Control server provisioning

appliance must have at least 4 CPUs, 16 GB memory, and 200 GB of disk space.

Hardware and firmware 13