The same policy rule (os_compute_api:os-server-groups) is being used
for all actions (show, index, delete, create) for server_groups REST
APIs. It is thus impossible to provide different RBAC for specific
actions based on roles. To address this changes are made to have
separate policy rules for each of action.
It has been argued that index and show may not need separate policy
rules, but most other places in nova (and OpenStack in general) do
have separate policy rules for each action. This affords the ultimate
flexibility to deployers, who can obviously use the same rule if
that is what they want. One example where show and index may be
different is that if show is restricted based on some criteria, such
that a user is able to see some resources within the tenant but not
others, then list would need to be disallowed to prevent the user
from using list to see resources they cannot show.
Reviewed: https:/ /review. openstack. org/391113 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=4a09c2210b3 c07343411a06c67 6c2d85aa0e214f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4a09c2210b3c073 43411a06c676c2d 85aa0e214f
Author: Prashanth kumar reddy <email address hidden>
Date: Thu Oct 27 07:09:01 2016 -0400
Separate CRUD policy for server_groups
The same policy rule (os_compute_ api:os- server- groups) is being used
for all actions (show, index, delete, create) for server_groups REST
APIs. It is thus impossible to provide different RBAC for specific
actions based on roles. To address this changes are made to have
separate policy rules for each of action.
It has been argued that index and show may not need separate policy
rules, but most other places in nova (and OpenStack in general) do
have separate policy rules for each action. This affords the ultimate
flexibility to deployers, who can obviously use the same rule if
that is what they want. One example where show and index may be
different is that if show is restricted based on some criteria, such
that a user is able to see some resources within the tenant but not
others, then list would need to be disallowed to prevent the user
from using list to see resources they cannot show.
Change-Id: Ica9e07f6e80257 902b4a0cc44b65f d6bad008bba
Closes-Bug: #1636157