HP Insight Orchestration 6.3 User Guide

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 as follows:
1. Run SIM discovery from the GUI, or via the command line mxnode -a <target IP or
DNS name> -w.
NOTE: If you use the mxnode command, you must also enter the root/<root password>
for the provisioned server into the global credentials for Systems Insight Manager
(Options→Security Credentials→Global Credentials).
2. Deploy the SIM agent to the server either from the GUI, or via the command line
mxagentconfig -a -n <target IP or DNS name> -u <user> -p <password>.
Where:
<user>
is root
<ip>
is the IP address of the newly created Systems Insight Manager node
<password>
is the root password of the newly created Systems Insight Manager node
NOTE: You must complete the above steps to successfully delete the server and have the storage
which is attached to the server correctly scrubbed before the server is made available for use in
a new service.
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.4, 5.5, and 6.0, you must 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, you are able to deploy Red Hat Enterprise Linux 5.5, 5.6, and 6.0 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, a
customizable allocation mechanism 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://www.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
Deploying an operating system to multi-path storage 61