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

[Lars Marowsky-Bree]

On 2010-03-10T16:58:48, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:

> > I fear if the admin has created the situation of conflicting attribute
> > sets, it is the admins responsibility to a) remove them, or b) select
> > the specific attribute set they want modified.
> True. It's just that the recent stampede of people running into
> this issue indicated that something may not exactly be right
> here.

Oh I agree. I didn't disagree that we need to improve, I even like the
direction, but this was going too far (ie, it bit me ;-) to the other
side.

> OK, probably a better and more correct way is to offer a choice
> in case there are multiple target-roles found. Though that would
> probably make quite a narative of a single question ;-) Another
> solution could be to keep the old behaviour and introduce a new
> option/command form to do a "stop regardless of multiple sets and
> what have you". BTW, it is interesting (and funny) that most
> admins have no idea about multiple attribute sets :)

Well, if I had my way, there'd be an shell option to specify the default
behaviour: ask, overwrite, reject (the latter being the current
behaviour) for interactive mode. (Default "ask")

In addition, to make this usable for non-interactive mode, there'd be a
--overwrite command or a --set=xxx method to specify the set the user
wants to modify.



Regards,
    Lars

-- 
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde