[Pacemaker] Enable remote monitoring

[Lars Marowsky-Bree]

On 2012-12-04T12:45:05, "Gao,Yan" <ygao at suse.com> wrote:

> > (Ohhh. Did we just find a use for a negative score here? ;-) Just
> > throwing that out there. It'd fit the model we have so far, is all I'm
> > saying.)
> Perhaps to name another "kind" for order constraint instead of an
> additional optional attribute?

Sounds good. But - may this be something that we'd perhaps want to
combine with Mandatory/Optional?

> If "group" has already been tortured enough, like Andrew said :-) , then
> we don't have to use group in either way.  If we really need some kind
> of "container", how about we just use resource_set:
> 
> order vm-then-rscs inf: vm (nagios-foo nagios-bar) \
>       restart-origin="true"
> colocation rscs-with-vm inf: (nagios-foo nagios-bar) vm

Yes, this also looks like a good idea.

(While we're at it, it'd be awesome if there was a constraint that
combined order + colocation.)

> <rsc_order id="vm-with-rscs" restart-origin="true">
>   <resource_set id="vm-origin">
>     <resource_ref id="vm"/>
>   </resource_set>
>   <resource_set id="vm-rscs" sequential="false" >
>     <resource_ref id="nagios-foo"/>
>     <resource_ref id="nagios-bar"/>
>   </resource_set>
> </rsc_order>

Yes, I think this looks good.


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde