On 02/12/2016 06:40 PM, John Griffith wrote:


On Fri, Feb 12, 2016 at 5:01 AM, Sean Dague <s...@dague.net
<mailto:s...@dague.net>> 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.

             -Sean

    --
    Sean Dague
    http://dague.net

    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe:
    openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
    <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

​I honestly don't have any real feeling about one over the other; BUT I
applaud the fact that somebody was brave enough to raise the question again.

Sounds like Project is where we're supposed to be, so if we can get it
in Keystone we can all go work on updating it once and for all?​

Tis all good in keystone. If you're using keystoneauth and keystone v3 everything will work magically. However, there are still some steps locally for things like config files and whatnot.


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to