Building an Anvil m2 - Revision history

Digimer: /* Network */

2013-02-26T21:19:22Z

Network

Show changes

Digimer: /* Network */

2013-02-26T21:07:03Z

Network

Show changes

Digimer at 19:05, 26 February 2013

2013-02-26T19:05:33Z

@@ Line 4: / Line 4: @@
 {{note|1=This is an updated version of [[2-Node Red Hat KVM Cluster Tutorial]] that adds support for the [[AN!CDB]] cluster dashboard. It also uses some tools to simplify the setup of nodes.}}
 This tutorial will help you build an Anvil Mark-2. It differs from the [[2-Node Red Hat KVM Cluster Tutorial| previous tutorial]] in that it does not focus on learning the foundation of the cluster. Instead, it's focus is to help you create a reliable platform for your servers.
@@ Line 27: / Line 29: @@
 == Hardware ==
 The hardware used in this tutorial is;
@@ Line 54: / Line 58: @@
 = The Setup =

Digimer: Created page with "{{howto_header}} {{warning|1=This is incomplete. Please do not follow this tutorial until this warning is removed!}} {{note|1=This is an updated version of [[2-Node Red Hat ..."

2013-02-26T18:00:23Z

Created page with "{{howto_header}} {{warning|1=This is incomplete. Please do not follow this tutorial until this warning is removed!}} {{note|1=This is an updated version of [[2-Node Red Hat ..."

Páàjì titun

{{howto_header}}

{{warning|1=This is incomplete. Please do not follow this tutorial until this warning is removed!}}

{{note|1=This is an updated version of [[2-Node Red Hat KVM Cluster Tutorial]] that adds support for the [[AN!CDB]] cluster dashboard. It also uses some tools to simplify the setup of nodes.}}

This tutorial will help you build an Anvil Mark-2. It differs from the [[2-Node Red Hat KVM Cluster Tutorial| previous tutorial]] in that it does not focus on learning the foundation of the cluster. Instead, it's focus is to help you create a reliable platform for your servers.

Think of this tutorial as a recipe for making a great cake, rather than learning the chemistry behind baking.

= Before We Start =

== The Task Ahead ==

We will be building up two servers, on redundant power and networking, to create a highly-available, highly fault-tolerant platform for virtual servers.

It will be built on 100% open-source software.

Specifically, we will be using;

* [[Red Hat Enterprise Linux]] or [[CentOS]] version 6.
** Red Hat Resilient Storage (including High-Availability Add-On) for automatic recovery
** KVM + qemu as the [[hypervisor]]
* Linbit's [[DRBD]] for replicated storage.
* [[AN!CDB]] for Anvil m2 management.
* [[AN!CM]] for hardware health monitoring.

== Hardware ==

The hardware used in this tutorial is;

* Two [http://www.fujitsu.com/fts/products/computing/servers/primergy/rack/rx300/ Fujitsu RX300] S6 nodes with redundant power supplies.
* Two [http://www.dlink.com/ca/en/support/product/dgs-3120-24tc-si D-Link DGS-3120-24TC/SI] switches, stacked.
* Two [http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=AP7900 APC AP7900] switched [[PDU]]s.
* Two [http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SMT1500RM2U APC SMT1500] [[UPS]]es, each with an [http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=AP9630 AP9630] network management card.
* One [http://ca.asus.com/en/Eee/EeeBox_PC/EeeBox_PC_EB1021/ ASUS EeeBox EB1021] appliance server for the [[AN!CDB]] dashboard.

You may, of course, use other hardware. However, you need to ensure a few things;

# Your nodes need to have out-of-band management. This is usually provided via an [[IPMI]] controller, or an [[OEM]] version, like HP's [[iLO]], Dell's [[iDRAC]] or similar.
## Note: [[AN!CM]] was written to support [http://www.lsi.com/Pages/default.aspx LSI-brand] [[RAID]] controllers using the [[MegaCLI64]] tool.
## Note: [[AN!CM]] was tested against [[IPMI]] values returned by Fujitsu-brand servers.
### If you use other brands, updates to [https://github.com/digimer/an-cdb/blob/master/tools/an-cm AN!CM] may be required.
# Your switches need to support persistent [[multicast]] groups. Most simple, unmanaged switches do this. Some higher-end ones require static multicast groups be assigned.
# Your switched PDU needs to have a [[fence agent]] usable by the cluster. You can [https://access.redhat.com/knowledge/articles/28603 check here] if yours does.
# In order to monitor the [[UPS]]es, you need to use a network-able UPS that supports [[Setup apcupsd For Multiple Network-Enabled APC UPSes On EL6| apcupsd]].
# [[AN!CDB]] needs to run on a 64-bit CPU and on a machine that properly supports [[RHEL6]] with at least two network cards.

If you run into problems using other hardware, please [[contact us]] and we will do our best to help get the Anvil m2 working on your platform.

== Prerequisites ==

This tutorial assumes it's readers be familiar with basic command-line Linux tools. You will need to be familiar with networking concepts and terms. It uses [[vim]] as the default editor, though readers can safely substitute their preferred text editor, provided it uses standard unix-style line wrapping. Where ever possible, commands and shortcuts will be explained in detail.

= The Setup =

{{footer}}