<div dir="ltr">Hello, Jaromir<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 22, 2014 at 4:09 PM, Jaromir Coufal <span dir="ltr"><<a href="mailto:jcoufal@redhat.com" target="_blank">jcoufal@redhat.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im"><br></div>
I am leaning towards Role. We can be more specific with adding some extra word, e.g.:<br>
* Node Role<br></blockquote><div><br></div><div>We use this term a lot internally for the very similar purpose, so it looks reasonable to me.</div><div>Just my 2c.<br></div><div><br></div><div>--</div><div>Best regards,</div>

<div>Oleg Gelbukh</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
* Deployment Role<br>
... 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.<div class=""><div class="h5"><br>
<br>
-- Jarda<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>