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

Insight Orchestration – Storage Automation via NPIV
7
Building the storage pool for boot disks and private data disks
Figure 3: Building the storage pool
The figure above illustrates out the basic flow:
1. The Server administrator communicates the storage requirements for the servers that he wishes
to provision with HPIO. As a part of this, the Server administrator will consider the different
types of storage:
a. Boot Disks - how many?, what size or sizes?, RAID level?, what OS type will be
deployed (i.e. Windows, Linux, …), do they need to be HA protected within the
SAN?, do they need backup services?, are there specific I/O requirements or what
kind of applications will be running on a server that has access to the disk?, …
b. Private Data Disks - same question as above
c. Shared Data Disks - same question as above and, what level of sharing is required
(i.e. how many other servers in the environment will require access to the same set of
shared data disks?).
2. The Server administrator communicates the output of this planning process to the SAN
administrator, most likely in the form of an email or a spreadsheet. This communication may
also be part of an existing work ticketing process between the different groups that administer
the resources in the data center for various business units. As an example, the following
information would be used to concretely define a boot disk:
a. WindowsBootDisk1
Server
Admin
Array
Lun1 10GB
Lun2 10GB
Lun3 20GB
Lun4 20GB
Blade Enclosure
VC-FC
Blade
Fc-hba
Free VC
Domain
WWNs
Storage
Admin
Present
LUNs to floating
server side
WWNs
wwnr1
wwnr4
Storage
Mgmt
HPIO, LSM
VCEM
wwnr2
Email: Storage Pool request
wwnr3
wwnr1
wwnr2
wwnr3
wwnr4