<div dir="ltr"><div>+1 for using the term "project" across all services. Projects provide multi-tenant isolation for resources across the cloud. Part of the reason we prefer "projects" in keystone is that "domains" conceptually provide multi-tenant isolation within keystone itself, so the overloaded "tenant" terminology gets really confusing.</div>
<div><br></div><div>It's been a slow process to kill the term "tenant" in keystone, here's the current status:<br></div><div><br></div><div>- the v2.0 API is finally being deprecated altogether, which should be the last mentions of "tenant"</div>
<div>- the v3 API speaks in terms of "projects"</div><div>- keystoneclient already supports "projects" from a library perspective (including auth_token)</div><div>- keystoneclient's CLI is deprecated in favor of openstackclient's CLI, which supports the "project" terminology if you pass the --identity-api-version=3 flag</div>
<br><div class="gmail_extra"><div class="gmail_quote">On Sat, Nov 23, 2013 at 7:48 AM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.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 dir="ltr">Project is what Keystone chose to standardize on for their v3 API. Lots of other APIs are affected as you can imagine. <div>
<br><div>Here's a thread <a href="http://openstack.markmail.org/thread/wyce6kvkfqexcpuu" target="_blank">http://openstack.markmail.org/thread/wyce6kvkfqexcpuu</a> <br>
</div></div><div><br></div></div></blockquote><div><br></div><div>+1, everything mentioned in that email has now happened :)</div><div> </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">
<div dir="ltr"><div></div><div>Anne</div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Sat, Nov 23, 2013 at 7:07 AM, Nick Chase <span dir="ltr"><<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.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"><p dir="ltr">From a purely documentation and explanatory standpoint I vote for "project", if we're going to standardize on one or the other. </p>
<div><div>
<div class="gmail_quote">On Nov 23, 2013 7:13 AM, "Christopher Yeoh" <<a href="mailto:cbkyeoh@gmail.com" target="_blank">cbkyeoh@gmail.com</a>> wrote:<br type="attribution"><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">
Hi,<br>
<br>
So in the past we've used both tenant and project to refer to the same<br>
thing and I think its been a source of confusion for people new to<br>
OpenStack. In the Nova code we use both, but at least for the API we've<br>
been trying to consistently present to the client tenant (which is the<br>
majority usage) rather than project.<br>
<br>
And then Russell pointed out in <a href="https://review.openstack.org/#/c/57612/" target="_blank">https://review.openstack.org/#/c/57612/</a><br>
that the Keystone uses project in the Keystone V3 API rather than<br>
tenant. <a href="http://api.openstack.org/api-ref-identity.html#identity-v3" target="_blank">http://api.openstack.org/api-ref-identity.html#identity-v3</a><br>
<br>
I think that we should be consistent across the openstack projects.<br>
>From a very quick look at the core openstack projects I think that they<br>
mostly use tenant at the moment rather than project.<br>
<br>
Does this change in Keystone nomenclature signify that we all should be<br>
moving to use project rather than tenant in the future (its not<br>
too late to do a big a search and replace for the Nova V3 API). And is<br>
the plan for Keystone python client to also change to project rather<br>
than tenant?<br>
<br>
Chris<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class=""><font color="#888888">-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><br></div>-Dolph
</div></div>