Open Stack

+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.

It's been a slow process to kill the term "tenant" in keystone, here's the
current status:

- the v2.0 API is finally being deprecated altogether, which should be the
last mentions of "tenant"
- the v3 API speaks in terms of "projects"
- keystoneclient already supports "projects" from a library perspective
(including auth_token)
- 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

On Sat, Nov 23, 2013 at 7:48 AM, Anne Gentle
<annegentle at justwriteclick.com>wrote:

> Project is what Keystone chose to standardize on for their v3 API. Lots of
> other APIs are affected as you can imagine.
>
> Here's a thread http://openstack.markmail.org/thread/wyce6kvkfqexcpuu
>
>
+1, everything mentioned in that email has now happened :)


> Anne
>
>
> On Sat, Nov 23, 2013 at 7:07 AM, Nick Chase <nchase at mirantis.com> wrote:
>
>> From a purely documentation and explanatory standpoint I vote for
>> "project", if we're going to standardize on one or the other.
>>  On Nov 23, 2013 7:13 AM, "Christopher Yeoh" <cbkyeoh at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> So in the past we've used both tenant and project to refer to the same
>>> thing and I think its been a source of confusion for people new to
>>> OpenStack. In the Nova code we use both, but at least for the API we've
>>> been trying to consistently present to the client tenant (which is the
>>> majority usage) rather than project.
>>>
>>> And then Russell pointed out in https://review.openstack.org/#/c/57612/
>>> that the Keystone uses project in the Keystone V3 API rather than
>>> tenant. http://api.openstack.org/api-ref-identity.html#identity-v3
>>>
>>> I think that we should be consistent across the openstack projects.
>>> From a very quick look at the core openstack projects I think that they
>>> mostly use tenant at the moment rather than project.
>>>
>>> Does this change in Keystone nomenclature signify that we all should be
>>> moving to use project rather than tenant in the future (its not
>>> too late to do a big a search and replace for the Nova V3 API). And is
>>> the plan for Keystone python client to also change to project rather
>>> than tenant?
>>>
>>> Chris
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Anne Gentle
> annegentle at justwriteclick.com
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

-Dolph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131123/139b2ced/attachment.html>