Cluster node

A Cluster node represents a group of hosts collaborating to form a cluster. The Cluster node represents the group rather than a single physical entity. They are also used represent mainframe sysplexes. Cluster nodes are under the full control of patterns.

For detailed information about patterns, see the The-Pattern-Language-TPL and Configipedia.

Cluster node lifecycle

The following section describes the scenarios in which a Cluster node is created, updated, or removed.

Creation

The creation of a Cluster node is under the full control of patterns. Clusters are created when they are detected on a host by a pattern which is searching for them. The pattern contains the conditions which enable it to detect a cluster. Once found, the pattern creates the Cluster that it needs. A relationship link is automatically created to the Host node and the Cluster will have a key generated.

The generated key for a Cluster node is entirely dependent on the kind of Cluster.

Update

The update procedure for a Cluster node is also under full control of patterns. When the pattern has identified a cluster, it calculates a key. If a Cluster node with that key already exists, it is updated accordingly.

Removal

A Cluster node can be destroyed either manually or automatically. Cluster nodes are automatically removed when the last remaining Host node or MFPart is unlinked. In some cases, particular patterns might not create a cluster until hosts are detected. In these cases, the pattern will remove the Cluster node when there is only one host linked to it. For vCenter cluster nodes, cluster nodes are removed when a VMware cluster no longer exists.

To manually remove a Cluster node, find the necessary Cluster, select it in the list and pick Destroy from the Actions list. Aging of Clusters node are controlled by a Software Instance node. For more information about cluster aging, see Software-Instance-node.

This is a Cascade Removal type, see Cascade Removal.

Cluster node attributes

The attributes on a Cluster node as described in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

Cluster node relationships

The relationships on a Cluster node are as described in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.