In Keystone, as Dolph says, a tenant name is not globally unique, so IMHO tenant_id needs to be passed to a back-end controller to ensure uniqueness of tenant (or project).
tenant_name can be an additional information. For example it can be used in a GUI of a back-end controller, so I think it may be useful for some purpose. Thanks, Akihiro On Sun, Sep 21, 2014 at 8:46 AM, Kevin Benton <blak...@gmail.com> wrote: > Hello all, > > A patch has come up to query keystone for tenant names in the IBM > plugin. As I understand it, this was one of the reasons another > mechanism driver was reverted. Can we get some clarity on the level > of integration with Keystone that is permitted? > > Thanks > > 1. https://review.openstack.org/#/c/122382 > 2. https://review.openstack.org/#/c/118456 > > -- > Kevin Benton > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro Motoki <amot...@gmail.com> _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev