[Pacemaker] getting started with development

David Vossel dvossel at redhat.com
Wed Feb 26 10:37:02 EST 2014

----- Original Message -----
> From: "Tasim Noor" <tasimne76 at gmail.com>
> To: pacemaker at oss.clusterlabs.org
> Sent: Tuesday, February 25, 2014 5:10:33 PM
> Subject: [Pacemaker] getting started with development
> Hi All,
> I would be interested in contributing to the pacemaker/linux HA codebase. I
> did look through the TODO but it doesn't say which of topics are currently
> worked on and which ones are open to be taken up. i would appreciate if
> somebody can point me to a starting point i.e some feature that i can start
> looking at to get my hands dirty along with some pointers to specific source
> files as a starting point.

Awesome, one of the things we recommend to pacemaker developers is to learn about our unit tests. Specifically, being able to run CTS in a virtualized environment with 3 or more nodes is a good exercise.

I run CTS on KVM instances using libvirt. For fencing I use fence_virtd on the host machine and the fence_xvm agent within the guest vms.

After you get fence_virtd running and accessible from the guests ('fence_xvm -o list' should list all the running guest vms when executed from a guest vm) you can use the steps I have outlined in the scenario file below to execute cts.


CTS is not strictly required for all pacemaker development. Depending on how deep you want go it is very helpful at verifying invasive changes.

-- Vossel

> Thanks for your help.
> Kind Regards,
> Tasim
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

More information about the Pacemaker mailing list