Chapter 15: Node Groups

Home Prev	InCenter 2.2.5 On-Premises Administration Guide	Next

A node can be assigned membership in a NodeGroup. The group concept provides the ability to apply administrative actions to a group instead of an individual node, where the action will apply to all the nodes within the group

No predefined groups exist in InCenter so they must be defined by the administrator and then assigned to nodes.

The Rules of Using Groups

The following rules should be noted when using groups:

A single node can only be a member of a single group.
A group can contain other groups.
Individual HA members cannot be group members, instead it is the HAPair object that is added and as a consequence the HA members are indirectly included in the group.
If a group is deleted, its members become children of any parent group. If there is no parent to the original group then the children will have no group membership after deletion.

15.1. Managing Groups with the CLI

The way to create a new group called my-group is with the following command:

admin@InCenter:/> add NodeGroup
			Name=my-group1
			NodeType=NetWall

Note that the NodeType property must be specified. The NodeType would be set to NetShield for NetShield nodes.

Adding a Node to a Group

The node called my-node1 can then be added to this group:

admin@InCenter:/> set StandaloneNode my-node1
			Group=my-group1

Group Membership of Other Groups

A group can itself be a member of a group. Suppose there is a group called my-top-group. The group my-group1 could be added to it:

admin@InCenter:/> set NodeGroup my-group1 Group=my-top-group

Commands That Can Use Groups

Instead of specifying a StandaloneNode or HAPair object in a command, a NodeGroup can be specified instead. The command will then be applied to all members of the group, including subgroups.

The <all> Group

The special keyword <all> can be used if a command is to be applied to all the nodes under <all> control. This can be regarded as a predefined group that contains all nodes.