[Pacemaker] Constraint on location of resource start

Andreas Kurz andreas at hastexo.com
Fri Nov 9 20:33:16 EST 2012

On 11/09/2012 08:49 AM, Cserbák Márton wrote:
> Hi,
> I have successfully set up a DRBD+Pacemaker+Xen cluster on two Debian
> servers. Unfortunately, I am facing the same issue as the one
> described in https://bugzilla.redhat.com/show_bug.cgi?id=694492,
> namely, that the CPU features differ on the two servers. When the domU
> resources, that were originally created on the newer server get
> migrated to the older server, they usually crash with libc trap
> messages on the console. Live migration of domUs originally created on
> the older server is without problem in both ways.
> What I was trying to figure out, if there was any way to configure
> pacemaker to allow creation of domUs on the older server only, and
> allow migration of resources to the newer server.

a simple location constraint preferring the older server should be
sufficient ... for most cases ...


Need help with Pacemaker?

> Any help is appreciated. Best regards,
> Márton Cserbák
> _______________________________________________
> 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: 222 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20121110/1774c141/attachment-0003.sig>

More information about the Pacemaker mailing list