Frittoli, I think for other services we could achieve that by modifying the policy.json( add domain admin role and control what the cloud admin can do ) so that domain admin user is able to manage resources belong to users and projects in that domain. 2014-05-09 15:24 GMT+08:00 Frittoli, Andrea (HP Cloud) <frittoli at hp.com>: > *From:* Adam Young [mailto:ayoung at redhat.com] > *Sent:* 09 May 2014 04:19 > *To:* openstack-dev at lists.openstack.org > *Subject:* Re: [openstack-dev] Hierarchical administrative boundary > [keystone] > > > > On 05/08/2014 07:55 PM, Tiwari, Arvind wrote: > > Hi All, > > > > Below is my proposal to address VPC use case using hierarchical > administrative boundary. This topic is scheduled in Hierarchical > Multitenancy<http://junodesignsummit.sched.org/event/20465cd62e9054d4043dda156da5070e#.U2wYXXKLR_9>session of Atlanta design summit. > > > > https://wiki.openstack.org/wiki/Hierarchical_administrative_boundary > > > > Please take a look. > > > > Thanks, > > Arvind > > > > > > > _______________________________________________ > > OpenStack-dev mailing list > > OpenStack-dev at lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > Looks very good. One question: Why hierarchical domains and not > Projects. I'm not disagreeing, mind you, just that I think the Nova team > is going for hierarchical Projects. > > > *------------------------------* > > Looks good, thank you! > > > > But for this to be even more interesting nova (and other services) should > be domain aware – e.g. so that a domain admin could have control on all > resources which belong to users and projects in that domain. > > > > andrea > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Tang Yaguang Canonical Ltd. | www.ubuntu.com | www.canonical.com Mobile: +86 152 1094 6968 gpg key: 0x187F664F -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140509/4ef708a5/attachment.html>