Operating Environment Software Instruction Manual

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.
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 allocated.
• 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
allocated, not the actual consumption of disk space.
• IP addresses allocation cost – cost assigned to each address allocated in the service, including
Virtual IP addresses.
• Cost frequency – assigned to a service and inherited by all resources. This represents the
recurrence of each cost mentioned above.
The chargeback system derives cost based on the value in minutes per cost frequency.
Cost frequency can be set to the following:
Day 24 hours
Week 7 days, which is 168 hours
Month 30 days, which is 720 hours
Using the infrastructure orchestration chargeback feature, the administrator can:
• Map allocation data to services, logical servers, logical networks, and logical disks
• Map uptime for logical servers
• Filter data for a specific period in time
• Store allocation data for the last 365 days, and archive monthly data after 365 days
SOAP API extensions and the chargeback command line interface can be used to retrieve
allocation data. See “Using API extensions to retrieve chargeback data” (page 130) and “Using
the CLI to retrieve chargeback data” (page 133) for more information.
NOTE: The APIs and CLI command can retrieve data only for the last 365 days. Ensure that you
save old data before it is more than one year old so that you can access the data, if needed.
Deploying an operating system to multi-path storage 125