Abandoned - 2-Node EL5 Cluster - Revision history

Digimer: moved 2-Node EL5 Cluster to Abandoned - 2-Node EL5 Cluster

2012-01-05T16:08:25Z

moved 2-Node EL5 Cluster to Abandoned - 2-Node EL5 Cluster

← Older revision		Revision as of 16:08, 5 January 2012
(No difference)

Digimer at 17:36, 6 May 2011

2011-05-06T17:36:08Z

← Older revision		Revision as of 17:36, 6 May 2011
Line 1:		Line 1:
	{{howto_header}}		{{howto_header}}

			{{warning\|1=This is an older article and should only be used for historical reference. The only up to date clustering tutorial is: [[Red Hat Cluster Service 2 Tutorial]].}}

	----		----

Digimer at 13:54, 14 March 2011

2011-03-14T13:54:46Z

← Older revision		Revision as of 13:54, 14 March 2011
Line 2:		Line 2:

	----		----
	I've restarted ~~work on~~ this ~~paper, given~~ the ~~delays in CentOS 6~~.~~0 release. Even after it~~ is ~~released, I think there~~ will be ~~sufficient interest in EL5 and Cluster 2 that~~ it ~~is worth completing~~.		I've restarted this tutorial from scratch in the [[Red Hat Cluster Service 2 Tutorial]]. This tutorial is for reference only and will be deleted once I finish the new tutorial. Please do not follow this tutorial, but it should be ok to use as a reference.
	- '''~~Mer~~. 03, 2011'''.		- '''Mar. 14, 2011'''.
	----		----

Digimer: /* LVM */

2011-03-10T17:00:28Z

LVM

← Older revision		Revision as of 17:00, 10 March 2011
Line 1,103:		Line 1,103:
	=== Updating '/etc/lvm/lvm.conf' ===		=== Updating '/etc/lvm/lvm.conf' ===

	'''Note''': ~~After CentOS 5~~.5 ~~is released~~, this step ~~should no longer be~~ needed. See [https://bugzilla.redhat.com/show_bug.cgi?id=530881 here] for details.		'''Note''': With [[EL5]].5, this step is only needed with using software [[RAID]] as LVM sees both the <span class="code">/dev/mdX</span> and <span class="code">/dev/drbdX</span> devices as LVM PVs and defaults to using the RAID device, which fails when creating LVs. See [https://bugzilla.redhat.com/show_bug.cgi?id=530881 here] for details.

	~~By default, LVM ignores DRBD~~ devices ~~as candidate physical volumes. To enable DRBD~~, we need to change the <span class="code">filter</span> in <span class="code">/etc/lvm/lvm.conf</span> to include a regular expression that matches the name of our DRBD device. We created our DRBD device as <span class="code">/dev/drbd0</span>, so changing the <span class="code">filter</span> to <span class="code">filter = [ "a\|drbd.\|", "a\|sd.\|", "r\|.\|" ]</span> ('''a'''ccept <span class="code">drbd</span> devices and devices with the <span class="code">sd</span> "scsi" names, '''r'''eject everything else) will do this. Edit <span class="code">lvm.conf</span> and change it to match this:		To hide software RAID devices, we need to change the <span class="code">filter</span> in <span class="code">/etc/lvm/lvm.conf</span> to include a regular expression that matches the name of our DRBD device and rejects everything else. We created our DRBD device as <span class="code">/dev/drbd0</span>, so changing the <span class="code">filter</span> to <span class="code">filter = [ "a\|drbd.\|", "a\|sd.\|", "r\|.\|" ]</span> ('''a'''ccept <span class="code">drbd</span> devices and devices with the <span class="code">sd</span> "scsi" names, '''r'''eject everything else) will do this. Edit <span class="code">lvm.conf</span> and change it to match this:

	<source lang="bash">		<source lang="bash">

Digimer: /* Create or Edit /etc/drbd.conf */

2011-03-03T22:41:26Z

Create or Edit /etc/drbd.conf

← Older revision		Revision as of 22:41, 3 March 2011
Line 912:		Line 912:

	syncer {		syncer {
	rate ~~33M~~;		rate 15M;
	}		}
	}		}
Line 921:		Line 921:
	net {		net {
	allow-two-primaries;		allow-two-primaries;
			after-sb-0pri discard-zero-changes;
			after-sb-1pri discard-secondary;
			after-sb-2pri disconnect;
	}		}

Line 927:		Line 930:
	}		}

	meta-disk internal		meta-disk internal;

	on an-node01.alteeve.com {		on an-node01.alteeve.com {
	address 10.0.0.71:7789;		address 192.168.2.71:7789;
	disk /dev/~~an-lvm01/lv02~~;		disk /dev/sda4;
	}		}

	on an-node02.alteeve.com {		on an-node02.alteeve.com {
	address 10.0.0.72:7789;		address 10.0.0.72:7789;
	disk /dev/~~an-lvm02/lv02~~;		disk /dev/sda4;
	}		}
	}		}

Digimer at 22:37, 3 March 2011

2011-03-03T22:37:38Z

← Older revision		Revision as of 22:37, 3 March 2011
Line 2:		Line 2:

	----		----
	I've ~~been working~~ on ~~what stumps me with Corosync/OpenAIS~~, ~~Pacemaker and so on. I've concluded that~~ the ~~best course forward is to re-work this paper to be based on [[Fedora]] 13. There has simply been too many dramatic changes~~ in ~~the Cluster Stack to make clustering on~~ CentOS ~~5 worth it~~. ~~The Fedora 13 adaption will be focused on, itself, being adapted to RHEL/CentOS 6 when it~~ it released~~. That~~, ~~of course, should~~ be ~~''real soon now''. Sorry for the recent delays... I've burned through a lot of time coming to this decision. [[Two Node Fedora 13~~ Cluster~~\|Here]]~~ is ~~the work-in-progress~~.		I've restarted work on this paper, given the delays in CentOS 6.0 release. Even after it is released, I think there will be sufficient interest in EL5 and Cluster 2 that it is worth completing.
	- '''~~Jun. 12, 2010'''~~.		- '''Mer. 03, 2011'''.

	This How-To is nearing completion, but is '''not''' finished yet. Please [[Digimer\|provide]] feedback, criticism and advice. Until this warning is removed, please do not link to this page - we'll both just look bad. :)
	~~- '''May 12~~, ~~2010~~'''.
	----		----

Digimer: moved 2-Node CentOS5 Cluster to 2-Node EL5 Cluster: Changed the name to better reflect "Enterprise Linux" version 5 compatibility.

2011-02-27T14:49:56Z

moved 2-Node CentOS5 Cluster to 2-Node EL5 Cluster: Changed the name to better reflect "Enterprise Linux" version 5 compatibility.

← Older revision	Revision as of 14:49, 27 February 2011
(No difference)

Digimer: /* OS Install */

2011-02-25T20:28:08Z

OS Install

← Older revision		Revision as of 20:28, 25 February 2011
Line 89:		Line 89:
	* [[an-node01.ks]]		* [[an-node01.ks]]
	* [[an-node02.ks]]		* [[an-node02.ks]]
			* [[c5_generic_node.ks]] - New kickstart for automatically detecting and configuring storage.

	== AN!Cluster Install ==		== AN!Cluster Install ==

Digimer at 03:54, 12 July 2010

2010-07-12T03:54:25Z

← Older revision		Revision as of 03:54, 12 July 2010
Line 619:		Line 619:

	Here is the one '''AN!Cluster''' uses, with in-line comments, mostly from the <span class="code">man cluster.conf</span> page.		Here is the one '''AN!Cluster''' uses, with in-line comments, mostly from the <span class="code">man cluster.conf</span> page.
	* [[Two-Node cluster.conf\|cluster.conf]]		* [[Two-Node CentOS 5 cluster.conf\|cluster.conf]]

	Once you're comfortable with your changes to the file, you need to validate it. Run:		Once you're comfortable with your changes to the file, you need to validate it. Run:

Digimer: Undo revision 1748 by Digimer (Talk)

2010-07-04T00:02:01Z

Undo revision 1748 by Digimer (Talk)

← Older revision		Revision as of 00:02, 4 July 2010
Line 68:		Line 68:
	* Three network cards; At least one should be gigabit or faster.		* Three network cards; At least one should be gigabit or faster.
	* One or more hard drives.		* One or more hard drives.
	* You will need some form of a [[fence device]]. This can be an [[IPMI]]-enabled server, a [http://nodeassassin.org Node Assassin], a fenceable [http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=AP7900&tab=features PDU] or similar.

	This paper uses the following hardware:		This paper uses the following hardware:
Line 76:		Line 75:
	* 1x Intel 82540 PCI NICs		* 1x Intel 82540 PCI NICs
	* 1x D-Link DGE-560T		* 1x D-Link DGE-560T
	* Node Assassin

	This is not an endorsement of the above hardware. I bought what was within my budget that would server the purposes of creating this document. What you purchase shouldn't matter, so long at the minimum requirements are met.		This is not an endorsement of the above hardware. I bought what was within my budget that would server the purposes of creating this document. What you purchase shouldn't matter, so long at the minimum requirements are met.

	~~== Pre-Assembly ==~~

	With multiple NICs, it is quite likely that the mapping of physical devices to logical <span class="code">ethX</span> devices may not be ideal. This is a particular issue if you decide to [[Setting Up a PXE Server in Fedora\|network boot]] your install media. In that case, if the wrong NIC is chosen for <span class="code">eth0</span>, you will be presented with a list of MAC addresses to attempt setup with.

	~~Before you assemble your servers, record their network cards' [[MAC]] addresses. I like to keep simply text files like this:~~
	~~<source lang="bash">~~
	~~vim an-node02.mac~~
	~~</source>~~
	~~<source lang="text">~~
	~~90:E6:BA:71:82:D8 eth0 # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller~~
	~~00:21:91:19:96:5A eth1 # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter~~
	~~00:0E:0C:59:45:78 eth2 # Intel Corporation 82540EM Gigabit Ethernet Controller~~
	~~</source>~~

	~~Feel free to record the information in any way that suits you the best.~~

	== OS Install ==		== OS Install ==

	Start with a stock ~~Fedora 13~~ install. This How-To uses ~~Fedora 13~~ x86_64, however it should be fairly easy to adapt to other ~~recent Fedora version. This document is also attempting to be easily ported to [[~~CentOS~~]]/~~[[RHEL]] ~~version 6 once it is released. This will not adapt well to CentOS/RHEL version~~ 5 ~~though... Much of the cluster stack has changed dramatically since it was initially released~~.		Start with a stock CentOS 5.x install. This How-To uses CentOS 5.4 x86_64, however it should be fairly easy to adapt to other CentOS 5*, [[RHEL]]5 or other RHEL5-based distributions.

	These are sample kickstart script used by this paper. Be sure to set your how password string and network settings.		These are sample kickstart script used by this paper. Be sure to set your how password string and network settings.
Line 105:		Line 87:

	Generic cluster node kickstart scripts.		Generic cluster node kickstart scripts.
	* [[~~Fedora13 KS an-node01.ks\|~~an-node01.ks]]		* [[an-node01.ks]]
	* [[~~Fedora13 KS an-node01.ks\|~~an-node02.ks]]		* [[an-node02.ks]]

	== AN!Cluster Install ==		== AN!Cluster Install ==
Line 112:		Line 94:
	If you are feeling brave, below is a link to a custom install DVD that contains the kickstart scripts to setup nodes and an <span class="code">an-cluster</span> directory with all the configuration files.		If you are feeling brave, below is a link to a custom install DVD that contains the kickstart scripts to setup nodes and an <span class="code">an-cluster</span> directory with all the configuration files.

	* Download the custom '''AN!Cluster v0.2.~~001~~''' Install DVD. (4.5[[GiB]] iso). (Currently disabled - Reworking for F13)		* Download the custom '''AN!Cluster v0.1.006''' Install DVD. (4.5[[GiB]] iso). (Currently disabled - Reworking for F13)

	== Post OS Install ==		== Post OS Install ==