[openstack-dev] tenant or project
nkinder at redhat.com
Sat Nov 23 17:09:12 UTC 2013
On 11/23/2013 08:28 AM, Tim Bell wrote:
> Horizon uses Project in the user interface, yet the openstack.rc file contains tenant_id and tenant_name. It makes it very difficult to write user guides given that such a fundamental concept has two names.
+1. I struggled with this dual-nomenclature when writing up a security
note earlier this week. I discussed it with Adam from the Keystone
project, and he said that they want the tenant term to go away and be
replaced by project. This is even mentioned in their v3 API docs:
> No problem to maintain compatibility (i.e. try OS_TENANT_NAME after OS_PROJECT_NAME) but the lack of convergence is not helping new user adoption.
> How about the technical committee makes a statement that by Icehouse we align all user facing definitions to Tenant or Project (while maintaining backwards compatibility on the environment variables) ?
I think that this is absolutely needed.
>> -----Original Message-----
>> From: Christopher Yeoh [mailto:cbkyeoh at gmail.com]
>> Sent: 23 November 2013 13:10
>> To: openstack-dev at lists.openstack.org
>> Subject: [openstack-dev] tenant or project
>> 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
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev