Open Stack

I think it would be practical to expose the authenticated user's DOMAIN_ID
and DOMAIN_NAME into the request environment for the underlying service /
middleware to consume, as we do today with TENANT_ID / TENANT_NAME (soon to
be deprecated in favor of PROJECT_ID / PROJECT_NAME).


-Dolph


On Tue, Jan 8, 2013 at 7:22 AM, Alexandra Shulman-Peleg <SHULMANA at il.ibm.com
> wrote:

> Hi,
>
> As most of you know, Keystone v3 API will introduce the notions of
> "domains" and "projects" which will replace the existing notion of tenants.
> It is important to allow using the same concepts in Swift. Since different
> domains may represent different companies, it is important to allow
> reflecting the Keystone "domain name" in the Swift "account name",
> providing an option to isolate the requests of different domains. Are there
> existing plans of adjusting Swift to Keystone v3 API? If not, I would like
> to start discussing the potential solutions.
>
> Thank you all,
> Alex.
>
>
> ----------------------------------------------------------
> Alexandra Shulman-Peleg, PhD
> Storage Research, Cloud Platforms Dept.
> IBM Haifa Research Lab
> Tel: +972-3-7689530 | Fax: +972-3-7689545
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130108/c52b125c/attachment.html>