[Pacemaker] Handling multiple attribute sets (cs#26435fdfd488)

[Dejan Muhamedagic]

On Wed, Mar 10, 2010 at 04:58:48PM +0100, Dejan Muhamedagic wrote:
> Hi,
> 
> On Wed, Mar 10, 2010 at 04:24:16PM +0100, Lars Marowsky-Bree wrote:
> > Hi all, Dejan,
> > 
> > the above changeset aims to improve the behaviour with multiple
> > attribute sets - right now, the crm_resource et al complain that they
> > can't figure out which one to set, so the changeset simply
> > clears/updates all of them.
> > 
> > I disagree, for the following reasons:
> > 
> > First, I frequently have a "stop" attribute set on a specific resource
> > within a group to make the group start up only to that point; I don't
> > want that overwritten automatically. In fact, I might just want to
> > modify the group target-role, regardless of the value of its children.
> 
> Yes, you might, but why don't then just modify the target-role
> attribute. I have been thinking about this too and to me
> 
> # crm resource start g
> 
> seems to express clear intent to start the whole group g. Don't
> forget that our minds are plagued by all the technical details
> about how the CIB is implemented.

Thinking again about it, dropping target-role from the members of
the group is really wrong. I'll change that.

Cheers,

Dejan