Open Stack

On 12/14/2013 01:31 PM, Tzu-Mainn Chen wrote:
> Thanks for the reply!  Let me try and address one particular section for now,
> since it seems to be the part causing the most confusion:
>
>>>      * 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... :)
> I admit that this concept was a bit fuzzy for me as well, but after a few IRC
> chats, I think I have a better handle on this.  Let me begin with my understanding of what
> happens in Heat, using Heat terminology:
>
> A Heat stack template defines RESOURCES.  When a STACK is deployed using that template,
> the resource information in the template is used to instantiate an INSTANCE of that
> resource on a NODE.  Heat can pass a FLAVOR (flavors?) to nova-scheduler in order to
> filter for appropriate nodes.
>
> So: based on that explanation, here's what Tuskar has been calling the above:
>
> HEAT TERM == TUSKAR TERM
> ------------------------
...
> INSTANCE == INSTANCE
Actually the native nova resource is OS::Nova::Server, and properties
that need server references are called server_id.

I *thought* that nova's official term for a single compute resource was
Server, and that Instance was a leftover from the AWS API, but looking
through the nova v3 API there is mentions of instances. Some
clarification and historic context from nova would help here.