WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Using Pacemaker with Lustre: Difference between revisions

From Obsolete Lustre Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 14: Line 14:
* ''Pacemaker 1.0 Configuration Explained'' at [http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained].
* ''Pacemaker 1.0 Configuration Explained'' at [http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained].
* M. Schwartzkopff, ''Clusterbau: Hochverfügbarkeit mit pacemaker, OpenAIS, heartbeat und LVS'', O'Reilly Vlg. Gmbh & Co., Dec 2009. (German)
* M. Schwartzkopff, ''Clusterbau: Hochverfügbarkeit mit pacemaker, OpenAIS, heartbeat und LVS'', O'Reilly Vlg. Gmbh & Co., Dec 2009. (German)
==== Setting Up the corosync Communication Stack ====
The ''corosync'' communication stack, developed as part of the OpenAIS project, supports all the communication needs of the cluster. The package is included in all recent Linux distributions. If it is not included in your distribution, you can find precompiled binaries at [http://www.clusterlabs.org/rpm www.clusterlabs.org/rpm]. It is also possible to compile OpenAIS from source and install it on all HA nodes by running ''/configure''; ''make'' and ''make install''.
'''''Note:''''' If ''corosync'' is not included in your distribution, your distribution may include the complete OpenAIS package. From the cluster point of view, the only difference is that all files and commands start with ''openais'' rather than ''corosync''. The configuration file is located in ''/etc/ais/openais.conf''.
Once installed, the software looks for a configuration in the file ''/etc/corosync/corosync.conf''.
Complete the following steps to set up the ''corosync'' communication stack:

Revision as of 12:31, 15 January 2010


DISCLAIMER - EXTERNAL CONTRIBUTOR CONTENT

This content was submitted by an external contributor. We provide this information as a resource for the Lustre™ open-source community, but we make no representation as to the accuracy, completeness or reliability of this information.


This page describes how to configure and use Pacemaker with Lustre Failover.

Setting Up Cluster Communications

Communication between the nodes of the cluster allows all nodes to “see” each other. In modern clusters, OpenAIS, or more specifically, its communication stack corosync, is used for this task. All communication paths in the cluster should be redundant so that a failure of a single path is not fatal for the cluster.

An introduction to the setup, configuration and operation of a Pacemaker cluster can be found in:

Setting Up the corosync Communication Stack

The corosync communication stack, developed as part of the OpenAIS project, supports all the communication needs of the cluster. The package is included in all recent Linux distributions. If it is not included in your distribution, you can find precompiled binaries at www.clusterlabs.org/rpm. It is also possible to compile OpenAIS from source and install it on all HA nodes by running /configure; make and make install.

Note: If corosync is not included in your distribution, your distribution may include the complete OpenAIS package. From the cluster point of view, the only difference is that all files and commands start with openais rather than corosync. The configuration file is located in /etc/ais/openais.conf.

Once installed, the software looks for a configuration in the file /etc/corosync/corosync.conf.

Complete the following steps to set up the corosync communication stack: