[openstack-dev] [Neutron] Rename tenant to project: discussion
Neil.Jerram at metaswitch.com
Fri Dec 4 18:23:37 UTC 2015
On 04/12/15 18:03, Kevin Benton wrote:
> >The whole world says 'tenant' for the 'tenant' concept, particularly
> in the context of networking. Changing to a different term is just
> Except for the rest of OpenStack.
Do you mean OpenStack developers, OpenStack customers, or OpenStack code?
OpenStack developers mostly say 'tenant', I'd say from my following of
All the OpenStack users/operators/customers that I've interacted with,
As far as code is concerned, I'm fine with any initiative to align the
Neutron code better with other OpenStack code - but only so long as this
is change that doesn't cause pain and loss of back-compatibility. Even
the merge pain from this change may be substantial, let alone that from
> Consistency is the one argument we can't use as a reason not to switch
> to project.
I'm not sure what you mean here.
> Please read the blueprint and the email it links
> to: https://blueprints.launchpad.net/neutron/+spec/rename-tenant-to-project
Dariusz asked for feedback, and I believe it's valid and useful for me
to give my intuitive feedback without having to read up on the history
Also it seems likely to me that the fact that this work hasn't happened,
for two years, is a reflection of most people not really wanting it. I
thought it might be helpful to get that out in the open.
That said, I did look at some of the history -
> +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.
and noted a couple of points:
1. The text here twice says "multi-tenant isolation", not "multi-project
2. This whole renaming proposal apparently stems from an internal
confusion in keystone?
More information about the OpenStack-dev