Comment 12 for bug 1472031
Revision history for this message
| John Griffith (john-griffith) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
demo site
(Get the code!)
Oh... I almost forgot, the point WRT to the items Anna pointed out:
I'm not sure how/why you would have a user that can auth but not have the ability to create via policy. It might well be a use case, so they have an admin that is the only one allowed to create volumes, and then those are given out for use by tenants perhaps. Makes sense for things like internal services maybe (DB as a service etc).
That being said, I'm not sure why types would be considered confidential or sensitive info. Consistency groups.. well, that's just ugly leaky abstraction IMHO. The type info and CG info currently are public and available to all tenants so not sure that's a concern. We are working on private types, at which point this might matter, but not sure I see the security impact.
Just my opinions on this; easy to fix either way I think.