Finer access control in os-volume_attachments
Bug #1108222 reported by
Andrew Laski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Andrew Laski |
Bug Description
Currently it is only possible to restrict access through policy.json to the volumes API extension in an all or nothing way. There is not a way to allow a user with role 'a' to view details of volumes and attachments, while requiring role 'b' to create/delete them.
Changed in nova: | |
assignee: | nobody → Andrew Laski (alaski) |
Changed in nova: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/20643
Review: https:/