Open Stack

> >        * created as part of undercloud install process
> >        * can create additional management nodes (F)
> >     * Resource nodes
> >
> >                         ^ nodes is again confusing layers - nodes are
> > what things are deployed to, but they aren't the entry point
> >
> > Can you, please be a bit more specific here? I don't understand this note.
> 
> By the way, can you get your email client to insert > before the text
> you are replying to rather than HTML | marks? Hard to tell what I
> wrote and what you did :).
> 
> By that note I meant, that Nodes are not resources, Resource instances
> run on Nodes. Nodes are the generic pool of hardware we can deploy
> things onto.

I don't think "resource nodes" is intended to imply that nodes are resources; rather, it's supposed to
indicate that it's a node where a resource instance runs.  It's supposed to separate it from "management node"
and "unallocated node".

> >     * Unallocated nodes
> >
> > This implies an 'allocation' step, that we don't have - how about
> > 'Idle nodes' or something.
> >
> > It can be auto-allocation. I don't see problem with 'unallocated' term.
> 
> Ok, it's not a biggy. I do think it will frame things poorly and lead
> to an expectation about how TripleO works that doesn't match how it
> does, but we can change it later if I'm right, and if I'm wrong, well
> it won't be the first time :).
> 

I'm interested in what the distinction you're making here is.  I'd rather get things
defined correctly the first time, and it's very possible that I'm missing a fundamental
definition here.


Mainn