Hello Ken,
Thanks for the feedback. Yea, I am on v1.4.2 currently.
Let me start with checking my resource script against the head and see if
anything pops out at me.
Thanks!
-With kind regards,
Peter Brunnengräber
- Original Message -
From: "Ken Gaillot"
To:
- On Jul 18, 2016, at 7:29 PM, Ken Gaillot kgail...@redhat.com wrote:
>>
>> Hi Ken,
>>
>> thanks for your help.
>>
>> Can i edit them directly ? Or do i have to make a circuit with constraints ?
>
> Constraints are how they are edited.
>
> Stop/start aren't used in normal operation,
- On Jul 18, 2016, at 4:04 PM, Ken Gaillot kgail...@redhat.com wrote:
>>
>> Is there a way to manipulate the scores ? Is the score -INFINITY because the
>> resource is stopped
>> or is the resource stopped because the score is -INFINITY ?
>
> Yes, yes and yes ;-)
>
> You can manipulate
On 07/15/2016 07:08 PM, Lentes, Bernd wrote:
>
>
> - Am 15. Jul 2016 um 23:48 schrieb Ken Gaillot kgail...@redhat.com:
>
>> On 07/15/2016 03:54 PM, Lentes, Bernd wrote:
>>>
>>>
>>> - Am 13. Jul 2016 um 14:25 schrieb Kristoffer Grönlund
>>> kgronl...@suse.com:
>>>
>
>
>
>>>
>>>
> On 18/07/16 07:59, Da Shi Cao wrote:
>> dlm_controld is very tightly coupled with cman.
Wrong assumption.
In fact, support for shipping ocf:pacemaker:controld has been
explicitly restricted to cases when CMAN logic (specifically the
respective handle-all initscript that is in turn, in that
Hi,
On 07/18/2016 02:59 PM, Da Shi Cao wrote:
dlm_controld is very tightly coupled with cman. I have built a cluster purely
with pacemaker+corosync+fence_sanlock. But if agent ocf:pacemaker:controld is
desired, dlm_controld must exist! I can only find it in cman.
Not sure I can understand
dlm_controld is very tightly coupled with cman. I have built a cluster purely
with pacemaker+corosync+fence_sanlock. But if agent ocf:pacemaker:controld is
desired, dlm_controld must exist! I can only find it in cman.
Can the command dlm_controld be obtained without bringing in cman?
Best