HP Insight Orchestration 6.0 User Guide

IA_64_MODELS=nb50000c
SUPPORTED_MODELS=bl260c
SUPPORTED_MODELS=bl280c
SUPPORTED_MODELS=bl460c
SUPPORTED_MODELS=bl465c
SUPPORTED_MODELS=bl480c
SUPPORTED_MODELS=bl490c
SUPPORTED_MODELS=bl495c
SUPPORTED_MODELS=bl680c
SUPPORTED_MODELS=bl685c
SUPPORTED_MODELS=bl860c
SUPPORTED_MODELS=bl870c
SUPPORTED_MODELS=bl890c
SUPPORTED_MODELS=HP xw8400 Workstation
After making the changes to the blade_models.properties file, it is necessary to restart the
Insight Orchestration Windows service for the changes to take effect.
This is a basic overview of how Operations Orchestration and ESA are used to provide inventory and
power control access for non-Virtual Connect managed servers. The reference implementation may be
used as is or it may be replaced by extending the workflows to obtain the server inventory from another
source within the data center. In addition, the power control workflows may be extended to other server
management processor types.
For more information on Operations Orchestration, see the HP Operations Orchestration Software Guide
located at http:// support.openview.hp.com/selfsolve/manuals.
Configuring Insight Orchestration storage management
Insight Orchestration integrates with several distinct approaches to storage management. The overall system
may be used with any or all of the approaches combined. The approaches are:
• Manual storage provisioning
• Automated storage provisioning
“Static” SAN volume automation through multi-initiator NPIVa.
b. “Dynamic” SAN volume automation via LUN masking
Manual storage provisioning means that either no storage has been pre-provisioned or that only a subset
of the storage has been pre-provisioned for a logical server. At the service creation time, Insight Orchestration
attempts to locate and allocate the storage resources.
When none are found, the overall request pauses for the administrator to manually provision the required
storage. The pause is notified by an Operations Orchestration generated email which contains the details
of the service being provisioned and the storage resources that are required. Once the administrator has
completed the storage provisioning process, the request is re-activated and allowed to continue.
Automated storage provisioning depends on pre-provisioning of SAN volumes. Once the SAN volumes have
been pre-provisioned, Insight Orchestration can automate the LUN presentation process to a server through
two different approaches. The first approach is called “Static” SAN volume automation through multi-initiator
NPIV. In this approach, SAN volumes are pre-masked to one more initiator WWNs within the SAN. Zoning
is also pre-configured. The SAN volumes are then made available within Virtualization Manager’s storage
pool as storage pool entries. At service creation, Insight Orchestration is able to choose one or more storage
pool entries from the storage pool. It will then examine the initiator WWNs that were associated with each
of the storage pool entries and perform the required assignment to the server in order to enable server
visibility within the SAN to the set of SAN volume targets defined by the storage pool entries. This approach
has the advantage of still being able to separate the boot and data storage visibility to the server during OS
provisioning without requiring any access to the existing SAN management interfaces. The approach is
limited to Virtual Connect managed servers only. For additional information, see Insight Dynamics – Automated
Storage Provisioning: “Static” SAN volume automation through multi-iniator NPIV White Paper or contact
your HP support representative.
Configuring Insight Orchestration to list heterogeneous hardware 33