[openstack-dev] [nova] policy names for API extensions
Christopher Yeoh
cbkyeoh at gmail.com
Wed May 29 07:43:52 UTC 2013
On Wed, May 29, 2013 at 3:40 AM, Kevin L. Mitchell <
kevin.mitchell at rackspace.com> wrote:
> On Fri, 2013-05-24 at 13:59 +0930, Christopher Yeoh wrote:
> > What I'd like to do for only the V3 API is to change the convention so
> > the name used for an extension's policy to be the same as the alias
> > definition. This would make things more difficult for a
> > Grizzly->Havana upgrade, but long term I think its worth it.
>
> One comment I have is that we have a few V2 extensions that have
> multiple authorizors; generally, they have one interface accessible to
> the general user and one that should be restricted to administrative
> access. I think they generally use ':' to append a differentiator, but
> I wanted to point this out, since any policy naming scheme needs to take
> this use into account…
>
I think we can still keep that convention. So for example "quotas:update"
would change to
"v3:os-quota-sets:update".
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130529/17e46892/attachment.html>
More information about the OpenStack-dev
mailing list