HP 3PAR StoreServ 7400 2-node HP 3PAR Policy Server Administrator's G - Page 28

Notifications, Editing Asset Groups

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

Page 28 highlights

Notifications As you have seen in creating an asset group, the properties for asset groups include notification information. You configure notifications so that Policy Server can send a notification to the appropriate Policy Server user(s) when it receives a request for approval of an action from an Agent in this asset group. If no user is specified for an asset group, Policy Server sends the notification to the designated Administrator for Policy Server. If you choose different users, make sure they have the privileges to the Pending Requests component so that they can respond to the notification. Editing Asset Groups You can change the names of asset groups created automatically for models. You might want to do this if, for example, you want to apply the same policy to two different models. After you change the name of one model group, you can move assets from the other model group into the newly named group. You can also create child groups in any existing asset group. You cannot create parent groups except by creating a new child group in the Global group and then creating child groups in that new child group. Then, you need to move the assets that you want to have the policies for the groups into the appropriate groups. Policy Server can support up to nine nested child groups within groups. The following hierarchy is possible: "Global.parent.child1.child2." The following figure illustrates how the hierarchy of asset groups is displayed under All Assets: HP 3PAR Policy Server 3-6

  • 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
HP 3PAR Policy Server
3-6
Notifications
As you have seen in creating an asset group, the properties for asset groups include notification information.
You configure notifications so that Policy Server can send a notification to the appropriate Policy Server
user(s) when it receives a request for approval of an action from an Agent in this asset group. If no user is
specified for an asset group, Policy Server sends the notification to the designated Administrator for Policy
Server. If you choose different users, make sure they have the privileges to the Pending Requests component
so that they can respond to the notification.
Editing Asset Groups
You can change the names of asset groups created automatically for models. You might want to do this if,
for example, you want to apply the same policy to two different models. After you change the name of one
model group, you can move assets from the other model group into the newly named group.
You can also create child groups in any existing asset group. You cannot create parent groups except by
creating a new child group in the Global group and then creating child groups in that new child group. Then,
you need to move the assets that you want to have the policies for the groups into the appropriate groups.
Policy Server can support up to nine nested child groups within groups. The following hierarchy is possible:
“Global.parent.child1.child2.” The following figure illustrates how the hierarchy of asset groups is displayed
under All Assets: