Re: Colocation of cloned resource instances.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



So, if I really really want to do it, can I?
I'm not being snarky.  I'd like to know if it's possible.

You are forcing me to think of a different solution to my cluster implementation.  Maybe that's good.


Regards.
Mark K Vallevand   Mark.Vallevand@xxxxxxxxxx
May you live in interesting times, may you come to the attention of important people and may all your wishes come true.
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.


-----Original Message-----
From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Andrew Beekhof
Sent: Monday, February 17, 2014 05:45 PM
To: linux clustering
Subject: Re:  Colocation of cloned resource instances.


On 18 Feb 2014, at 8:32 am, Vallevand, Mark K <Mark.Vallevand@xxxxxxxxxx> wrote:

> I have 2 cloned resources.  I want to make sure that instance 0 of each cloned resource are collocated.  (And instance 1, 2, etc.)

Instance numbers are an implementation detail.  You're not supposed to care.

>  
> I'd like to do something like this:
>                 crm configure colocation name INFINITY: a_clone:0 b_clone:0
> Where a_clone is a clone of resource a, etc:
> crm configure clone a_clone a meta clone-max=2
> Same for b_clone and b.
> A and b are primitives:
>                 crm configure primitive a .
>  
> Not having much luck.  Advice?
> Tried using a_clone:0 and a:0 on the collocation command.
> Is this even possible?
>  
> Regards.
> Mark K Vallevand   Mark.Vallevand@xxxxxxxxxx
> May you live in interesting times, may you come to the attention of important people and may all your wishes come true.
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>  
> -- 
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster


-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster





[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux