[Pacemaker] Migrating resources on custom conditions

Andrew Beekhof andrew at beekhof.net
Thu Feb 20 18:58:54 EST 2014

On 20 Feb 2014, at 7:34 pm, Dan Markhasin <minimizer at gmail.com> wrote:

> Hi,
> I am wondering if it is possible to configure complex/custom migration rules, so resources would migrate in case there is a problem with the current node it is running on.
> i.e.
> If the node has a bad disk, or high load, the resource should be migrated to a different node.

If you write a resource agent that monitors any or all of the above conditions and add it to the cluster as an unmanaged clone resource, then you can colocate things with it.
At the point the disk goes bad, the resource appears to have stopped and the real resources will be moved somewhere else.

> I didn't find any examples for such custom rules in the documentation. Is it possible ?
> Thanks,
> Dan
> _______________________________________________
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140221/c52379c5/attachment-0003.sig>

More information about the Pacemaker mailing list