RHCS v3 cluster.conf - Revision history

Digimer: moved RHCS v3 Cluster.conf to RHCS v3 cluster.conf: Lowercasing the file name.

2011-03-15T02:20:45Z

moved RHCS v3 Cluster.conf to RHCS v3 cluster.conf: Lowercasing the file name.

← Older revision		Revision as of 02:20, 15 March 2011
(No difference)

Digimer: moved Cluster.conf to RHCS v3 Cluster.conf: Splitting v2 and v3 versions.

2011-03-15T02:17:54Z

moved Cluster.conf to RHCS v3 Cluster.conf: Splitting v2 and v3 versions.

← Older revision	Revision as of 02:17, 15 March 2011
(No difference)

Digimer: /* rm; The Resource Manager */

2010-09-20T21:52:44Z

rm; The Resource Manager

@@ Line 1,178: / Line 1,178: @@
 Fail over domains are a collection of nodes that a defined service may relocate to when the host node fails. It also how or if a service is to be relocates as nodes return to the cluster.
-* [http://sources.redhat.com/cluster/wiki/FailoverDomains More information]
+==== Element; failoverdomain ====
 <source lang="xml">

Digimer: /* rm; The Resource Manager */

2010-09-20T15:05:32Z

rm; The Resource Manager

@@ Line 1,155: / Line 1,155: @@
 === status_poll_interval ===
-...
+''No info''
 <source lang="xml">

Digimer: /* rrp_mode */

2010-09-07T16:51:53Z

rrp_mode

← Older revision		Revision as of 16:51, 7 September 2010
Line 298:		Line 298:

	'''NOTE''': Be sure to set this if you are using redundant rings! If you wish to use a redundant ring, it must be configured in each node's <span class="code">[[#clusternode\|clusternode]]</span> entry. See below for an example.		'''NOTE''': Be sure to set this if you are using redundant rings! If you wish to use a redundant ring, it must be configured in each node's <span class="code">[[#clusternode\|clusternode]]</span> entry. See below for an example.

			* Default is <span class="code">none</span>
			* Valid options are <span class="code">active</span>, <span class="code">passive</span>, or <span class="code">none</span>

	==== Manual Ring Recovery ====		==== Manual Ring Recovery ====
Line 312:		Line 315:
	corosync-cfgtool -s		corosync-cfgtool -s
	</source>		</source>

	* Default is <span class="code">none</span>
	* Valid options are <span class="code">active</span>, <span class="code">passive</span>, or <span class="code">none</span>

	=== secauth ===		=== secauth ===

Digimer: /* rrp_mode */

2010-09-07T16:51:27Z

rrp_mode

← Older revision		Revision as of 16:51, 7 September 2010
Line 298:		Line 298:

	'''NOTE''': Be sure to set this if you are using redundant rings! If you wish to use a redundant ring, it must be configured in each node's <span class="code">[[#clusternode\|clusternode]]</span> entry. See below for an example.		'''NOTE''': Be sure to set this if you are using redundant rings! If you wish to use a redundant ring, it must be configured in each node's <span class="code">[[#clusternode\|clusternode]]</span> entry. See below for an example.

			==== Manual Ring Recovery ====

	If a ring fails and then is restored, you must manually run the following to re-enable the ring.		If a ring fails and then is restored, you must manually run the following to re-enable the ring.

Digimer: /* Element; altname */

2010-09-07T16:49:26Z

Element; altname

← Older revision		Revision as of 16:49, 7 September 2010
Line 945:		Line 945:
	This provides a means of setting up a second, [[#rrp_mode\|redundant]] <span class="code">[[#totem; Totem Ring and the Redundant Ring Protocol\|totem]]</span> ring. This provides a means of communication between the nodes in the event of a failure of the primary ring, which could happen if a main switch failed. Without this, should the primary network fail, your nodes would all separate and there would be no way to gain quorum, stopping all hosted services. In corosync or openais, this would be known as ring number <span class="code">1</span>.		This provides a means of setting up a second, [[#rrp_mode\|redundant]] <span class="code">[[#totem; Totem Ring and the Redundant Ring Protocol\|totem]]</span> ring. This provides a means of communication between the nodes in the event of a failure of the primary ring, which could happen if a main switch failed. Without this, should the primary network fail, your nodes would all separate and there would be no way to gain quorum, stopping all hosted services. In corosync or openais, this would be known as ring number <span class="code">1</span>.

	At the time of this writing, totem rings will not automatically recover after a failure. Please see the ~~node~~ in [[#rrp_mode\|rrp_mode]] for information on how to manually recover a ring.		At the time of this writing, totem rings will not automatically recover after a failure. Please see the note in [[#rrp_mode\|rrp_mode]] for information on how to manually recover a ring.

	===== name =====		===== name =====

Digimer: /* rm; The Resource Manager */

2010-08-23T02:21:42Z

rm; The Resource Manager

← Older revision		Revision as of 02:21, 23 August 2010
Line 1,097:		Line 1,097:
	== rm; The Resource Manager ==		== rm; The Resource Manager ==

			The resource manager, also known as the resource group manager, handles clustered services.

			When the cluster gains [[quorum]], the resource manager brings clustered services online by starting them on their assigned nodes. In the event of a failure, the resource manager will wait until the node has been fenced and the cluster has been reconfigured. Once completed, it will
			recover the services that had been on the effected node(s).

			On the node that lost quorum, the resource manager on that node will stop all clustered services. These services will not restart until quorum has been regained.

			A key term to be familiar with is <span class="code">resource tree</span>, <span class="code">resource group</span> and <span class="code">service</span>. These refer to a collection of resources defined by and contained in a <span class="code"><service></span> tag. For more information, please see [[Red Hat]]'s article defining [http://sources.redhat.com/cluster/wiki/ResourceTrees resource trees].

			For more general information on resource groups, see <span class="code">man rgmanager</span>.

			=== log_level ===

			'''This attribute is deprecated'''.

			Please refer to <span class="code">[[#logging; Global Logging Settings\|logging; Global Logging Settings]]</span> for configuring logging.

			This sets the verbosity of messages sent to [[syslog]]. The following list indicates the priority of messages. Messages of level equal to or lower than the value set here will be logged. Messages from levels higher will be suppressed.

			* Log levels:
			** <span class="code">0</span> - System is unusable, emergency messages
			** <span class="code">1</span> - Action must be taken immediately
			** <span class="code">2</span> - Critical conditions
			** <span class="code">3</span> - Error conditions
			** <span class="code">4</span> - Warning conditions
			** <span class="code">5</span> - Normal but significant condition
			** <span class="code">6</span> - Informational
			** <span class="code">7</span> - Debug-level messages

			'''This attribute is deprecated'''.

			* Default is <span class="code">5</span>
			* Must be an integer between <span class="code">0</span> and <span class="code">7</span>

			=== log_facility ===

			'''This attribute is deprecated'''.

			Please refer to <span class="code">[[#logging; Global Logging Settings\|logging; Global Logging Settings]]</span> for configuring logging.

			This sets the [[Syslog#Facility\|syslog facility]] to use when sending messages to [[syslog]].

			* Default is <span class="code">daemon</span>
			* Valid values are listed <span class="code">auth</span>, <span class="code">authpriv, <span class="code">daemon, <span class="code">cron, <span class="code">ftp, <span class="code">lpr, <span class="code">kern</span>, <span class="code">mail</span>, <span class="code">news</span>, <span class="code">syslog</span>, <span class="code">user</span>, <span class="code">uucp</span>, <span class="code">local0</span>, <span class="code">local1</span>, <span class="code">local2</span>, <span class="code">local3</span>, <span class="code">local4</span>, <span class="code">local5</span>, <span class="code">local6</span> and <span class="code">local7</span>

			=== status_child_max ===

			This sets the maximum number of status check threads that may run on any given node at a time. Specifically, it controls how many instances of <span class="code">[[clustat]]</span> queries may be outstanding.

			Do not change this unless you have a good reason to and understand the effects of your change.

			* Default is <span class="code">5</span>
			* Must be a [http://en.wikipedia.org/wiki/Natural_number natural number]

			=== status_poll_interval ===

			...

	<source lang="xml">		<source lang="xml">

Digimer: /* Element; device */

2010-08-23T01:51:08Z

Element; device

← Older revision		Revision as of 01:51, 23 August 2010
Line 1,013:		Line 1,013:
	===== Element; device =====		===== Element; device =====

	This tag tells the cluster manager which <span class="code">[[#fencedevice\|fencedevice]]</span> to call in order to perform the defined fence action against the node.		This tag tells the cluster manager which <span class="code">[[#Element; fencedevice\|fencedevice]]</span> to call in order to perform the defined fence action against the node.

	There is one required tag, <span class="code">name</span>, though many more attributes may be defined depending on the fence device in use. All attributes other than <span class="code">name</span> will be passed to the [[fence agent]] associated with the appropriate <span class="code">[[#fencedevice\|fencedevice]]</span>.		There is one required tag, <span class="code">name</span>, though many more attributes may be defined depending on the fence device in use. All attributes other than <span class="code">name</span> will be passed to the [[fence agent]] associated with the appropriate <span class="code">[[#Element; fencedevice\|fencedevice]]</span>.

	====== name ======		====== name ======

Digimer: /* name */

2010-08-23T01:49:44Z

name

← Older revision		Revision as of 01:49, 23 August 2010
Line 1,019:		Line 1,019:
	====== name ======		====== name ======

	This must match the name of the <span class="code">[[#fencedevice\|fencedevice]]</span> name.		This must match the name of the <span class="code">[[#Element; fencedevice\|fencedevice]]</span> name.

	It uses this to find out which physical (or logical) fence device to use, and in turn what fence agent to call. Any attributes beyond <span class="code">name</span> will be passed to that fence agent. Generally this includes the port the node is connected to and what action to take. In the case of single-node fence devices, like IPMI, simply the action is defined.		It uses this to find out which physical (or logical) fence device to use, and in turn what fence agent to call. Any attributes beyond <span class="code">name</span> will be passed to that fence agent. Generally this includes the port the node is connected to and what action to take. In the case of single-node fence devices, like IPMI, simply the action is defined.

	Please see <span class="code">[[#fencedevices\|fencedevices]]</span> and individual <span class="code">[[#Fence Devices\|fence devices]]</span> for other attributes that may be used here.		Please see <span class="code">[[#fencedevices; Defining Fence Devices\|fencedevices]]</span> and individual <span class="code">[[#Fence Devices\|fence devices]]</span> for other attributes that may be used here.

	* No default		* No default