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

Insight Orchestration – Storage Automation via NPIV
4
Figure 1: Deploy SAN storage
Figure 1 describes the basic process that must be followed in order to configure a SAN bootable C-
Class blade with Virtual Connect. The process must be repeated for each server that the Server
administrator wishes to deploy. The time delay between steps 2 and 4 can be days to weeks. Any
changes to the Server’s SAN configuration must be accomplished by another manual interaction with
the Storage administrator.
This process can be improved through an alternate approach as described in the following figure:
System Admin
Storage Admin
Defines server profiles
and identifies required
storage volumes.
1
Defines server profiles
and identifies required
storage volumes.
1
Requests Volumes
[provides HBA WWNs]
2
Creates volumes,
configures SAN zoning,
configures target SSP
3
Creates volumes,
configures SAN zoning,
configures target SSP
3
Assigns server profiles
and deploys images
5
Assigns server profiles
and deploys images
5
Ready
[provides target WWNs]
4
Repeat.
6
“Batched”
System Admin
Storage Admin
Selects volumes and
uses associated WWNs
to create server profile.
3
Selects volumes and
uses associated WWNs
to create server profile.
3
Creates volumes and
associates with WWNs.
Configures SAN zoning,
configures target SSP.
Defines HA/backup
policies.
Defines performance.
1
Assigns server profiles
and deploys images
4
Assigns server profiles
and deploys images
4
Provides Pool of Volumes
[Each volume has pair of HBA WWNs]
2
Repeat over and over
again without interacting
with storage admin!
5
Owns a large range
of FC HBA WWNs