Anvil! m2 Tutorial - Revision history

Digimer: /* A machine for Striker */

2015-11-11T19:13:36Z

A machine for Striker

← Older revision		Revision as of 19:13, 11 November 2015
Line 73:		Line 73:
	{\|style="width: 100%;"		{\|style="width: 100%;"
	\|style="width: 710px"\|[[image:Fujitsu_Primergy_RX1330-M1_Front-Left.jpg\|thumb\|center\|700px\|Fujitsu Primergy [http://www.fujitsu.com/fts/products/computing/servers/primergy/rack/rx1330m1/ RX1330 M1]; Photo by [http://mediaportal.ts.fujitsu.com/pages/view.php?ref=33902&k= Fujitsu].]]		\|style="width: 710px"\|[[image:Fujitsu_Primergy_RX1330-M1_Front-Left.jpg\|thumb\|center\|700px\|Fujitsu Primergy [http://www.fujitsu.com/fts/products/computing/servers/primergy/rack/rx1330m1/ RX1330 M1]; Photo by [http://mediaportal.ts.fujitsu.com/pages/view.php?ref=33902&k= Fujitsu].]]
	\|[[image:~~ASUS_EeeBox_PX1035~~.~~jpg~~\|thumb\|center\|200px\|[http://www.~~asus~~.com/~~ca-~~en/~~EeeBox_PCs~~/~~EeeBox_PC_EB1035/ ASUS EeeBox PC1035~~]; Photo by [http://www.~~asus~~.com/ca-en/ ~~ASUSTEK~~].]]		\|[[image:Intel_NUC_NUC5i5RYH.png\|thumb\|center\|200px\|[http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i5ryh.html Intel NUC NUC5i5RYH]; Photo by [http://www.intel.com/content/dam/www/public/us/en/images/photography-consumer/16x9/65596-tall-nuc-kit-i5-i3-ry-frontangle-white-16x9.png/_jcr_content/renditions/intel.web.256.144.png Intel].]]
	\|}		\|}

Line 79:		Line 79:

	We have used;		We have used;
	* ~~Very light-weight~~ machines like the [http://www.~~asus~~.com/~~ca-~~en/~~EeeBox_PCs~~/~~EeeBox_PC_EB1035/ ASUS EeeBox~~] with a simple [http://~~store~~.~~apple~~.com/ca/~~product~~/~~MC704ZM~~/~~A/apple~~-~~usb~~-ethernet-adapter ~~Apple~~ USB ethernet] adapter.		* Small but powerful machines like the [http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5i5ryh.html Intel Core i5 NUC NUC5i5RYH] with a simple [http://www.siig.com/it-products/networking/wired/usb-3-0-to-gigabit-ethernet-adapter.html Siig JU-NE0211-S1 USB 3.0 to gigabit ethernet] adapter.
	* On the other end of the scale, we've used fully redundant [http://www.fujitsu.com/fts/products/computing/servers/primergy/rack/rx1330m1/ Fujitsu Primergy RX 1330 M1] servers with four network interfaces. The decision here will be principally guided by your budget.		* On the other end of the scale, we've used fully redundant [http://www.fujitsu.com/fts/products/computing/servers/primergy/rack/rx1330m1/ Fujitsu Primergy RX 1330 M1] servers with four network interfaces. The decision here will be principally guided by your budget.

Digimer: /* Configure the Foundation Pack Backup Fencing */

2015-03-24T20:14:21Z

Configure the Foundation Pack Backup Fencing

← Older revision		Revision as of 20:14, 24 March 2015
Line 189:		Line 189:
	* [[Configuring an APC AP7900]]		* [[Configuring an APC AP7900]]
	* [[Configuring Brocade Switches]]		* [[Configuring Brocade Switches]]
	* [[Configuring APC SmartUPS with ~~AP7930~~ Network Cards]]		* [[Configuring APC SmartUPS with AP9630 Network Cards]]

	== Create an "Install Manifest" ==		== Create an "Install Manifest" ==

Digimer: /* Preparing the Anvil! Nodes */

2015-01-05T17:57:52Z

Preparing the Anvil! Nodes

← Older revision		Revision as of 17:57, 5 January 2015
Line 175:		Line 175:

	Some mini tutorials that might be helpful:		Some mini tutorials that might be helpful:
	* [[Configuring Fujitsu ~~Nodes~~]]		* [[Configuring Network Boot on Fujitsu Primergy]]
	* [[Configuring Hardware RAID Arrays on Fujitsu Primergy]]		* [[Configuring Hardware RAID Arrays on Fujitsu Primergy]]
	* [[Encrypted Arrays with LSI SafeStore]] (Also covers '<span class="code">[https://github.com/digimer/striker/blob/master/tools/anvil-self-destruct anvil-self-destruct]</span>')		* [[Encrypted Arrays with LSI SafeStore]] (Also covers '<span class="code">[https://github.com/digimer/striker/blob/master/tools/anvil-self-destruct anvil-self-destruct]</span>')

Digimer: /* Preparing the Anvil! Nodes */

2015-01-05T17:56:49Z

Preparing the Anvil! Nodes

← Older revision		Revision as of 17:56, 5 January 2015
Line 176:		Line 176:
	Some mini tutorials that might be helpful:		Some mini tutorials that might be helpful:
	* [[Configuring Fujitsu Nodes]]		* [[Configuring Fujitsu Nodes]]
	* [[Configuring ~~LSI~~ RAID ~~Controllers~~]]		* [[Configuring Hardware RAID Arrays on Fujitsu Primergy]]
	* [[Encrypted Arrays with LSI SafeStore]] (Also covers '<span class="code">[https://github.com/digimer/striker/blob/master/tools/anvil-self-destruct anvil-self-destruct]</span>')		* [[Encrypted Arrays with LSI SafeStore]] (Also covers '<span class="code">[https://github.com/digimer/striker/blob/master/tools/anvil-self-destruct anvil-self-destruct]</span>')

Digimer at 03:42, 5 January 2015

2015-01-05T03:42:44Z

← Older revision		Revision as of 03:42, 5 January 2015
Line 88:		Line 88:
	The more fault-tolerant, the better!		The more fault-tolerant, the better!

	The ''Anvil!'' Nodes host power your highly-available servers, but the servers themselves are totally decoupled from the hardware. You can move your servers back and forth between these nodes without any interruption. In a node ~~explodes~~ without warning, the survivor will reboot your servers within seconds ensuring the most minimal service interruptions (typical recovery time from node crash to server being at the login prompt is 30 to 90 seconds).		The ''Anvil!'' Nodes host power your highly-available servers, but the servers themselves are totally decoupled from the hardware. You can move your servers back and forth between these nodes without any interruption. If a node catastrophically fails without warning, the survivor will reboot your servers within seconds ensuring the most minimal service interruptions (typical recovery time from node crash to server being at the login prompt is 30 to 90 seconds).

	{\|style="width: 100%;"		{\|style="width: 100%;"
Line 158:		Line 158:
	== Preparing the Anvil! Nodes ==		== Preparing the Anvil! Nodes ==

	{{Note\|1=Every server vendor has it's own way to configure a node's BIOS and storage. For this reason, we're skipping that part here. Please consult your manual to enable network booting and for creating your storage array.}}		{{Note\|1=Every server vendor has it's own way to configure a node's BIOS and storage. For this reason, we're skipping that part here. Please consult your server or motherboard manual to enable network booting and for creating your storage array.}}

	It's rather difficult ~~to borderline-impossible~~ to fully automate the node install process, but Striker does automate the vast majority of it.		It's rather difficult to fully automate the node install process, but Striker does automate the vast majority of it.

	It simplifies the few manual parts by automatically becoming a simple menu-driven target for operating system installs.		It simplifies the few manual parts by automatically becoming a simple menu-driven target for operating system installs.
Line 221:		Line 221:
	= Building a Striker Dashboard =		= Building a Striker Dashboard =

	We recommend [https://access.redhat.com/products/red-hat-enterprise-linux/evaluation Red Hat Enterprise Linux] (RHEL), but you can also use the free, [http://wiki.centos.org/FAQ/General#head-4b2dd1ea6dcc1243d6e3886dc3e5d1ebb252c194 binary-compatible] rebuild called [[CentOS]]. Collectively these (and other RHEL-based operating systems) are often call "EL" (for "Enterprise Linux"). We will be using release version 6, which is ~~shorted~~ to simple '''EL6'''.		We recommend [https://access.redhat.com/products/red-hat-enterprise-linux/evaluation Red Hat Enterprise Linux] (RHEL), but you can also use the free, [http://wiki.centos.org/FAQ/General#head-4b2dd1ea6dcc1243d6e3886dc3e5d1ebb252c194 binary-compatible] rebuild called [[CentOS]]. Collectively these (and other RHEL-based operating systems) are often call "EL" (for "Enterprise Linux"). We will be using release version 6, which is abbreviated to simple '''EL6'''.

	== Installing the Operating System ==		== Installing the Operating System ==
Line 235:		Line 235:
	== Download the Striker Installer ==		== Download the Striker Installer ==

	The Striker installer is a small "command line" program that you download and run~~. It looks a little intimidating at first, but it's actually quite easy to use~~.		The Striker installer is a small "command line" program that you download and run.

	We need to download it from the Internet. You can download it in your browser [https://raw.githubusercontent.com/digimer/striker/master/tools/striker-installer by clicking here], if you like.		We need to download it from the Internet. You can download it in your browser [https://raw.githubusercontent.com/digimer/striker/master/tools/striker-installer by clicking here], if you like.
Line 272:		Line 272:
	</syntaxhighlight>		</syntaxhighlight>

	See the '<span class="code">-rwxr-xr-x.</span>' line? That tells use that the file is ~~not~~ 'e<span class="code">x</span>ecutable'.		See the '<span class="code">-rwxr-xr-x.</span>' line? That tells use that the file is now 'e<span class="code">x</span>ecutable'.

	We're ready!		We're ready!
Line 329:		Line 329:
	One of the really nice features of Striker dashboards is that you can use them to automatically install the base operating system on new and replacement ''Anvil!'' nodes.		One of the really nice features of Striker dashboards is that you can use them to automatically install the base operating system on new and replacement ''Anvil!'' nodes.

	To do this, Striker can be told to setup a "<span class="code">[[PXE]]</span>" (''P're-e''C''ecution ''E''nvironment) server. When this is enabled, you can tell a new node to "boot off the network". Doing this allows you to boot and install an operating system without using a boot disc. Also, it allows us to specify special install instruction, removing the need to ask you how you want to configure the OS.		To do this, Striker can be told to setup a "<span class="code">[[PXE]]</span>" (''P're-boot e''X''ecution ''E''nvironment) server. When this is enabled, you can tell a new node to "boot off the network". Doing this allows you to boot and install an operating system without using a boot disc. Also, it allows us to specify special install instruction, removing the need to ask you how you want to configure the OS.

	The Striker dashboard will do everything for you to be an install target.		The Striker dashboard will do everything for you to be an install target.
Line 366:		Line 366:
	If you want to know more about how networks are used in the ''Anvil!'', please see:		If you want to know more about how networks are used in the ''Anvil!'', please see:

	* "[[AN!Cluster_Tutorial_2#Planning_The_Use_of_Physical_Interfaces\|Planning The Use of Physical Interfaces]]" ~~over on~~ the main tutorial		* "[[AN!Cluster_Tutorial_2#Planning_The_Use_of_Physical_Interfaces\|Planning The Use of Physical Interfaces]]" in the main tutorial

	If your Striker dashboard has just two network interfaces, then the first will ask you which interface plugs into your [[Back-Channel Network]] and then which one plugs into your [[Internet-Facing Network]].		If your Striker dashboard has just two network interfaces, then the first will ask you which interface plugs into your [[Back-Channel Network]] and then which one plugs into your [[Internet-Facing Network]].
Line 385:		Line 385:
	If the '<span class="code">value</span>' has a space in it, then we'll put quotes around it.		If the '<span class="code">value</span>' has a space in it, then we'll put quotes around it.

	If you want to know more about the switches, you can run '<span class="code">./striker-installer</span>' by itself and all the available switches and how to use them will be explained~~. This tutorial isn't meant to be comprehensive though, so we're not going to go into all the ways we can use the installer~~.		If you want to know more about the switches, you can run '<span class="code">./striker-installer</span>' by itself and all the available switches and how to use them will be explained.

	{{note\|1=This uses the 'git' repository option. It will be redone later without this option once version 1.2.0 is released. Please do not use 'git' versions in production!}}		{{note\|1=This uses the 'git' repository option. It will be redone later without this option once version 1.2.0 is released. Please do not use 'git' versions in production!}}
Line 410:		Line 410:
	\|class="code"\|-m		\|class="code"\|-m
	\|class="code"\|mail.alteeve.ca:587		\|class="code"\|mail.alteeve.ca:587
	\|The name and port number of the mail server do we ~~go to send~~ email to.		\|The server name and [[TCP]] port number of the mail server we route email to.
	\|-		\|-
	\|Email user		\|Email user
Line 472:		Line 472:
	</syntaxhighlight>		</syntaxhighlight>

	~~That was the hardest part, and it wasn't really hard, was it?~~		Done!

	When you press <span class="code"><enter></span>, the install will start.		When you press <span class="code"><enter></span>, the install will start.
Line 778:		Line 778:

	[[image:Striker-1.2.0b_Install-Manifest_Blank-Form.png\|thumb\|center\|665px\|Striker - Install Manifest - Blank form]]		[[image:Striker-1.2.0b_Install-Manifest_Blank-Form.png\|thumb\|center\|665px\|Striker - Install Manifest - Blank form]]

	~~'''Holy form Batman!'''~~

	Don't worry, we only need to set the fields in the top, and Striker will auto-fill the rest.		Don't worry, we only need to set the fields in the top, and Striker will auto-fill the rest.

Digimer at 07:54, 4 January 2015

2015-01-04T07:54:06Z

Show changes

Digimer at 07:49, 4 January 2015

2015-01-04T07:49:25Z

← Older revision		Revision as of 07:49, 4 January 2015
Line 2:		Line 2:

	{{warning\|1=This tutorial is '''NOT''' complete! It is being written using [[Striker]] version <span class="code">1.2.0 β</span>. Things may change between now and final release.}}		{{warning\|1=This tutorial is '''NOT''' complete! It is being written using [[Striker]] version <span class="code">1.2.0 β</span>. Things may change between now and final release.}}

			'''How to build an '''''Anvil!''''' from scratch in under a day!'''

	I hear you now; "''Oh no, another book!''"		I hear you now; "''Oh no, another book!''"

Digimer: /* Understanding the output = */

2015-01-04T07:46:28Z

Understanding the output =

← Older revision		Revision as of 07:46, 4 January 2015
Line 1,287:		Line 1,287:
	There is now nothing more for you to do, so long as nothing fails. '''If''' something fails, correct the error and then re-run the install. Striker tries to be smart enough to figure out what part of the install was already completely and pick up where it left off on subsequent runs.		There is now nothing more for you to do, so long as nothing fails. '''If''' something fails, correct the error and then re-run the install. Striker tries to be smart enough to figure out what part of the install was already completely and pick up where it left off on subsequent runs.

	=== Understanding the output ====		=== Understanding the output ===

	{{warning\|1=The install process can '''take a long time''' to run, please don't interrupt it!		{{warning\|1=The install process can '''take a long time''' to run, please don't interrupt it!

Digimer: /* Understanding the output = */

2015-01-04T07:46:18Z

Understanding the output =

← Older revision		Revision as of 07:46, 4 January 2015
Line 1,382:		Line 1,382:
	\|The ''Anvil!'' uses a small amount of space, 40 [[GiB]] by default, for storing server definition files, provision scripts and install media (DVD images). This step carves a small "Logical Volume" ([[LV]]) out of the first storage pool's [[VG]].		\|The ''Anvil!'' uses a small amount of space, 40 [[GiB]] by default, for storing server definition files, provision scripts and install media (DVD images). This step carves a small "Logical Volume" ([[LV]]) out of the first storage pool's [[VG]].
	\|-		\|-
	\|style="color: #13749a; font-weight: bold;"\|		\|style="color: #13749a; font-weight: bold;"\|Create Clustered Filesystem
	\|		\|The [[LV]] from the previous step is, basically, raw storage. This step formats it with the [[GFS2]] filesystem which allows for the data on it to be accessed by both nodes at the same time.
	\|-		\|-
	\|style="color: #13749a; font-weight: bold;"\|		\|style="color: #13749a; font-weight: bold;"\|Configure FS Table
	\|		(mislabelled in the screen shot)
			\|If the cluster filesystem was created, the information about this new filesystem is added the each node's central file system table.
	\|-		\|-
	\|style="color: #13749a; font-weight: bold;"\|		\|style="color: #13749a; font-weight: bold;"\|Starting the storage service
	\|		\|With the storage now configured and running, it is now placed under the cluster's management and control.
	\|-		\|-
	\|style="color: #13749a; font-weight: bold;"\|		\|style="color: #13749a; font-weight: bold;"\|Starting the hypervisor
	\|		\|This enables virtualization layer needed for the ''Anvil!'' to host servers.
			\|-
			\|style="color: #13749a; font-weight: bold;"\|Updating system password
			\|This is the last stage of the install! Here, the '<span class="code">root</span>' password on each node is changed to match that defined in the install manifest.
	\|}		\|}

	~~<span class="code"></span>~~		Done!
	~~<syntaxhighlight lang="bash">~~
	~~</syntaxhighlight>~~		Your ''Anvil!'' is now ready to be added to Striker.
	~~<syntaxhighlight lang="text">~~
	~~</syntaxhighlight>~~

	{{footer}}		{{footer}}

Digimer: /* Understanding the output = */

2015-01-04T07:35:56Z

Understanding the output =

@@ Line 1,319: / Line 1,319: @@
 |{{note|1=This is usually the longest stage of the install, please be patient.}}
 At this stage, all additional software that is needed for the ''Anvil!'' nodes to work is installed. This requires a pretty large download which, depending on the speed of your Internet connection, could take a very long time to complete. Using a [[Anvil! m2 Tutorial - Create Local Repositories|local repository]] can greatly speed this stage up.
 |-
 |style="color: #13749a; font-weight: bold;"|