13.11.2014 00:52, Kristoffer Grönlund wrote:
[...]
> Let me know if you find any other issues, thanks!
The one I met yesterday is an inability to set schema to
'pacemaker-next' with crmsh (did not try other values).
cibadmin did the job for me.
Best,
Vladislav
_
Vladislav Bogdanov writes:
> 13.11.2014 00:12, Kristoffer Grönlund wrote:
>> Vladislav Bogdanov writes:
>>
I haven't had time to look closer at resource-discovery, but yes, I
certainly intend to support every option that makes it into a released
version of pacemaker at least.
>>>
13.11.2014 00:12, Kristoffer Grönlund wrote:
> Vladislav Bogdanov writes:
>
>>> I haven't had time to look closer at resource-discovery, but yes, I
>>> certainly intend to support every option that makes it into a released
>>> version of pacemaker at least.
>>
>> Great. Can't wait for that to hap
Vladislav Bogdanov writes:
>> I haven't had time to look closer at resource-discovery, but yes, I
>> certainly intend to support every option that makes it into a released
>> version of pacemaker at least.
>
> Great. Can't wait for that to happen :)
>
>>
>> As for the pacemaker-next schema, I th
12.11.2014 23:32, Kristoffer Grönlund wrote:
> Vladislav Bogdanov writes:
>
>> Hi Kristoffer, Dejan.
>>
>> Do you have plans to add support to crmsh for 'resource-discovery'
>> location constraint option (added to pacemaker by David in pull requests
>> #589 and #605) as well as for the 'pacemaker
Vladislav Bogdanov writes:
> Hi Kristoffer, Dejan.
>
> Do you have plans to add support to crmsh for 'resource-discovery'
> location constraint option (added to pacemaker by David in pull requests
> #589 and #605) as well as for the 'pacemaker-next' schema (this one
> seems to be trivial)?
>
> Be
Hi Kristoffer, Dejan.
Do you have plans to add support to crmsh for 'resource-discovery'
location constraint option (added to pacemaker by David in pull requests
#589 and #605) as well as for the 'pacemaker-next' schema (this one
seems to be trivial)?
Best,
Vladislav
_
