----- Original Message ----- > Is it possible to put a location constraint on a resource such that it will > only run on a pacemaker-remote node? Or vice-versa, so that a resource will > not run on a pacemaker-remote node? > > At a glance, this doesn't seem possible as the pacemaker-remote node does not > exist as a <node> entry in the CIB, so there's nothing to match on. Is it > possible to match on the absence of that <node> entry? > > The only other way I can think of doing this is to set utilization > attributes, such that the remote nodes provide a "remote" utilization > attribute, and configure the resource such that it needs 1 unit of "remote".
There is definitely a way to do this already. I can't remember how though. Andrew, I know we discussed this a few months ago and you immediately rattled off how we allow this. Do you remember? -- Vossel > -Patrick > > _______________________________________________ > 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 > _______________________________________________ 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
