New documentation just in time for OSCON!

July 26, 2011

With OSCON in Portland under way (where LINBIT has a presence, of course), we are making three new documents available in the popular Tech Guides section of our web site.

Want to provide feedback or just chat about high availability? Our team is at OSCON booth 426, and the expo space is open 10am-4:30pm on Wednesday, and 10am-5pm on Thursday.

Incidentally, Microsoft is just across the aisle from us — perhaps you want to convince them of DRBD on Windows?


Cluster Stack update for Debian

December 17, 2010

Last week, the Linux-HA project made its Heartbeat 3.0.4 and Cluster Glue 1.0.7 release, and Pacemaker released 1.0.10 a few weeks back. Thanks to the amazing Simon Horman (horms to IRC regulars), those releases have been uploaded to Debian unstable (sid) yesterday.

What's sid?

sid is the permanent code name of the Debian unstable distribution. It's where package maintainers upload fresh builds and maintain the latest versions of distribution packages. It's not meant for general consumption, but acts as a large integration testing platform for Debian developers.

From sid, packages automatically migrate into the testing distribution after a 10-day cooling-off period, and the testing distribution eventually turns into stable at the time of a new Debian release.

So when will these packages show up in testing?

They won't for a time. The current testing distribution is Debian squeeze, which is frozen pending the upcoming release. As such, the automatic unstable-to-testing migration is currently disabled and the only uploads that are allowed in testing are for release-critical bug fixes. Thus, Debian squeeze will ship with Heartbeat 3.0.3, Cluster Glue 1.0.6, and Pacemaker 1.0.9.

After squeeze ships, the normal testing workflow resumes, and new releases of all packages will then pour in again. These will eventually ship as the next Debian release, codenamed wheezy.

What are the Debian maintainers doing to keep packages in shape?

Fixes for critical issues in upstream code are being back-ported to the Debian packages, and released as normal Debian updates. So what is labeled as, say, Heartbeat 3.0.3 in Debian is not identical to the upstream 3.0.3 release -- instead, it's upstream 3.0.3 plus bug fixes.

Can I get the new versions from backports?

The Debian backports repository is for packages being back-ported from the next Debian release to the current. However, packages going to backports are first expected to pass through testing.

With testing frozen, no new packages go to backports. So before the Debian squeeze release, don't expect these packages in backports.

But I need these new versions now! What can I do?

If you must, roll your own backport. This is at your own risk and you will be using packages lacking proper integration testing. If things break, you get to keep the pieces.

The example below is for cluster-glue.

Add the following line to your /etc/apt/sources.list:

deb-src http://<your favorite debian mirror>/debian sid main

Then, install build dependencies (as root):

apt-get build-dep cluster-glue

Get the sources and build a package (as non-root):

apt-get -t sid source cluster-glue
cd cluster-glue-<version>
dpkg-buildpackage

Finally, again as root, install the newly built binary packages.

If you are upgrading the whole stack, make sure you

  • build and install packages from the cluster-glue source package first,
  • then build and install packages from heartbeat,
  • finally build and install packages from pacemaker.

Upstart support coming to Pacemaker

September 15, 2010

Thanks primarily to the efforts of Senko Rašić and Ante Karamatić, the Pacemaker cluster stack is being augmented with support for Upstart services. This is in addition to support for OCF resource agents and LSB/SysV init scripts, both of which have been supported in Pacemaker for years.

This is functionality now present in the upstream Mercurial trees, and we need testers to get in shape for release. Yes, that means you can help!

This is primarily relevant to you if you use a distribution with upstart as its default init daemon. This includes Ubuntu lucid, OpenSuSE 11.3, recent Fedora releases, and others. To enable upstart support, you will need an upstream hg tip for the cluster-glue libraries, and for Pacemaker.

Here’s how I build cluster-glue with upstart support from local hg checkouts:

hg clone http://hg.linux-ha.org/glue cluster-glue
cd cluster-glue
./autogen.sh
# Next step is important: must include --enable-upstart to enable upstart support
./configure --enable-upstart
make
sudo make install

... and then I simply continue like I normally would for a Pacemaker from-source install, as illustrated here.

When I'm done, and have configured my Heartbeat/Pacemaker cluster as shown here, I can proceed with adding an Upstart based job to my cluster configuration:

crm configure
primitive mysql upstart:mysql \
  op start timeout=120s
  op stop timeout=120s
  op monitor interval=30s
commit

And that's it! Now I can use the mysql upstart job like any other cluster resource. Try it out -- and please report back any issues you encounter!


Automating MySQL replication with Pacemaker

July 12, 2010

A little while back we did a webinar on using Pacemaker to fully automate MySQL replication. We now have a recording of that webinar available from our web site.


Linux cluster stack Debian packages for lenny!

July 9, 2010

Thanks to Martin Loschwitz, official Linux cluster stack Debian packages are now available for Debian lenny. Check out the the lenny-backports repository on backports.org (and your favorite local mirror).

When upgrading from Heartbeat 2.1.3, this webinar recording may come in handy. The webinar covers an upgrade to squeeze, but the upgrade procedure is identical if you’re staying on lenny.


Follow

Get every new post delivered to your Inbox.