|
|
(32 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
− | QWERTYU SDFGHJ
| |
| | | |
− | == BDII setup on active/passive failover cluster ==
| |
− |
| |
− | == Generic active/passive clusters ==
| |
− | Configuring a cluster using corosync and heartbeat means you have to write a start/stop and monitoring script for the service you are building the cluster for.
| |
− |
| |
− | This script is very much like an "init.d" script, but you can't directly use an init.d script as heartbeat scripts use tri-state logic in stead of two-state logic. I.e., heartbeat controlled services are "running", "stopped" or "failed".
| |
− |
| |
− |
| |
− |
| |
− |
| |
− | == Install the cluster engine & resource manager ==
| |
− | You need to perform the installation on each cluster node.
| |
− |
| |
− | Add the EPEL repo to /etc/yum.repos.d:
| |
− | # rpm -Uhv http://download.fedora.redhat.com/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm
| |
− |
| |
− | Add the Clusterlabs repo to /etc/yum.repos.d:
| |
− | # wget -O /etc/yum.repos.d/pacemaker.repo http://clusterlabs.org/rpm/epel-5/clusterlabs.repo
| |
− |
| |
− | Now have yum install the cluster engine and resource managers. This will install loads of dependencies:
| |
− | # yum -y install pacemaker
| |
− |
| |
− | == Configure the cluster engine ==
| |