Hi all,
I want to accomplish the following behaviour for two
resource A and B:
* If A is running and B will be started, B should run
on the same node as A
* If A is NOT started and B will be started, B can be
run whereever it wants.
* If A is not running, B is running on node X, A is
started on n
On Wednesday 25 July 2007, matilda matilda wrote:
> Hi all,
>
> I want to accomplish the following behaviour for two
> resource A and B:
>
> * If A is running and B will be started, B should run
> on the same node as A
> * If A is NOT started and B will be started, B can be
> run whereever it wants
On Wednesday 25 July 2007, matilda matilda wrote:
> >>> Max Hofer <[EMAIL PROTECTED]> 25.07.2007 12:12 >>>
> >
> > This is a simple assymetric co-location rule (since 2.0.8 all co-location
> > rules are assymetric).
> >
> > This means write a rule that B follows A:
> >
>
> Hi Max,
>
> that is exac
On Wednesday 25 July 2007, matilda matilda wrote:
> Hi Max,
>
> >>> Max Hofer <[EMAIL PROTECTED]> 25.07.2007 14:33 >>>
> >
> > It really would help if you just attached the CIB before and after you
> > started resource A. ;-)
>
> I thought it would be easier this way. :-))
>
> > [...many many valu
>>> Max Hofer <[EMAIL PROTECTED]> 25.07.2007 12:12 >>>
> This is a simple assymetric co-location rule (since 2.0.8 all co-location
> rules are assymetric).
>
> This means write a rule that B follows A:
>
Hi Max,
that is exactly what I thought, too.
BUT: With this constraint, if A is NOT starte
Hi Max,
>>> Max Hofer <[EMAIL PROTECTED]> 25.07.2007 14:33 >>>
> It really would help if you just attached the CIB before and after you
> started
> resource A. ;-)
I thought it would be easier this way. :-))
> [...many many valuable informations...]
Thank you for the informations and the ti
Hi Max,
>>> Max Hofer <[EMAIL PROTECTED]> 25.07.2007 15:55 >>>
> [...] (not to mention that my english is not the best). [...]
You can write it in Austrian if you like... ;-))
Best regards
Andreas Mock
___
Linux-HA mailing list
Linux-HA@lists.linux-
On 7/25/07, matilda matilda <[EMAIL PROTECTED]> wrote:
> >>> Max Hofer <[EMAIL PROTECTED]> 25.07.2007 12:12 >>>
> > This is a simple assymetric co-location rule (since 2.0.8 all co-location
> > rules are assymetric).
> >
> > This means write a rule that B follows A:
> >
>
> Hi Max,
>
> that is exa
Hi Max, hi all,
for all who want to follow up, attached the needed files:
* cluster-options.xml : all options explicit
* r-A.xml (resource definition and constraints for resource A)
* r-B.xml (resource definition and constraints for resource B)
* WARNING: My nodes are called db01 and db02. You ha
On 7/25/07, matilda matilda <[EMAIL PROTECTED]> wrote:
> Hi Max, hi all,
>
> for all who want to follow up, attached the needed files:
> * cluster-options.xml : all options explicit
> * r-A.xml (resource definition and constraints for resource A)
> * r-B.xml (resource definition and constraints for
On 8/16/07, Andrew Beekhof <[EMAIL PROTECTED]> wrote:
> On 7/25/07, matilda matilda <[EMAIL PROTECTED]> wrote:
> > * all resources do have target_role=stopped
> > * try to start r_B (target_role=started)
> > * it doesn't start here.
>
> not sure if this was a question or an answer, but because of
>>> "Christian Rishøj" <[EMAIL PROTECTED]> 08/16/07 11:11 PM >>>
> Just to further my understanding of colocation constraints: Does this
> also imply that B will stop/relocate if A fails, or does it take an
>extra rule to achieve that?
If you have resource A and B and an asymetrical colocation con
12 matches
Mail list logo
