[ClusterLabs] simple active/active router using pacemaker+corosync

Dejan Muhamedagic dejanmm at fastmail.fm
Fri Jan 27 15:33:02 EST 2017


Hi,

On Fri, Jan 27, 2017 at 10:52:25AM +0100, Arturo Borrero Gonzalez wrote:
> On 26 January 2017 at 22:31, Valentin Vidic <Valentin.Vidic at carnet.hr> 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




More information about the Users mailing list