HP Insight Orchestration 6.0 User Guide

Insight Orchestration supports SAN boot or DAS boot OS deployment using Insight Control server deployment,
HP Server Automation, and Ignite-UX. With Insight Control server deployment, boot from SAN support in
Insight Orchestration requires that the Deploy ProLiant System Configuration (BL BFS) server deployment
job (from HP Deployment Toolbox\Hardware Configuration folder) be placed in the job folder.
After having provisioned HP-UX to an Integrity blade and after the newly provisioned server is discovered
by Systems Insight Manager, the new Systems Insight Manager node needs to be authorized to run the CMS
tools. That is done by running the mxagentconfig command as follows:
mxagentconfig –a –n <ip> –u root –p <root password>
Where:
<ip> is the IP address of the newly created Systems Insight Manager node
<root password> is the root password of the newly created Systems Insight Manager node
No additional configuration is needed for physical provisioning for HP Server Automation.
Deploying an operating system to multi-path storage
Insight 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.2 and 5.3, you must modify the default server deployment deployment process
by editing the Create Boot Environment job.
Edit the Create Boot Environment and add the export kernparm=mpath kernel parameter. After updating
the job, you are able to deploy both Red Hat Enterprise Linux 5.2 and Red Hat Enterprise Linux 5.3 to a
multi-path LUN.
Customizable allocation process
Insight Orchestration performs automated resource allocation using a built-in allocation mechanism, as
described above. This built in allocator is the default allocation mechanism. In addition, version 6.0 also
includes a customizable allocation mechanism that can be used instead of the built in allocator for some
parts of the resource customizable allocation process. The customizable allocator supports a flexible, rule
based fitting process using the JBoss Drools rule engine (http:// jboss.org/drools/). You can configure Insight
Orchestration to enable selective rule based fitting processes, which you can then customize as needed. By
default, all of the rule based fitting processes are disabled — the built in allocator’s fitting process is used.
This section describes how to enable rule based fitting processes.
Policy configuration file
The customizable allocation process uses pre-defined policy hooks in the <HPIO Install
dir>/conf/policy.xml configuration file. The policy file (policy.xml) contains multiple pre-defined
entry points (or hooks), enabled state, and the corresponding rule files. A sample entry in the policy.xml
file is shown in the following figure.
Deploying an operating system to multi-path storage 47