HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

Deploying an operating system to multi-path storage
Matrix infrastructure orchestration can deploy an operating system to a multi-path storage volume.
For Insight Control server deployment, Windows operating systems do not require any server
deployment modifications. However, for Red Hat Enterprise Linux 5.4, 5.5, and 6.0, modify the
default server deployment process by editing the Configure Boot Environment job.
Edit the Configure Boot Environment job and add the export kernparm=mpath kernel parameter.
After updating the job, Red Hat Enterprise Linux 5.5, 5.6, and 6.0 can be deployed to a multi-path
LUN.
Matrix Operating Environment support of IO accelerators
NOTE: Matrix infrastructure orchestration Accelerator support applies to Matrix OE versions 7.2,
7.2.1, 7.2.2, 7.3, and 7.3.1.
Matrix infrastructure orchestration Accelerators are supported in the Matrix Operating Environment
with limitations. The hypervisor version and Virtual Connect modules need to support the particular
IO Accelerator. Matrix OE will not provision the hypervisor host to use the IO Accelerators (the
installation and configuration of the hypervisor using these accelerators would be independent of
Matrix OE). Matrix OE can be used to provision VMs to the hypervisor host. For information on
IO Accelerators, see http://h18004.www1.hp.com/products/storageworks/io_accelerator/
index.html. Two whitepapers are available online that describe the setup and scenarios for using
IO Accelerators. You can locate the Insight Management and HP IO Accelerators (ioTurbine version
2.0.3.1) – Supported Environments and Scenarios White Paper and the Insight Management and
HP IO Accelerators (ioTurbine version 2.1) – Supported Environments and Scenarios White Paper
in the Insight Management Information Library at http://www.hp.com/go/insightmanagement/
docs.
Assigning and retrieving cost and billing information (chargeback)
The Matrix infrastructure orchestration architect can specify allocation costs for resources in a
service. Matrix infrastructure orchestration collects and stores this allocation data, which can be
retrieved in a format that can be easily consumed by a variety of third-party applications.
Following are the types of costs that can be specified and reported.
• Fixed cost – Specific per service instance. Represents startup cost, software or administrative
overhead, and ongoing maintenance.
• Server allocation cost – cost for server is divided into:
Memory unit cost – Allocation cost associated to each CPU assigned to the server.◦
◦ CPU unit cost – Allocation cost per CPU unit.
◦ Server base cost – Represents the cost associated with the server to cover other services,
such as linked clone deployment and high availability. Can also be used to assign cost
on a per server basis, independent of the number of CPUs and memory.
• Disk allocation cost – allocation cost per disk unit (MB or GB). This is the disk space that is
specified in the template, not the actual consumption of disk space. For example, if you have
an inventory of physical disks that are 50 GB each and you specify in the IO template that
you need only 20 GB, IO allocates storage at 50 GB because that is the size of the available
disks. However, the user is only billed for the 20 GB that is specified for use in the template.
• IP addresses allocation cost – cost assigned to each address allocated in the service, including
Virtual IP addresses.
Deploying an operating system to multi-path storage 153