Open Stack

In addition to these hardcoded "admin" (and "Member") role names, for legacy reasons there are also several roles in the keystone sample data which have never been used in OpenStack (e.g. "netadmin", etc.):

https://github.com/openstack/keystone/blob/master/tools/sample_data.sh#L119

Just sayin', ;-)


-          Gabriel

From: openstack-bounces+gabriel.hurley=nebula.com at lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula.com at lists.launchpad.net] On Behalf Of Joshua Harlow
Sent: Thursday, May 10, 2012 7:13 PM
To: Salman A Baset; openstack
Subject: Re: [Openstack] 'admin' role hard-coded in keystone and nova, and policy.json

I was also wondering about this, it seems there are lots of policy.json files with hard coded roles in them, which is weird since keystone supports the creation of roles and such, but if u create a role which isn't in a policy.json then u have just caused yourself a problem, which isn't very apparent...

On 5/10/12 2:32 PM, "Salman A Baset" <sabaset at us.ibm.com> wrote:
It seems that 'admin' role is hard-coded cross nova and horizon. As a result if I want to define 'myadmin' role, and grant it all the admin privileges, it does not seem possible. Is this a recognized limitation?

Further, is there some good documentation on policy.json for nova, keystone, and glance?

Thanks.

Best Regards,

Salman A. Baset
Research Staff Member, IBM T. J. Watson Research Center
Tel: +1-914-784-6248

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120511/de52c0d6/attachment.html>