*From:* Andrew Beekhof
*Sent:* 2014-08-31 23:16:10 EDT
*To:* The Pacemaker cluster resource manager
*Subject:* Re: [Pacemaker] pacemaker-remote container as a clone resource
> On 1 Sep 2014, at 12:41 pm, Patrick Hemmer wrote:
>
>> From: Andrew Beekhof
>> Sent: 2014-08-31 19:57:43 EDT
>> To: Th
On 1 Sep 2014, at 12:41 pm, Patrick Hemmer wrote:
> From: Andrew Beekhof
> Sent: 2014-08-31 19:57:43 EDT
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] pacemaker-remote container as a clone resource
>
>> On 31 Aug 2014, at 6:09 pm, Patrick Hemmer
>> wrote:
>>
>>
>
*From:* Andrew Beekhof
*Sent:* 2014-08-31 19:57:43 EDT
*To:* The Pacemaker cluster resource manager
*Subject:* Re: [Pacemaker] pacemaker-remote container as a clone resource
> On 31 Aug 2014, at 6:09 pm, Patrick Hemmer wrote:
>
>> I'm interested in creating a resource that will control host con
On 31 Aug 2014, at 6:09 pm, Patrick Hemmer wrote:
> I'm interested in creating a resource that will control host containers
> running pacemaker-remote. The catch is that I want this resource to be a
> clone, so that if I want more containers, I simply increase the `clone-max`
> property.
Wha
I'm interested in creating a resource that will control host containers
running pacemaker-remote. The catch is that I want this resource to be a
clone, so that if I want more containers, I simply increase the
`clone-max` property. The problem is that the `remote-node` meta
parameter is set on the c
