7 using hp 3par policy manager, Policy inheritance and hierarchy, Working in the policy tab – HP 3PAR Policy Manager Software User Manual
Page 24: Working in the policy
7 Using HP 3PAR Policy Manager
Policy Inheritance and Hierarchy
HP 3PAR Policy Manager manages device policies and notification settings through a hierarchy
of groups and standard parent-child relationships. There is one global group, named Global by
default (this name can be changed). The Global group is a parent (or grandparent, depending
upon the child group's level in the hierarchy) group to all other groups defined in Policy Manager.
Within the Global group, there can be one or more subgroups, or child groups, and devices.
Each device that registers with Policy Manager provides its model number, which is used to create
groups in Policy Manager. Within the Policy Manager application pages, you can rename existing
groups and create new groups.
To view the Policy Manager groups, click Explore Device Groups. Each subgroup below the Global
group is considered another level in the group hierarchy as shown in
Figure 16 Viewing Groups
In
, Service Processor and Gateway Processor are child groups to Global. Any
permissions set in the Global group are inherited by its child groups. Within a child group's policy
you can override a permission set in the parent group if that permission is not locked in the parent's
policy. The overridden policy is then inherited by that child group and its subgroups.
Group configuration settings also subscribe to this inheritance system with regard to notifications.
Notification settings for the Global group are inherited by the child groups of that Global group.
For each child group or device, you can override inherited permissions and notification settings
and add new permissions. Any new permissions or changed permissions affect all child groups
and related devices.
Working in the Policy Tab
When a device first registers with HP 3PAR Policy Manager, it provides the Policy Manager with
a complete list of its supported actions, as can be seen by navigating the Policy tab (
). Each action requires a permission. A permission is a set of parameters and an
associated access right. Some actions have parameters and some do not. Each action defined in
a device's policy may have multiple, related permissions.
Policy Manager is installed with support for all known actions contained in the released version
of the HP 3PAR Secure Service Architecture software (see
“Base Installation Actions” (page 25)
).
By default, all actions included in the installed Policy Manager are defined with an access right
of Ask for Approval. Until the access right is changed in the Policy Manager interface, each device
under management will ask for approval to perform any action defined in the policy. The Policy
Manager supports any new actions, such as custom actions that may be customer-specific or
device-specific, and automatically applies an access right of Ask for Approval.
24
Using HP 3PAR Policy Manager