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!
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
Image may be NSFW.Clik here to view.
Image may be NSFW.Clik here to view.
Image may be NSFW.Clik here to view.
Image may be NSFW.Clik here to view.
Image may be NSFW.Clik here to view.
Image may be NSFW.Clik here to view.
PlanetMySQL Voting: Vote UP / Vote DOWN
