[Pacemaker] Looking for correct constraints
Michael Schwartzkopff
misch at multinet.de
Fri Oct 30 12:49:32 UTC 2009
Am Freitag, 30. Oktober 2009 13:37:36 schrieb Dominik Klein:
> Michael Schwartzkopff wrote:
> > Am Freitag, 30. Oktober 2009 13:26:35 schrieb Lars Marowsky-Bree:
> >> On 2009-10-30T13:19:52, Michael Schwartzkopff <misch at multinet.de> wrote:
> >>> I have a three node cluster. I have two resources that are not allowed
> >>> to run together in the cluster. Basically resource2 is a failover case
> >>> for resource1.
> >>>
> >>> How can I tell the cluster not to run res1 and res2 together in the
> >>> cluster?
> >>
> >> You mean "start resource2 only when resource1 is not running anywhere,
> >> but prefer resource1"?
> >
> > Yes.
> >
> >> I'm not sure you can.
> >
> > That is bad news.
>
> Maybe set a cluster-wide attribute, which, when set, does not allow res2
> to run. Ie rule with score -infinity.
>
> res1 could remove this attribute while starting and set this attribute
> when stopping.
>
> Just an idea,
> Dominik
Yes. That would be the next step.
Since the res1 and res2 do differ only in the config file instance_attribute we
also could introduce a rule for the attribute section of a combined resource.
But that also would refer to some other attribute in the CIB.
Greetings,
--
Dr. Michael Schwartzkopff
MultiNET Services GmbH
Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany
Tel: +49 - 89 - 45 69 11 0
Fax: +49 - 89 - 45 69 11 21
mob: +49 - 174 - 343 28 75
mail: misch at multinet.de
web: www.multinet.de
Sitz der Gesellschaft: 85630 Grasbrunn
Registergericht: Amtsgericht München HRB 114375
Geschäftsführer: Günter Jurgeneit, Hubert Martens
---
PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B
Skype: misch42
More information about the Pacemaker
mailing list