HP Matrix Operating Environment Automated Storage Provisioning: "Static"SAN volume automation via multi-initiator NPIV

Insight Orchestration – Storage Automation via NPIV

Figure 8: Boot disk selection and OS deployment

The process of automating the OS deployment to the server involves the following steps:

1. The Server administrator submits the LogicalServer to HPIO for provisioning. For our

example, the LogicalServer requires a 10 GB boot disk and a 20 GB data disk represented

at the bottom of the figure

2. HPIO examines the storage pool and searches for an available set of entries that match the

LogicalServer storage definition. The requirements we are seeking to match are a 10GB,

RAID 1 bootable disk, single-path, with the additional selection tags of: “BackupEnable” (I.e.

the disk is tagged as protected by backup) and “Med_Seq_Blk_IO” (i.e. the SAN

performance is considered “medium” for both sequential and block r/w I/O). While the tags

are just examples, the point is that the Server and SAN administrator have agreed on a

workable taxonomy for identifying the characteristics of the various storage pool entries.

These are typically tied to additional services provided for the storage as well as expected (or

intended) I/O load that will be driven by the server. This allows the SAN administrator to

publish how the storage is intended to be used and allows the Server administrator to enforce

the correct storage selection for the LogicalServer’s intended role within the data center.

Array

Lun1 10GB

Lun2 10GB

Lun3 20GB

Lun4 20GB

Blade Enclosure

VC-FCVC-FC

Blade

Fc-hba

Storage

Admin

wwnr1

wwnr4

Storage

Mgmt

HPIO, LSM

VCEM

HPIO, LSM

VCEM

wwnr2

wwnr3

wwnr1

wwnr1, Lun1, …

wwnr2, Lun2, …

wwnr3, Lun3, …

wwnr4, Lun4, …

Storage Pool

LogicalServerLogicalServer

10GB

20GB