On 2013-07-03T00:20:19, Vladislav Bogdanov <[email protected]> wrote:
> I do not edit them. I my setup I generate full crm config with
> template-based framework.
And then you do a load/replace? Tough; yes, that'll clearly overwrite
what is already there and added by scripts that more dynamically modify
the CIB.
Since we don't know your complete merging rules, it's probably easier if
your template engine gains hooks to first read the CIB for setting those
utilization values.
> That is very convenient way to f.e stop dozen of resources in one shot
> for some maintenance. I have special RA which creates ticket on a
> cluster start and deletes it on a cluster stop. And many resources may
> depend on that ticket. If you request resource handled by that RA to
> stop, ticket is revoked and all dependent resources stop.
>
> I wouldn't write that RA if I have cluster-wide attributes (which
> perform like node attributes but for a whole cluster).
Right. But. Tickets *are* cluster wide attributes that are meant to
control the "target-role" of many resources depending on them. So you're
getting exactly what you need, no? What is missing?
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
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
