[Pacemaker] Node attributes

[Florian Haas]

On 2009-09-08 16:21, Johan Verrept wrote:
> On Tue, 2009-09-08 at 15:37 +0200, Florian Haas wrote:
> 
>> Because crm_master is already there, it works, it is what is designed to
>> be used as an interface for changing master preferences
> 
> As mentioned in my other post, it works as long as you do not have
> multiple reasons to move your master. If you do, you limit the priority
> space. This is not a problem in simple cases but it will be in more
> complex configurations, especially when you have more than one RA using
> crm_master and no ways to influence which priority values they assign
> without modifying them (with all the upgrade fun that entails).

crm_master always applies on a per-resource, per-node basis. It
absolutely wouldn't make sense to have one RA override the master pref
of another.

> On my system, I have an external way to detect if my internet
> connections are up or not. I have written a simple RA that hooks into
> this and changes a node attribute between "online" and "offline". This
> is then interpreted with a location rule. It works and allows me to keep
> my priorities all within my cib.

Why do you need to write an RA for that -- doesn't pingd already do what
you need?

Cheers,
Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20090908/96de2e6f/attachment-0004.sig>