HP 3PAR StoreServ 7450 4-node HP 3PAR StoreServ Storage Concepts Guide (OS 3.1 - Page 24

HP 3PAR Virtual Domains, Overview, Domain Types

Get HP 3PAR StoreServ 7450 4-node PDF manuals and user guides View all HP 3PAR StoreServ 7450 4-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 24 highlights

4 HP 3PAR Virtual Domains Overview When initially setting up the HP 3PAR storage system, the system administrator creates and assigns users with roles and rights in the system. You can create, modify, and remove a user's access to HP 3PAR Virtual Domains Software in the system with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator's Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks. NOTE: Virtual domains require an HP 3PAR Virtual Domains Software license. For additional information about the license, see "HP 3PAR Software" (page 9). In addition to the inherent security provided by this hierarchical user structure, finer grain access control of the system can optionally be achieved through the implementation of virtual domains. Domains allow an administrator to create up to 1,024 domains, or spaces, within an system, where each domain is dedicated to a specific application. A subset of the system users have varying rights over the domains. The use of domains can be useful in scenarios where a single system is used to manage data from several different independent applications (Figure 2 (page 24)). Figure 2 Single System Managing Multiple Independent Applications Each domain allows users with varying levels of accessibility to domain objects. A domain is made of Common Provisioning Groups (CPGs), hosts, and Remote Copy groups. Domains contain derived domain objects such as Virtual Volumes (VVs), Logical Disks (LDs), and volume exports (VLUNs). Because objects are domain-specific, domain users cannot accidentally or deliberately export VVs to hosts outside of their assigned domain. Virtual domains can be grouped into autonomic groups that can be managed as one domain. If you have a group of domains that require the same administrative procedures, it is easier to group those domains into an autonomic group and mange them together. NOTE: Remote Copy requires an HP 3PAR Remote Copy Software license. For additional information about the license, see "HP 3PAR Software" (page 9). Domain Types When using domains for access control, accessibility to basic objects and derived objects is limited by a user's role and domain assignment. For more information about roles and rights, see, "HP 3PAR Storage System Users" (page 18). 24 HP 3PAR Virtual Domains

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
4 HP 3PAR Virtual Domains
Overview
When initially setting up the HP 3PAR storage system, the system administrator creates and assigns
users with roles and rights in the system. You can create, modify, and remove a user’s access to
HP 3PAR Virtual Domains Software in the system with both the HP 3PAR Command Line Interface
(CLI) and the HP 3PAR Management Console. Refer to the
HP 3PAR Command Line Interface
Administrator’s Manual
and the HP 3PAR Management Console Online Help for instructions on
how to perform these tasks.
NOTE:
Virtual domains require an HP 3PAR Virtual Domains Software license. For additional
information about the license, see
“HP 3PAR Software” (page 9)
.
In addition to the inherent security provided by this hierarchical user structure, finer grain access
control of the system can optionally be achieved through the implementation of virtual domains.
Domains allow an administrator to create up to 1,024 domains, or spaces, within an system,
where each domain is dedicated to a specific application. A subset of the system users have
varying rights over the domains. The use of domains can be useful in scenarios where a single
system is used to manage data from several different independent applications (
Figure 2 (page 24)
).
Figure 2 Single System Managing Multiple Independent Applications
Each domain allows users with varying levels of accessibility to domain objects. A domain is made
of Common Provisioning Groups (CPGs), hosts, and Remote Copy groups. Domains contain derived
domain objects such as Virtual Volumes (VVs), Logical Disks (LDs), and volume exports (VLUNs).
Because objects are domain-specific, domain users cannot accidentally or deliberately export VVs
to hosts outside of their assigned domain.
Virtual domains can be grouped into autonomic groups that can be managed as one domain. If
you have a group of domains that require the same administrative procedures, it is easier to group
those domains into an autonomic group and mange them together.
NOTE:
Remote Copy requires an HP 3PAR Remote Copy Software license. For additional
information about the license, see
“HP 3PAR Software” (page 9)
.
Domain Types
When using domains for access control, accessibility to basic objects and derived objects is limited
by a user’s role and domain assignment. For more information about roles and rights, see,
“HP
3PAR Storage System Users” (page 18)
.
24
HP 3PAR Virtual Domains