Open Stack

On Jan 22, 2014, at 7:09 AM, Jaromir Coufal <jcoufal at redhat.com> wrote:

> 
> 
> On 2014/22/01 10:00, Jaromir Coufal wrote:
>> 
>> 
>> On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
>>> Hiya - Resource is actually a Heat term that corresponds to what we're
>>> deploying within
>>> the Overcloud Stack - i.e., if we specify that we want an Overcloud
>>> with 1 Controller
>>> and 3 Compute, Heat will create a Stack that contains 1 Controller and
>>> 3 Compute
>>> Resources.
>> 
>> Then a quick question - why do we design deployment by
>> increasing/decreasing number of *instances* instead of resources?
>> 
>> -- Jarda
> 
> And one more thing - Resource is very broad term as well as Role is. The only difference is that Heat accepted 'Resource' as specific term for them (you see? they used broad term for their concept). So I am asking myself, where is difference between generic term Resource and Role? Why cannot we accept Roles? It's short, well describing...
> 
> I am leaning towards Role. We can be more specific with adding some extra word, e.g.:
> * Node Role

+1 to Node Role. I agree that “role” is being used as a generic term here. I’m still convinced it’s important to use “Node” in the name since this is the item we are describing by assigning it a certain type of role.

Liz

> * Deployment Role
> ... and if we are in the context of undercloud, people can shorten it to just Roles. But 'Resource Category' seems to me that it doesn't solve anything.
> 
> -- Jarda
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev