[openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles
Tzu-Mainn Chen
tzumainn at redhat.com
Tue Jan 28 10:04:14 UTC 2014
I've spent some time thinking about this, and I have a clarification.
I don't like the use of the word 'deployment', because it's not exact
enough for me. Future plans for the tuskar-ui include management of the
undercloud as well, and at that point, 'deployment role' becomes vague, as
it could also logically apply to the undercloud.
For that reason, I think we should call it an 'overcloud deployment role',
or 'overcloud role' for short.
That being said, I think that the UI could get away with just displaying
'Role', as presumably the user would be in a page with enough context to
make it clear that he's in the overcloud section.
Mainn
----- Original Message -----
> I'd argue that we should call it 'overcloud role' - at least from the
> modeling
> point of view - since the tuskar-api calls a deployment an overcloud.
>
> But I like the general direction of the term-renaming!
>
> Mainn
>
> ----- Original Message -----
> > Based on this thread which didn't seem to get clear outcome, I have one
> > last suggestion:
> >
> > * Deployment Role
> >
> > It looks that it might satisfy participants of this discussion. When I
> > internally talked to people it got the best reactions from already
> > suggested terms.
> >
> > Depending on your reactions for this suggestion, if we don't get to
> > agreement of majority by the end of the week, I would call for voting
> > starting next week.
> >
> > Thanks
> > -- Jarda
> >
> > On 2014/21/01 15:19, Jaromir Coufal wrote:
> > > Hi folks,
> > >
> > > when I was getting feedback on wireframes and we talked about Roles,
> > > there were various objections and not much suggestions. I would love to
> > > call for action and think a bit about the term for concept currently
> > > known as Role (= Resource Category).
> > >
> > > Definition:
> > > Role is a representation of a group of nodes, with specific behavior.
> > > Each role contains (or will contain):
> > > * one or more Node Profiles (which specify HW which is going in)
> > > * association with image (which will be provisioned on new coming nodes)
> > > * specific service settings
> > >
> > > So far suggested terms:
> > > * Role *
> > > - short name - plus points
> > > - quite overloaded term (user role, etc)
> > >
> > > * Resource Category *
> > > - pretty long (devs already shorten it - confusing)
> > > - Heat specific term
> > >
> > > * Resource Class *
> > > - older term
> > >
> > > Are there any other suggestions (ideally something short and accurate)?
> > > Or do you prefer any of already suggested terms?
> > >
> > > Any ideas are welcome - we are not very good in finding the best match
> > > for this particular term.
> > >
> > > Thanks
> > > -- Jarda
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
More information about the OpenStack-dev
mailing list