AN!Cluster Tutorial 2 - Revision history

Digimer: /* Reading IPMI Data */

2016-05-28T21:20:38Z

Reading IPMI Data

← Older revision		Revision as of 21:20, 28 May 2016
Line 4,569:		Line 4,569:
	Found it! So we know that this server uses LAN channel 2. We'll need to use this for the next steps.		Found it! So we know that this server uses LAN channel 2. We'll need to use this for the next steps.

	=== Reading IPMI ~~Data~~ ===		=== Reading IPMI Network Info ===

	Now that we can read our IPMI data, it's time to set some values.		Now that we can read our IPMI data, it's time to set some values.

Digimer: /* A Note on STP */ - caught by ildefonso

2016-03-18T23:53:20Z

A Note on STP: - caught by ildefonso

← Older revision		Revision as of 23:53, 18 March 2016
Line 996:		Line 996:
	=== A Note on STP ===		=== A Note on STP ===

	~~Scanning~~ Tree Protocol, [[STP]], is a protocol used for detecting and protecting against switch loops. Without it, if both ends of the same cable plugged into the same switch or VLAN, or if two cables run between the same pair of switches, a [[broadcast storm]] could cause the switches to hang and traffic would stop routing.		Spanning Tree Protocol, [[STP]], is a protocol used for detecting and protecting against switch loops. Without it, if both ends of the same cable plugged into the same switch or VLAN, or if two cables run between the same pair of switches, a [[broadcast storm]] could cause the switches to hang and traffic would stop routing.

	The problem with STP in HA clusters though is that the attempt to detect loops requires blocking all other traffic for a short time. Though this is short, it is usually long enough to cause corosync to think that the peer node has failed, triggering a fence action.		The problem with STP in HA clusters though is that the attempt to detect loops requires blocking all other traffic for a short time. Though this is short, it is usually long enough to cause corosync to think that the peer node has failed, triggering a fence action.

Nyz: /* RAM - Preparing for Degradation */

2016-01-05T15:18:20Z

RAM - Preparing for Degradation

← Older revision		Revision as of 15:18, 5 January 2016
Line 204:		Line 204:
	=== RAM - Preparing for Degradation ===		=== RAM - Preparing for Degradation ===

	RAM is a far simpler topic than storage, thankfully. Here, all you need to do is add up how much RAM you plan to assign to servers, add at least 2 [[GiB]] for the host, and then install that much memory in both of your nodes.		RAM is a far simpler topic than storage, thankfully. Here, all you need to do is add up how much RAM you plan to assign to servers, add at least 2 [[GiB]] for the host (we recommend 4), and then install that much memory in both of your nodes.

	In production, there are two technologies you will want to consider;		In production, there are two technologies you will want to consider;

Digimer: /* Initializing vm04-win8's Install */

2015-09-10T17:06:24Z

Initializing vm04-win8's Install

← Older revision		Revision as of 17:06, 10 September 2015
Line 13,787:		Line 13,787:
	[[Image:AN!Cluster_Tutorial_2-vm04-win8_03.png\|thumb\|900px\|center\|The <span class="code">vm04-win8</span> server doesn't see its hard drive.]]		[[Image:AN!Cluster_Tutorial_2-vm04-win8_03.png\|thumb\|900px\|center\|The <span class="code">vm04-win8</span> server doesn't see its hard drive.]]

	This was expected because ~~windows 2008~~ does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.		{{warning\|1=Since this tutorial was written, the virtio project has significantly changed the directory structure where drivers are held. The storage drivers are now found in <span class="code">viostor/w8/amd64/</span>. The trick of loading the other drivers is still possible by loading the "wrong" driver, one at a time, but it is quite a bit easier to now load the network and other drivers after the install completes. To do so, go to "Device Manager" and select the devices with a yellow exclamation mark, choose to update their drivers and tell it to search all subdirectories on the "dvd".}}

			This was expected because Windows 8 does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.

	Click on "Load Driver" on the bottom right.		Click on "Load Driver" on the bottom right.

Digimer: /* Initializing vm03-win7's Install */

2015-09-10T17:05:09Z

Initializing vm03-win7's Install

← Older revision		Revision as of 17:05, 10 September 2015
Line 13,570:		Line 13,570:

	[[Image:AN!Cluster_Tutorial_2-vm03-win7_02.png\|thumb\|900px\|center\|Installation of <span class="code">vm03-win7</span> begins!]]		[[Image:AN!Cluster_Tutorial_2-vm03-win7_02.png\|thumb\|900px\|center\|Installation of <span class="code">vm03-win7</span> begins!]]

			{{warning\|1=Since this tutorial was written, the virtio project has significantly changed the directory structure where drivers are held. The storage drivers are now found in <span class="code">viostor/w7/amd64/</span>. The trick of loading the other drivers is still possible by loading the "wrong" driver, one at a time, but it is quite a bit easier to now load the network and other drivers after the install completes. To do so, go to "Device Manager" and select the devices with a yellow exclamation mark, choose to update their drivers and tell it to search all subdirectories on the "dvd".}}

	Follow the install process, entering the values you want. When you get to the install target screen, you will see that Windows can't find the hard drive.		Follow the install process, entering the values you want. When you get to the install target screen, you will see that Windows can't find the hard drive.

Digimer: /* Initializing vm02-win2012's Install */

2015-09-10T17:03:52Z

Initializing vm02-win2012's Install

← Older revision		Revision as of 17:03, 10 September 2015
Line 13,365:		Line 13,365:

	[[Image:AN!Cluster_Tutorial_2-vm02-win2012_03.png\|thumb\|900px\|center\|The <span class="code">vm02-win2012</span> server doesn't see its hard drive.]]		[[Image:AN!Cluster_Tutorial_2-vm02-win2012_03.png\|thumb\|900px\|center\|The <span class="code">vm02-win2012</span> server doesn't see its hard drive.]]

			{{warning\|1=Since this tutorial was written, the virtio project has significantly changed the directory structure where drivers are held. The storage drivers are now found in <span class="code">viostor/2k12R2/amd64/</span>. The trick of loading the other drivers is still possible by loading the "wrong" driver, one at a time, but it is quite a bit easier to now load the network and other drivers after the install completes. To do so, go to "Device Manager" and select the devices with a yellow exclamation mark, choose to update their drivers and tell it to search all subdirectories on the "dvd".}}

	This was expected because windows 2008 does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.		This was expected because windows 2008 does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.

Digimer: /* Initializing vm01-win2008's Install */

2015-09-10T17:02:16Z

Initializing vm01-win2008's Install

← Older revision		Revision as of 17:02, 10 September 2015
Line 13,158:		Line 13,158:
	This was expected because windows 2008 does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.		This was expected because windows 2008 does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.

	{{warning\|1=Since this tutorial was written, the virtio project has significantly changed the directory structure where drivers are held. The storage drivers are now found in <span class="code">viostor/w7/amd64/</span>. The trick of loading the other drivers is still possible by loading the "wrong" driver, one at a time, but it is quite a bit easier to now load the network and other drivers after the install completes. To do so, go to "Device Manager" and select the devices with a yellow exclamation mark, choose to update their drivers and tell it to search all subdirectories on the "dvd".}}		{{warning\|1=Since this tutorial was written, the virtio project has significantly changed the directory structure where drivers are held. The storage drivers are now found in <span class="code">viostor/2k8/amd64/</span>. The trick of loading the other drivers is still possible by loading the "wrong" driver, one at a time, but it is quite a bit easier to now load the network and other drivers after the install completes. To do so, go to "Device Manager" and select the devices with a yellow exclamation mark, choose to update their drivers and tell it to search all subdirectories on the "dvd".}}

	Click on "Load Driver" on the bottom right.		Click on "Load Driver" on the bottom right.

Digimer: /* Initializing vm01-win2008's Install */

2015-09-10T17:01:08Z

Initializing vm01-win2008's Install

← Older revision		Revision as of 17:01, 10 September 2015
Line 13,157:		Line 13,157:

	This was expected because windows 2008 does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.		This was expected because windows 2008 does not natively support <span class="code">virtio</span>. That's why we used two virtual cd-rom drives and "inserted" the <span class="code">virtio</span> driver disk into the second drive.

			{{warning\|1=Since this tutorial was written, the virtio project has significantly changed the directory structure where drivers are held. The storage drivers are now found in <span class="code">viostor/w7/amd64/</span>. The trick of loading the other drivers is still possible by loading the "wrong" driver, one at a time, but it is quite a bit easier to now load the network and other drivers after the install completes. To do so, go to "Device Manager" and select the devices with a yellow exclamation mark, choose to update their drivers and tell it to search all subdirectories on the "dvd".}}

	Click on "Load Driver" on the bottom right.		Click on "Load Driver" on the bottom right.

Digimer: /* Provisioning vm01-win2008 */

2015-09-10T16:34:37Z

Provisioning vm01-win2008

← Older revision		Revision as of 16:34, 10 September 2015
Line 12,969:		Line 12,969:
	\|style="white-space: nowrap;"\|<syntaxhighlight lang="bash">		\|style="white-space: nowrap;"\|<syntaxhighlight lang="bash">
	cd /shared/files/		cd /shared/files/
	wget -c https://~~alt.fedoraproject~~.org/~~pub~~/~~alt~~/virtio-win/stable/virtio-win~~-0.1-74~~.iso		wget -c https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
	cd ~		cd ~
	</syntaxhighlight>		</syntaxhighlight>
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	--~~2014~~-04-~~28 18~~:01:10-- https://~~alt.fedoraproject~~.org/~~pub~~/~~alt~~/virtio-win/stable/virtio-win~~-0.1-74~~.iso		--2015-09-10 12:24:17-- https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
	Resolving ~~alt~~.~~fedoraproject~~.~~org (alt~~.~~fedoraproject~~.org)... ~~209~~.~~132~~.~~181~~.27, ~~209~~.~~132~~.~~181~~.~~23, 209~~.~~132~~.~~181~~.24, ...		Resolving fedorapeople.org... 152.19.134.196, 2610:28:3090:3001:5054:ff:feff:683f
	~~Connecting~~ to ~~alt~~.~~fedoraproject~~.org ~~(alt~~.~~fedoraproject~~.org~~)\|209~~.~~132~~.~~181~~.~~27\|:443~~... ~~connected~~.		Connecting to fedorapeople.org\|152.19.134.196\|:443... connected.
			HTTP request sent, awaiting response... 301 Moved Permanently
			Location: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.102/virtio-win.iso [following]
			--2015-09-10 12:24:17-- https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.102/virtio-win.iso
			Reusing existing connection to fedorapeople.org:443.
			HTTP request sent, awaiting response... 301 Moved Permanently
			Location: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.102/virtio-win-0.1.102.iso [following]
			--2015-09-10 12:24:17-- https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.102/virtio-win-0.1.102.iso
			Reusing existing connection to fedorapeople.org:443.
	HTTP request sent, awaiting response... 200 OK		HTTP request sent, awaiting response... 200 OK
	Length: ~~61272064~~ (~~58M~~) [application/octet-stream]		Length: 160755712 (153M) [application/octet-stream]
	Saving to: ~~‘virtio~~-win~~-0.1-74~~.~~iso’~~		Saving to: `virtio-win.iso'

	100%[======================================>] 61,~~272~~,~~064 5~~.~~23MB~~/s in ~~15s~~		100%[====================================================================>] 160,755,712 1.11M/s in 2m 36s

	~~2014~~-04-~~28 18~~:01:26 (~~3.86 MB~~/s) - ~~‘virtio~~-win-0.1-74.~~iso’ saved [61272064~~/~~61272064]~~		2015-09-10 12:26:54 (1004 KB/s) - `virtio-win.iso' saved [160755712/160755712]
			</syntaxhighlight>
			\|}

			Note that the original file name was <span class="code">virtio-win-0.1.102</span>, but the downloaded file ended up being called <span class="code">virtio-win.iso</span>? Lets fix that so we know down the road the version we have. We'll also make sure the file is world-readable.

			{\|class="wikitable"
			!<span class="code">an-a05n01</span>
			\|style="white-space: nowrap;"\|<syntaxhighlight lang="bash">
			mv /shared/files/virtio-win.iso /shared/files/virtio-win-0.1.102.iso
			chmod 644 /shared/files/virtio-win-0.1.102.iso
	</syntaxhighlight>		</syntaxhighlight>
	\|-		\|-
Line 12,993:		Line 13,011:
	drwxr-xr-x. 2 root root 3.8K Nov 2 10:48 .		drwxr-xr-x. 2 root root 3.8K Nov 2 10:48 .
	drwxr-xr-x. 6 root root 3.8K Nov 1 01:23 ..		drwxr-xr-x. 6 root root 3.8K Nov 1 01:23 ..
	-rw-r--r-- 1 root root ~~59M Nov 20 15~~:08 virtio-win-0.1~~-74~~.iso		-rw-r--r-- 1 root root 154M Apr 26 18:25 virtio-win-0.1.102.iso
	-rw-rw-r--. 1 qemu qemu 3.0G Oct 14 2011 Windows_Svr_2008_R2_64Bit_SP1.ISO		-rw-rw-r--. 1 qemu qemu 3.0G Oct 14 2011 Windows_Svr_2008_R2_64Bit_SP1.ISO
	</syntaxhighlight>		</syntaxhighlight>

Digimer: /* Configuring Apcupsd For Two UPSes */

2015-07-07T17:26:34Z

Configuring Apcupsd For Two UPSes

← Older revision		Revision as of 17:26, 7 July 2015
Line 5,445:		Line 5,445:

	# Change the variables		# Change the variables
	sed -i "s/^UPSNAME.*/UPSNAME ${~~ups~~}/" /etc/apcupsd/apcupsd.${~~ups~~}.conf		sed -i "s/^UPSNAME.*/UPSNAME ${ups2}/" /etc/apcupsd/apcupsd.${ups2}.conf
	sed -i "s/^DEVICE.*/DEVICE ${~~ups~~}.${domain}:161:APC_NOTRAP:private/" /etc/apcupsd/apcupsd.${~~ups~~}.conf		sed -i "s/^DEVICE.*/DEVICE ${ups2}.${domain}:161:APC_NOTRAP:private/" /etc/apcupsd/apcupsd.${ups2}.conf
	sed -i "s/^NISPORT.*/NISPORT 3552/" /etc/apcupsd/apcupsd.${~~ups~~}.conf		sed -i "s/^NISPORT.*/NISPORT 3552/" /etc/apcupsd/apcupsd.${ups2}.conf
	sed -i "s/^EVENTSFILE .*/EVENTSFILE \/var\/log\/apcupsd.${~~ups~~}.events/" /etc/apcupsd/apcupsd.${~~ups~~}.conf		sed -i "s/^EVENTSFILE .*/EVENTSFILE \/var\/log\/apcupsd.${ups2}.events/" /etc/apcupsd/apcupsd.${ups2}.conf
	diff -u /etc/apcupsd/apcupsd.${ups2}.conf /etc/apcupsd/apcupsd.${ups}.conf		diff -u /etc/apcupsd/apcupsd.${ups2}.conf /etc/apcupsd/apcupsd.${ups}.conf
	</syntaxhighlight>		</syntaxhighlight>