Two-Node CentOS 5 cluster.conf - Revision history

Digimer: moved Two-Node cluster.conf to Two-Node CentOS 5 cluster.conf: Added another example of the same file for a different OS.

2010-07-12T03:53:31Z

moved Two-Node cluster.conf to Two-Node CentOS 5 cluster.conf: Added another example of the same file for a different OS.

← Older revision		Revision as of 03:53, 12 July 2010
(No difference)

Digimer at 02:08, 28 May 2010

2010-05-28T02:08:04Z

← Older revision		Revision as of 02:08, 28 May 2010
Line 8:		Line 8:
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!--		<!--
	The cluster's name is "~~an_cluster~~" and, as this is the first version of this		The cluster's name is "an-cluster" and, as this is the first version of this
	file, it is set to version "1". Each time this file changes in any way, the		file, it is set to version "1". Each time this file changes in any way, the
	version number will have to be incremented by 1.		version number will have to be incremented by 1.
	-->		-->
	<cluster name="~~an_cluster~~" config_version="1">		<cluster name="an-cluster" config_version="1">
	<!--		<!--
	This is a special cman argument to enable cluster services to run		This is a special cman argument to enable cluster services to run
Line 31:		Line 31:
	`uname -n`.		`uname -n`.
	-->		-->
	<clusternode name="~~an_node01~~.alteeve.com" nodeid="1">		<clusternode name="an-node01.alteeve.com" nodeid="1">
	<fence>		<fence>
	<!--		<!--
Line 65:		Line 65:

	<!-- AN!Cluster Node 2 -->		<!-- AN!Cluster Node 2 -->
	<clusternode name="~~an_node02~~.alteeve.com" nodeid="2">		<clusternode name="an-node02.alteeve.com" nodeid="2">
	<fence>		<fence>
	<method name="node_assassin">		<method name="node_assassin">

Digimer at 23:55, 10 May 2010

2010-05-10T23:55:28Z

← Older revision		Revision as of 23:55, 10 May 2010
Line 6:		Line 6:

	<source lang="xml">		<source lang="xml">
	<<?xml version="1.0"?>		<?xml version="1.0"?>
	<!--		<!--
	The cluster's name is "an_cluster" and, as this is the first version of this		The cluster's name is "an_cluster" and, as this is the first version of this

Digimer at 22:50, 10 May 2010

2010-05-10T22:50:19Z

← Older revision		Revision as of 22:50, 10 May 2010
Line 3:		Line 3:
	This is the <span class="code">/etc/cluster/cluster.conf</span> file used in the [[2-Node CentOS5 Cluster]].		This is the <span class="code">/etc/cluster/cluster.conf</span> file used in the [[2-Node CentOS5 Cluster]].

	'''Note''': ~~The node names reference [[SAN]] nodes, but there~~ is ~~nothing~~ in ~~this configuration file that dictates the role of~~ a node~~, so you are~~ safe to use and adapt ~~this~~ for any 2-node cluster.		'''Note''': This is used in a generic node and should be safe to use and adapt for any 2-node cluster.

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

Digimer at 22:49, 10 May 2010

2010-05-10T22:49:33Z

← Older revision		Revision as of 22:49, 10 May 2010
Line 6:		Line 6:

	<source lang="xml">		<source lang="xml">
	<?xml version="1.0"?>		<<?xml version="1.0"?>
	<!--		<!--
	The cluster's name is "~~an_san~~" and, as this is the first version of this file,		The cluster's name is "an_cluster" and, as this is the first version of this
	it is set to version "1". Each time this file changes in any way, the version		file, it is set to version "1". Each time this file changes in any way, the
	number will have to be incremented by 1.		version number will have to be incremented by 1.
	-->		-->
	<cluster name="~~an_san~~" config_version="1">		<cluster name="an_cluster" config_version="1">
	<!--		<!--
	This is a special cman argument to enable cluster services to run		This is a special cman argument to enable cluster services to run
Line 26:		Line 26:
	-->		-->
	<clusternodes>		<clusternodes>
	<!-- ~~SAN~~ Node 1 -->		<!-- AN!Cluster Node 1 -->
	<!--		<!--
	The clusternode names must match the name returned by		The clusternode names must match the name returned by
	`uname -n`.		`uname -n`.
	-->		-->
	<clusternode name="~~an_san01~~.alteeve.com" nodeid="1">		<clusternode name="an_node01.alteeve.com" nodeid="1">
	<fence>		<fence>
	<!--		<!--
Line 59:		Line 59:
	-->		-->
	<method name="node_assassin">		<method name="node_assassin">
	<device name="~~ariel~~" port="01" action="off"/>		<device name="motoko" port="01" action="off"/>
	</method>		</method>
	</fence>		</fence>
	</clusternode>		</clusternode>

	<!-- ~~SAN~~ Node 2 -->		<!-- AN!Cluster Node 2 -->
	<clusternode name="~~an_san02~~.alteeve.com" nodeid="2">		<clusternode name="an_node02.alteeve.com" nodeid="2">
	<fence>		<fence>
	<method name="node_assassin">		<method name="node_assassin">
	<device name="~~ariel~~" port="02" action="off"/>		<device name="motoko" port="02" action="off"/>
	</method>		</method>
	</fence>		</fence>
Line 83:		Line 83:
	where to find it and how to access it.		where to find it and how to access it.
	-->		-->
	<fencedevice name="~~ariel~~" agent="fence_na"		<fencedevice name="motoko" agent="fence_na"
	ipaddr="~~ariel~~.alteeve.com" login="~~ariel~~" passwd="~~gr0tt0~~">		ipaddr="motoko.alteeve.com" login="motoko"
			passwd="secret" quiet="1">
	</fencedevice>		</fencedevice>
	<!--		<!--

Digimer at 01:15, 15 March 2010

2010-03-15T01:15:16Z

← Older revision		Revision as of 01:15, 15 March 2010
Line 83:		Line 83:
	where to find it and how to access it.		where to find it and how to access it.
	-->		-->
	<fencedevice name="ariel" agent="fence_na"		<fencedevice name="ariel" agent="fence_na"
	ipaddr="ariel.alteeve.com" login="ariel" passwd="gr0tt0">		ipaddr="ariel.alteeve.com" login="ariel" passwd="gr0tt0">
	</fencedevice>		</fencedevice>
Line 96:		Line 96:
	fenced. By default, there is a 6 second buffer, but this isn't very		fenced. By default, there is a 6 second buffer, but this isn't very
	much time. The following argument increases the time window where other		much time. The following argument increases the time window where other
	nodes can join before being fenced. I like to give up to one minute.		nodes can join before being fenced. I like to give up to one minute but
			the Red Hat man page suggests 20 seconds. Please do your own testing to
			determine what time is needed for your environment.
	-->		-->
	<fence_daemon post_join_delay="60">		<fence_daemon post_join_delay="60">

Digimer at 01:12, 15 March 2010

2010-03-15T01:12:03Z

← Older revision		Revision as of 01:12, 15 March 2010
Line 6:		Line 6:

	<source lang="xml">		<source lang="xml">
			<?xml version="1.0"?>
	<!--		<!--
	The cluster's name is "an_san" and, as this is the first version of this file,		The cluster's name is "an_san" and, as this is the first version of this file,

Digimer at 23:03, 14 March 2010

2010-03-14T23:03:29Z

← Older revision		Revision as of 23:03, 14 March 2010
Line 2:		Line 2:

	This is the <span class="code">/etc/cluster/cluster.conf</span> file used in the [[2-Node CentOS5 Cluster]].		This is the <span class="code">/etc/cluster/cluster.conf</span> file used in the [[2-Node CentOS5 Cluster]].

			'''Note''': The node names reference [[SAN]] nodes, but there is nothing in this configuration file that dictates the role of a node, so you are safe to use and adapt this for any 2-node cluster.

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

Digimer: Created page with '{{howto_header}} This is the /etc/cluster/cluster.conf file used in the 2-Node CentOS5 Cluster.