[ClusterLabs] Feedback wanted: changing "master/slave" terminology

Jehan-Guillaume de Rorthais jgdr at dalibo.com
Fri Jan 26 17:30:47 EST 2018


On Fri, 26 Jan 2018 09:37:39 -0600
Ken Gaillot <kgaillot at redhat.com> wrote:
...

> > All RA
> > must implement the first two states "stopped" and "started". The
> > cases where RA
> > is promotable should then be called..."promotable" I suppose.
> > 
> > However, why exactly should we find a terminology for RA implementing
> > the
> > "promote" action? Should we find some new terminology for RA
> > implementing
> > optional actions like "notify" ("notifiable") or "validate-all"
> > ("validatable")
> > action as well? (ok, these are not roles, but I try to explain my
> > point :))
> > 
> > Now the terminology is common using "stopped, started, promoted",
> > should we stop considering "multistate RA" as special cases? We could
> > simply
> > explain RAs are implementing all or a subset of the actions/roles
> > Pacemaker
> > offers and give documentation details related to roles properties,
> > variables
> > and transitions, isn't it?  
> 
> We will need some way of specifying it in the syntax, and that will
> become its name ... <clone promotable="true"> or whatever. (We can't
> simply go by what's in the RA metadata for technical reasons not worth
> going into here.)

That makes me wonder how pcs and crm syntax should evolve as well from the
user point of view... :/ 

> > > "Promotable" is certainly accurate, but I have a (very mild)
> > > concern
> > > about how easily it is understood by non-native English speakers.
> > > Perhaps someone who speaks English as a second language could chime
> > > in
> > > on that?  
> > 
> > "Promotable" sounds accurate to me (native french speaker).  
> 
> That's good to know. I think we have at least narrowed it down to
> "multistate" or "promotable" :-)
> 
> Unfortunately the role names are now back in play as well. "Promoted"
> and "unpromoted"?
> 
> E.g.:
> 
> Instead of a single "started" role, a promotable clone resource must be
> in one of two roles when active: "promoted" or "unpromoted".

What about my previous suggestion to use "active" to match either "Started" or
"Promoted" state?




More information about the Users mailing list