Providing Open Source High-Availability Software for Linux and other OSes since 1999.

This web page is no longer maintained. Information presented here exists only to avoid breaking historical links.
The Project stays maintained, and lives on: see the Linux-HA Reference Documentation.

CRM Successor

Heartbeat 3.0

$/!\$ Pages linked to below may be out of date or right out obsolete.
See Site News.

Introduction

Using Linux-HA

Links

Common Searches

1 February 2010 Hearbeat 3.0.2 released see the Release Notes

18 January 2009 Pacemaker 1.0.7 released see the Release Notes

16 November 2009 LINBIT new Heartbeat Steward see the Announcement

Last site update:
2010-03-13 09:51:47

printer friendly view

ATTENTION

Linux HA has switched over to Mercurial as our source code management system. The text below is of historical interest only.

Please, go to http://hg.linux-ha.org/ instead.

Checking out the development branch

Make sure Mercurial is installed
Run
```
hg clone http://hg.linux-ha.org/dev
```

See http://hg.linux-ha.org/ for list of available branches.

CVS for Linux-HA

To get read-only access to the Linux-HA CVS instance, here's what you do:

export CVSROOT=:pserver:guest@cvs.linux-ha.org:/home/cvs/linux-ha
cvs login

The password for user guest is guest

The module name is "linux-ha". Now, you can do normal CVS commands, and things should go well from there.

For example, one can do a cvs co linux-ha, and got a copy of the workspace. Once a copy is obtained, one can do a cvs update -d to see the latest changes to the repository.

Linux-HA CVS web interface

The CVS repository can be accessed via the web.

CVS automated build script

We have written a script for automating builds and simple tests from CVS. Some may find it useful, or interesting as a start for your own tool to do the same.

Use of Branches

We keep the development version of CVS as the HEAD branch. When we want to create a maintainable, stable release, we create a branch in CVS. We currently have the following branches:

HEAD
STABLE_1_2
STABLE_1_0
STABLE_0_4_9-branch

Tagging

We have a convention of tagging releases with STABLE_x_y_z for stable release x.y.z. Here are a few of those tags:

STABLE_1_2_3
STABLE_1_2_2
STABLE_1_2_1
STABLE_1_2_0
STABLE_1_0_4
STABLE_1_0_3
STABLE_1_0_2
STABLE_1_0_1
STABLE_0_4_9

We tag beta releases with BETA_a_b_c for beta release a.b.c. Here are a few of these tags from CVS:

BETA_1_99_5
BETA_1_99_4
BETA_1_99_3
BETA_1_99_2
BETA_1_99_1