Node Assassin Fence Agent v1.1.4 - Revision history

Digimer: /* XML Validation Support */

2010-08-15T23:07:32Z

XML Validation Support

← Older revision		Revision as of 23:07, 15 August 2010
Line 48:		Line 48:

	== XML Validation Support ==		== XML Validation Support ==

			'''Note''': This applies to RHEL 5.x / CentOS 5.x only.

	Before you can [[2-Node_CentOS5_Cluster#cluster.conf\|validate]] your <span class="code">cluster.conf</span> file, the valid options and syntax need to be added to <span class="code">cluster.ng</span>. The Node Assassin installer will do this for you.		Before you can [[2-Node_CentOS5_Cluster#cluster.conf\|validate]] your <span class="code">cluster.conf</span> file, the valid options and syntax need to be added to <span class="code">cluster.ng</span>. The Node Assassin installer will do this for you.

Digimer: /* Agent Testing */

2010-04-20T01:58:47Z

Agent Testing

← Older revision		Revision as of 01:58, 20 April 2010
Line 281:		Line 281:
	== Agent Testing ==		== Agent Testing ==

	To test ~~the~~ agent in a manner similar to how <span class="code">[[fenced]]</span> ~~calls~~ it, copy the following into a file (ie: <span class="code">args.txt</span>):		To test Node Assassin's <span class="code">fence_na</span> agent in a manner similar to how the <span class="code">[[fenced]]</span> daemon will call it, copy the following into a file (ie: <span class="code">args.txt</span>):

	<source lang="bash">		<source lang="bash">
Line 294:		Line 294:
	And <span class="code">cat</span> it into the fence agent via a pipe:		And <span class="code">cat</span> it into the fence agent via a pipe:
	<source lang="bash">		<source lang="bash">
	~~clear;~~ cat args.txt \| fence_na		cat args.txt \| fence_na
	</source>		</source>

Digimer: /* Agent Testing */

2010-04-20T01:48:14Z

Agent Testing

← Older revision		Revision as of 01:48, 20 April 2010
Line 297:		Line 297:
	</source>		</source>

	You can replace the <span class="code">port=1</span> and <span class="code">action=on</span> with another port number or a different <span class="code">[[Node Assassin's implementation of 'action's\|action]]</span> if you wish.		You can replace the <span class="code">port=1</span> and <span class="code">action=on</span> with another port number or a different <span class="code">[[#Node Assassin's implementation of 'action's\|action]]</span> if you wish.

	{{na_footer}}		{{na_footer}}

Digimer: /* Agent Testing */

2010-04-20T01:48:01Z

Agent Testing

← Older revision		Revision as of 01:48, 20 April 2010
Line 296:		Line 296:
	clear; cat args.txt \| fence_na		clear; cat args.txt \| fence_na
	</source>		</source>

			You can replace the <span class="code">port=1</span> and <span class="code">action=on</span> with another port number or a different <span class="code">[[Node Assassin's implementation of 'action's\|action]]</span> if you wish.

	{{na_footer}}		{{na_footer}}

Digimer: /* Agent Testing */

2010-04-20T01:44:03Z

Agent Testing

← Older revision		Revision as of 01:44, 20 April 2010
Line 281:		Line 281:
	== Agent Testing ==		== Agent Testing ==

	To test the agent in a manner similar to how [[fenced]] calls it, copy the following into a file (ie: <span class="code">args.txt</span>):		To test the agent in a manner similar to how <span class="code">[[fenced]]</span> calls it, copy the following into a file (ie: <span class="code">args.txt</span>):

	<source lang="bash">		<source lang="bash">
Line 294:		Line 294:
	And <span class="code">cat</span> it into the fence agent via a pipe:		And <span class="code">cat</span> it into the fence agent via a pipe:
	<source lang="bash">		<source lang="bash">
	clear; cat args.txt \| ./fence_na		clear; cat args.txt \| fence_na
	</source>		</source>

	{{na_footer}}		{{na_footer}}

Digimer: /* IMPORTANT! */

2010-04-20T01:42:27Z

IMPORTANT!

← Older revision		Revision as of 01:42, 20 April 2010
Line 277:		Line 277:
	'''''ALWAYS TEST YOUR Node Assassin!'''''		'''''ALWAYS TEST YOUR Node Assassin!'''''

	Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup~~. This sequence requires all connections to be working~~. If there are any problems, the fence agent will generate errors.		Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup. If there are any problems with your Node Assassin or with the cables connected to your node, the fence agent will fail and generate errors.

	== Agent Testing ==		== Agent Testing ==

Digimer: /* IMPORTANT! */

2010-04-20T01:40:12Z

IMPORTANT!

← Older revision		Revision as of 01:40, 20 April 2010
Line 277:		Line 277:
	'''''ALWAYS TEST YOUR Node Assassin!'''''		'''''ALWAYS TEST YOUR Node Assassin!'''''

	Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup. This sequence ~~will boot, fence and reboot the node and will require~~ all ~~functions~~ to be working ~~properly to succeed~~. If there are any ~~errors~~, the fence agent will generate errors.		Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup. This sequence requires all connections to be working. If there are any problems, the fence agent will generate errors.

	== Agent Testing ==		== Agent Testing ==

Digimer: /* IMPORTANT! */

2010-04-20T01:39:26Z

IMPORTANT!

← Older revision		Revision as of 01:39, 20 April 2010
Line 277:		Line 277:
	'''''ALWAYS TEST YOUR Node Assassin!'''''		'''''ALWAYS TEST YOUR Node Assassin!'''''

	Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup. This sequence will boot, fence and reboot the node and will require all functions to be working properly to succeed.		Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup. This sequence will boot, fence and reboot the node and will require all functions to be working properly to succeed. If there are any errors, the fence agent will generate errors.

	== Agent Testing ==		== Agent Testing ==

Digimer: /* IMPORTANT! */

2010-04-20T01:37:01Z

IMPORTANT!

← Older revision		Revision as of 01:37, 20 April 2010
Line 275:		Line 275:
	If you connect the power or reset buttons backwards, the circuit will be closed (that is, you will have pressed the button). This is by design!		If you connect the power or reset buttons backwards, the circuit will be closed (that is, you will have pressed the button). This is by design!

	'''''ALWAYS TEST ~~YOU~~ Node Assassin!'''''		'''''ALWAYS TEST YOUR Node Assassin!'''''

	Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup. This sequence will boot, fence and reboot the node and will require all functions to be working properly to succeed.		Specifically, after connecting a new node, be sure to manually send the <span class="code">on</span> -> <span class="code">off</span> -> <span class="code">on</span> actions to make sure that the nodes are properly setup. This sequence will boot, fence and reboot the node and will require all functions to be working properly to succeed.

Digimer: /* list */

2010-04-20T01:20:19Z

list

← Older revision		Revision as of 01:20, 20 April 2010
Line 189:		Line 189:
	=== list ===		=== list ===

	This returns a CSV of the ports on your Node Assassin. Each node will be on a new line in the format '<span class="code">node,alias</span>' where the alias is read from the ~~config~~ file.		This returns a CSV of the ports on your Node Assassin. Each node will be on a new line in the format '<span class="code">node,alias</span>' where the alias is read from the Node Assassin [[Fence_na.conf\|configuration]] file.

	== Node Assassin Specific Actions ==		== Node Assassin Specific Actions ==