On Nov 14, 2007, at 10:17 AM, Daniel X Moore wrote:
Andrew Beekhof wrote:
We're not trying to restart the children of the group, we're
trying to
reload them (i.e. without a stop/start).
No kidding - thats why i said groups are hardwired to _always_
restart them.
The wiki says that a resource group is equivalent to a co-located
set of resources with ordering constraints chaining them together.
It seems odd that the reload behaviour should differ between these
two configurations which otherwise behave the same.
Is this an intentional feature or just a missing part of the reload
feature?
groups are a syntactic shortcut who's initial purpose was to simplify
migration from v1 configs.
the tradeoff for not having to specify the constraints is that you
only get access to a limited set of v2's capabilities^ (one that cover
the most common use cases).
reload is not one of those capabilities.
if you need access to the full power of v2's resource model, don't use
groups.
^ the alternative being I'd have to programatically support every
potential combination of constraint and resource options within a
group - which isn't going to happen.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
