[Pacemaker] Colocating resources on the same physical server when resources are run inside virtual servers

[Andrew Beekhof]

On Fri, Nov 18, 2011 at 10:33 AM, Attila Megyeri
<amegyeri at minerva-soft.com> wrote:
> HI,
>
>
> -----Original Message-----
> From: Andrew Beekhof [mailto:andrew at beekhof.net]
> Sent: 2011. november 18. 0:28
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Colocating resources on the same physical server when resources are run inside virtual servers
>
> On Fri, Nov 18, 2011 at 12:46 AM, Andreas Kurz <andreas at hastexo.com> wrote:
>> Hello,
>>
>> On 11/16/2011 09:04 PM, Attila Megyeri wrote:
>>> Hi Team,
>>>
>>>
>>>
>>> Resources "A" and "B" are running within virtual servers. There are
>>> two physical servers "ph1" and "ph2" with two virtualized nodes on each.
>>>
>>>
>>>
>>> What would be the easiest way to have a specific resource (e.g.
>>> resource
>>> "A") move to another node (From node "1" to node "2") in case when a
>>> different resource (e.g. "B")
>>>
>>> moves from node 3 to node 4?
>>>
>>>
>>>
>>> Resources "A" and "B" are independent, but nodes 1 and 3 are virtual
>>> servers running on physical host "ph1" whereas nodes 2 and 4 are
>>> virtual servers on physical host "ph2" and
>>>
>>> the goal is to have resources "A" and "B" run on the same physical
>>> (host) server.
>>
>> Is this one cluster or are these two independent clusters?
>
>
> Well, my first idea was to make them independent, but I am ready to merge them as well :)
>
>
>>
>> For one cluster there would the (hidden,undocumented) feature to use a
>> node-attribute in colocation constraints
>
> Did I not document it, or just not explain how useful it could be in these cases? :-)
>
>
> So I guess I found something not very trivial :)

Actually its pretty trivial to configure, its just not very common

>
>>  unfortunately the crm shell is
>> not aware of this feature so you would have to manipulate the cib
>> directly ... might be worth trying.
>>
>> Regards,
>> Andreas
>>
>> --
>> Need help with Pacemaker?
>> http://www.hastexo.com/now
>>
>>>
>>>
>>>
>>> Thank you in advance,
>>>
>>>
>>>
>>> Bests
>>>
>>>
>>>
>>> Attila
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>>
>>> Project Home: http://www.clusterlabs.org Getting started:
>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs:
>>> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacem
>>> aker
>>
>>
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs:
>> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacema
>> ker
>>
>>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>