Building an Anvil m2

From Alteeve Wiki
Revision as of 18:00, 26 February 2013 by Digimer (talk | contribs) (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 ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

 AN!Wiki :: How To :: Building an Anvil m2

Warning: This is incomplete. Please do not follow this tutorial until this warning is removed!
Note: 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 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;

Hardware

The hardware used in this tutorial is;

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

  1. 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.
    1. Note: AN!CM was written to support LSI-brand RAID controllers using the MegaCLI64 tool.
    2. Note: AN!CM was tested against IPMI values returned by Fujitsu-brand servers.
      1. If you use other brands, updates to AN!CM may be required.
  2. Your switches need to support persistent multicast groups. Most simple, unmanaged switches do this. Some higher-end ones require static multicast groups be assigned.
  3. Your switched PDU needs to have a fence agent usable by the cluster. You can check here if yours does.
  4. In order to monitor the UPSes, you need to use a network-able UPS that supports apcupsd.
  5. 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

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche! Enterprise Support:
Alteeve Support
Community Support
© Alteeve's Niche! Inc. 1997-2024   Anvil! "Intelligent Availability®" Platform
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.