if you are only using ips, keepalived with two vrrp groups might be the better solution. failover times in about two seconds.
Greetings Christoph On Fri, Jan 27, 2017 at 9:33 PM, Dejan Muhamedagic <[email protected]> wrote: > Hi, > > On Fri, Jan 27, 2017 at 10:52:25AM +0100, Arturo Borrero Gonzalez wrote: > > On 26 January 2017 at 22:31, Valentin Vidic <[email protected]> > wrote: > > > On Thu, Jan 26, 2017 at 09:31:23PM +0100, Valentin Vidic wrote: > > >> Guess you could create a Dummy resource and make INIFINITY colloction > > >> constraints for the IPs so they follow Dummy as it moves between the > > >> nodes :) > > > > > > In fact using resource sets this becomes one rule: > > > > > > colocation ip6-leader6 inf: ( ip6a ip6b ip6c ip6d ) leader6 > > > > > > But I also had to set: > > > > > > property node-action-limit=30 > > > > > > or the number of running resource operations was limited to > > > 2 x number of CPUs. > > > > > > > Great thanks, I couldn't find this in the docs. Any chance this get > > included somewhere? > > You can find documentation for such attributes in the pengine's > meta-data or, sometimes, crmd's. For instance: > > crm ra info pengine > crm ra info crmd > > Thanks, > > Dejan > > _______________________________________________ > Users mailing list: [email protected] > http://lists.clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org >
_______________________________________________ Users mailing list: [email protected] http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
