[ClusterLabs] Two related Cluster

[‪H Yavari‬ ‪]

Hi,
I begin to test. So I defined 2 clusters that are include: Cluster 1: App1 and App3   Cluster 2: App2 and App4
Now If I want enable IPaddr as a resource on clusters, this resource will assign to both nodes. while ip float should run only on App3 and App4.Should I use constraints to limit ip float resource to only one node in each cluster? so I should do this for other resource too and then use Booth for CTR?Any hints or sample save my life :)

Regards,H.Yavari


      From: Klaus Wenninger <kwenning at redhat.com>
 To: users at clusterlabs.org 
 Sent: Tuesday, 17 May 2016, 11:08:51
 Subject: Re: [ClusterLabs] Two related Cluster
   
On 05/17/2016 08:20 AM, ‪H Yavari‬ ‪ wrote:
> Hi,
>
> Emm I have a scenario and I'm confused. So I'm searching for the
> solutions. Can you please check this
> http://clusterlabs.org/pipermail/users/2016-April/002796.html
>
> I don't know how achieve to this? with Booth? with attribute? 2
> clusters or 1 cluster?

I would say you have 2 options:

- 1 cluster with node attributes and these dummy resources I had
described previously in the thread. (Unless
  anybody has a better idea how to tackle this).
- 2 small clusters and use booth

Which one is better depends e.g. on where your servers are located -
timing/reliability issues with certain network connections
between them?
Bringing up the booth infrastructure is of course an issue as well...

>
> Please show me a way.
>
> Many thanks.
>
> Regards,
> H.Yavari
>
>
> ------------------------------------------------------------------------
> *From:* Kristoffer Grönlund <kgronlund at suse.com>
>
>
>
> ‪H Yavari‬ ‪ <hyavari at rocketmail.com <mailto:hyavari at rocketmail.com>>
> writes:
>
> > Thank you for reply.
> > I mean when in cluster X , node A is online and node B is offline,
> in cluster Y nodes will have same status.
>
> Why do you want to have two clusters with the same set of nodes? A
> single cluster can do everything that the two clusters could. If you
> want to run certain resources on only some of the nodes, you can achieve
> this with node attributes and location constraints.
>
>
> Cheers,
> Kristoffer
>
> -- 
> // Kristoffer Grönlund
> // kgronlund at suse.com <mailto:kgronlund at suse.com>
>
>
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://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: Users at clusterlabs.org
http://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


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160518/792ac67a/attachment-0001.htm>