Hi Thank you for your answer. OK I understand, but this makes troubles for me... Example: When the node holding the resource (and the constraint) reboots the resource is not moving to the other node (because of this constraint, I see on the debug logs no node can hold the resource). As soon as I remove this constraint, the resource migrates...
What's your mind about that ? Thank you very much Le 05/12/13 18:18, Lars Marowsky-Bree a écrit : > On 2013-12-05T17:12:01, Gaëtan Slongo <gslo...@it-optics.com> wrote: > >> Hi ! >> >> I'm trying to configure a cluster using pacemaker 1.1 and corosync since >> 2 days (on Debian wheezy). Many of my current problems are related to >> the contraint creation. When I manually move a resource (or when a >> failback occurs) this kind of constraint is automatically created : > It's not "automatically" created - it is created explicitly in response > to your "manual" resource move. The way how resources are moved in > Pacemaker is just this: by creating a constraint in the configuration. > > There is no other state in Pacemaker policy but what you see in the CIB. > Any and all configuration changes are reflected there. > > Similarly, when you "unmove" a resource, the tools will remove that > constraint as well. You can also make it time-dependent so that it > expires after a while automatically. > > > Regards, > Lars > _______________________________________________ Pacemaker mailing list: Pacemaker@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
