[openstack-dev] [all] tenant vs. project
me at ronaldbradford.com
Fri Feb 12 16:32:27 UTC 2016
I am taking on the task in the Oslo Logging/Context projects to ensure
project replaces a deprecated use of tenant.
This includes the end user/operator view of logging configuration options
 replacing tenant with project, and RequestContext used across most
projects that has an inconsistent mixture of terms.
Web Site: http://ronaldbradford.com
Twitter: @RonaldBradford <http://twitter.com/ronaldbradford>
On Fri, Feb 12, 2016 at 10:34 AM, Monty Taylor <mordred at inaugust.com> wrote:
> On 02/12/2016 07:36 AM, Jay Pipes wrote:
>> On 02/12/2016 07:01 AM, Sean Dague wrote:
>>> Ok... this is going to be one of those threads, but I wanted to try to
>>> get resolution here.
>>> OpenStack is wildly inconsistent in it's use of tenant vs. project. As
>>> someone that wasn't here at the beginning, I'm not even sure which one
>>> we are supposed to be transitioning from -> to.
>>> At a minimum I'd like to make all of devstack use 1 term, which is the
>>> term we're trying to get to. That will help move the needle.
>>> However, again, I'm not sure which one that is supposed to be (comments
>>> in various places show movement in both directions). So people with
>>> deeper knowledge here, can you speak up as to which is the deprecated
>>> term and which is the term moving forward.
>> "Project" is the term that should be used.
> FWIW - The ansible modules in ansible 2.0 (as well as the shade library)
> use the term "project" regardless of whether the cloud in question is
> running keystone v2 or v3. It's the least I could do to try to nudge
> consumption in the right direction.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev