If you are willing to change every services policy file, then you can do it. Every service assumes any user with the role "admin" as superuser. Due to this "admin" in one service is by default "admin" in other service. As a first step you need to define "NovaAdmin" , "NeutronAdmin" and change the respective services policy file to use that role. This isolates one service's admin from becoming "admin" for another service.
What do you mean by restrict power at tenant level. All the service operations operate on tenant level except keystone operations. Do you have an example of any service operation which doesn't operate on tenant level?
Restrict power of admin at tenant level means, consider two projects Project A and Project B who have Admin A and Admin B respectively, Now I want the Admin A to modify only the resources and Users of Project A but not Project B and Admin B of Project B Only.
This is keystone operation. You can't do this in keystone v2. You can do this in keystone v3. Look at keystone https://github.com/openstack/keystone... . If you use v3cloudsample.json as policy file ( with some modification) you an do that
Asked: 2015-02-11 23:59:14 -0500
Seen: 730 times
Last updated: Feb 12 '15
