On Wed, 2013-12-11 at 14:15 -0500, Tzu-Mainn Chen wrote: > Hi, > > 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 > updated. > > * 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.
Must a node be a physical machine? What about a container? > * 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. OK, so "role" has implications in both Keystone-land as well as various configuration management systems (Chef, Ansible). What about just using the term "workload"? > * MANAGEMENT NODE - a node that has been mapped with an undercloud > role > * SERVICE NODE - a node that has been mapped with an overcloud role I like the above breakdowns, but instead of "mapped with an undercloud role", I'd say "runs an undercloud workload" or similar. > * 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) "FREE NODE" would be my preference here. > * INSTANCE - A role deployed on a node - this is where work actually > happens. If it's something that is deployed (eventually) using a Nova call, it should be called an "instance", yes. ++ > * DEPLOYMENT Did you want to add a definition to the term "DEPLOYMENT"? How about this? DEPLOYMENT - A collection of nodes that comprise both the under and overcloud > * 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?) Yeah, I agree with some others that "SIZE THE ROLES" sounds a bit odd. How about "SIZE THE DEPLOYMENT" or "DETERMINE DEPLOYMENT SCOPE"? > * SCHEDULING - the process of deciding which role is deployed on which > node Agree with others that this isn't really scheduling in the sense that it's not a temporal activity. How about "ASSIGN THE WORKLOADS"? > * 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 I think I still need some more information about the above two. They sound vaguely like Cobbler's system profiles... :) Best, -jay _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
