On 18/04/2013, at 2:42 PM, Yuichi SEINO wrote:
> Hi,
>
> 2013/4/15 Andrew Beekhof :
>>
>> On 15/04/2013, at 3:38 PM, Yuichi SEINO wrote:
>>
>>> Hi,
>>>
>>> 2013/4/8 Andrew Beekhof :
I'm not 100% sure what the best approach is here.
Traditionally this is done with resource ag
Hi,
2013/4/15 Andrew Beekhof :
>
> On 15/04/2013, at 3:38 PM, Yuichi SEINO wrote:
>
>> Hi,
>>
>> 2013/4/8 Andrew Beekhof :
>>> I'm not 100% sure what the best approach is here.
>>>
>>> Traditionally this is done with resource agents (ie. ClusterMon or ping)
>>> which update attrd.
>>> We could p
On 15/04/2013, at 3:38 PM, Yuichi SEINO wrote:
> Hi,
>
> 2013/4/8 Andrew Beekhof :
>> I'm not 100% sure what the best approach is here.
>>
>> Traditionally this is done with resource agents (ie. ClusterMon or ping)
>> which update attrd.
>> We could potentially build it into attrd directly, b
Hi,
2013/4/8 Andrew Beekhof :
> I'm not 100% sure what the best approach is here.
>
> Traditionally this is done with resource agents (ie. ClusterMon or ping)
> which update attrd.
> We could potentially build it into attrd directly, but then we'd need to
> think about how to turn it on/off.
>
>
I'm not 100% sure what the best approach is here.
Traditionally this is done with resource agents (ie. ClusterMon or ping) which
update attrd.
We could potentially build it into attrd directly, but then we'd need to think
about how to turn it on/off.
I think I'd lean towards a new agent+daemon
Hi All,
I want to display interface link status in corosync. So, I think that
I will add this function to the part of "pacemakerd".
I am going to display this status to "Node Attributes" in crm_mon.
When the state of link change, corosync can run the callback function.
When it happens, we updat
