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

Insight Orchestration – Storage Automation via NPIV
14
3. HPIO finds a free storage pool entry that matches the requested boot disk criteria and marks
it as used. HPIO also finds a storage pool entry that matches the requested data disk criteria
and marks it as used. At this point, only the boot disk will be attached to the server.
4. HPIO finds a free server and takes the HBA WWN (in this case ‘wwnr1’) that was stored in
the boot disk’s storage pool entry and assigns this WWN to the server’s HBA (as indicated
above).
5. HPIO powers the server up and initiates the standard FC login sequence and is granted
access to ‘Lun1’ on the disk array.
6. The blade continues to boot. When it finds no OS on ‘Lun1’, it falls through to a network boot
which attaches the server to the OS deployment server.
7. HPIO instructs the OS deployment server to install the selected OS on ‘Lun1’. The OS install
process is monitored to completion.
8. HPIO instructs the server to power off.
This leads to the second phase of the server provisioning process which is outlined in the next figure.
Figure 9: Add the data disk(s)
After HPIO successfully deploys the OS to the server, the server is powered-off and HPIO begins the
process of attaching the server to its data disks.
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
wwnr3
wwnr1, Lun1, …
wwnr2, Lun2, …
wwnr3, Lun3, …
wwnr4, Lun4, …
Storage Pool
LogicalServerLogicalServer
10GB
20GB