Managing Microsoft Windows Server 2008 Hyper-V with HP Insight Software, integration note, 4th edition

7
As an example, Matrix infrastructure orchestration can automatically provision authorized test and
development templates. They can request resources through a self-service portal and its standard
catalog of infrastructure services. After making their requests, they can use the self-service portal to
track the status of resource requests from approval through the provisioning process. IT administrators
no longer need to respond to frequent questions on the status of resource requests.
Once a new service has been designed and tested it is ready to go into production, Matrix
infrastructure orchestration can repurpose the test and development infrastructure for other uses. Based
on best practice templates called Cloud Maps, you can provision certified infrastructure for production
use.
Planning for Using Insight Management and Matrix OE
software with Hyper-V R2
Using Insight Management software with Hyper-V R2 involves the following resources:
• Disk and memory
• Cluster discovery and management
• Required Microsoft patches
• QLogic HBA driver upgrades, if using a QLogic HBA
Disk and memory considerations
You can create the volume on disk in Windows in three ways:
• Assign a drive letter to the disk volume created
• Mount the disk volume to an empty folder in an existing partition
• Reference the disk directly using Volume GUID (Global Unique Identifier) if there is no drive letter or
mount point assigned
Insight Management software supports disk access for Hyper-V R2 virtual machines. This resolves the
limitation in the previous software release of 24 VMs per host and cluster.
In the Matrix capacity planning screens, Hyper-V R2 host headroom may have a one star rating. The
headroom of the host and the headroom of each guest running on the host determine the rating. For
Hyper-V R2 guests, memory reports at 100 percent (no headroom) because Microsoft Hyper-V R2
statically allocates memory for VMs and returns this value as the utilization. To work around this,
remove the default Memory Utilization limit from the Workload Utilization Limits configuration for
each guest.
Cluster discovery and management with HP SIM
HP SIM requires HP ProLiant Support Pack 8.20 (or later) to discover and associate members of a
Windows 2008 Failover Cluster correctly. Install the support pack on cluster members before
discovering and managing Windows 2008 Failover Clusters.
Microsoft Failover Cluster Manager does not set up reverse DNS lookup records in a way that allows
HP SIM to discover and associate the cluster members with the cluster ID. For steps to correct the
reverse DNS lookup records after creating a cluster, see the article “Registration of DNS PTR Records
for a Failover Cluster on 2008 Server.” It is available at
http://support.microsoft.com/kb/969049.
For the Matrix Operating Environment to manage a cluster host, use domain credentials to discover
the cluster in HP SIM. You can discover cluster aliases and VMs using administrator credentials. In HP