[openstack-dev] [TripleO][Tuskar] Terminology
tzumainn at redhat.com
Thu Dec 12 21:29:00 UTC 2013
Thanks for all the replies so far! Let me try and distill the thread down to the points of
interest and contention:
1) NODE vs INSTANCE
This is a distinction that Robert brings up, and I think it's a good one that people agree
with. The various ROLES can apply to either.
What isn't clear to me (and it's orthogonal to this particular thread) is whether the
wireframes are correct in classifying things by NODES, when it feels like we might want
to classify things by INSTANCE?
2) UNDEPLOYED NODE - a node that has not been deployed with an instance
Other suggestions included UNASSIGED, UNMAPPED, FREE, and AVAILABLE. Some people (I'm one of them)
find AVAILABLE to be a bit of an overloaded term, as it can also be construed to mean that, say,
a service instance is now running on a node and is now "available for use". I'm in favor of an
"UN" word, and it sounds like "UNDEPLOYED" was the most generally acceptable?
3) SIZE THE DEPLOYMENT - the act of deciding how many nodes will need to be assigned to each role in a deployment
Other suggestions included "SET NODE COUNT", "DESIGN THE DEPLOYMENT", "SIZE THE CLOUD". SIZE THE DEPLOYMENT
sounds like the suggested option that used the most words from the other choices, so I picked it as a likely
candidate :) I also like that it uses the word deployment, as that's what we're calling the end result.
4) SERVICE CLASS/RESOURCE CLASS/ROLE CONFIGURATION
So, an example of this was
> KVM Compute is a role configuration. KVM compute(GPU) might be another
I'm personally somewhat averse to "role configuration". Although there are aspects of configuration to
this, "configuration" seems somewhat misleading to me when the purpose of this classification is something
more like - a subrole?
5) NODE PROFILE/FLAVOR
Flavor seemed generally acceptable, although there was some mention of it being an overloaded term. Is there
a case for using a more "user-friendly" term in the UI (like node profile or hardware configuration or. . .)?
Or should we just expect users to be familiar with OpenStack terminology?
Please feel free to correct me if I've left anything out or misrepresented anything!
----- Original Message -----
> I'm trying to clarify the terminology being used for Tuskar, which may be
> helpful so that we're sure
> that we're all talking about the same thing :) I'm copying responses from
> the requirements thread
> and combining them with current requirements to try and create a unified
> view. Hopefully, we can come
> to a reasonably rapid consensus on any desired changes; once that's done, the
> requirements can be
> * NODE a physical general purpose machine capable of running in many roles.
> Some nodes may have hardware layout that is particularly
> useful for a given role.
> * REGISTRATION - the act of creating a node in Ironic
> * ROLE - a specific workload we want to map onto one or more nodes.
> Examples include 'undercloud control plane', 'overcloud control
> plane', 'overcloud storage', 'overcloud compute' etc.
> * MANAGEMENT NODE - a node that has been mapped with an undercloud
> * SERVICE NODE - a node that has been mapped with an overcloud role
> * COMPUTE NODE - a service node that has been mapped to an
> overcloud compute role
> * CONTROLLER NODE - a service node that has been mapped to an
> overcloud controller role
> * OBJECT STORAGE NODE - a service node that has been mapped to an
> overcloud object storage role
> * BLOCK STORAGE NODE - a service node that has been mapped to an
> overcloud block storage role
> * UNDEPLOYED NODE - a node that has not been mapped with a role
> * another option - UNALLOCATED NODE - a node that has not been
> allocated through nova scheduler (?)
> - (after reading lifeless's explanation, I
> agree that "allocation" may be a
> misleading term under TripleO, so I
> personally vote for UNDEPLOYED)
> * INSTANCE - A role deployed on a node - this is where work actually
> * DEPLOYMENT
> * SIZE THE ROLES - the act of deciding how many nodes will need to be
> assigned to each role
> * another option - DISTRIBUTE NODES (?)
> - (I think the former is more accurate, but
> perhaps there's a better way to say it?)
> * SCHEDULING - the process of deciding which role is deployed on which
> * SERVICE CLASS - a further categorization within a service role for a
> particular deployment.
> * NODE PROFILE - a set of requirements that specify what attributes
> a node must have in order to be mapped to
> a service class
> Does this seem accurate? All feedback is appreciated!
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev