| opendevreview | OpenStack Proposal Bot proposed openstack/glance master: Imported Translations from Zanata https://review.opendev.org/c/openstack/glance/+/813565 | 02:54 |
|---|---|---|
| *** EugenMayer4 is now known as EugenMayer | 07:34 | |
| *** akekane_ is now known as abhishekk | 07:52 | |
| opendevreview | Mridula Joshi proposed openstack/glance-specs master: Expose store specific information https://review.opendev.org/c/openstack/glance-specs/+/817391 | 08:33 |
| opendevreview | Merged openstack/glance_store master: Cleanup devstack jobs https://review.opendev.org/c/openstack/glance_store/+/817344 | 11:13 |
| opendevreview | Mridula Joshi proposed openstack/glance-specs master: Append new tags to existing tags https://review.opendev.org/c/openstack/glance-specs/+/813429 | 11:28 |
| lbragstad | pdeore did you have some rbac questions? | 14:04 |
| pdeore | lbragstad, yeah just wanted a brief idea of how much impact the new role project-manager would have on the current project personas? | 14:04 |
| pdeore | I've gone thro' the updated patch of RBAC community goals, but couldn't get which image apis would be impacted with this new role | 14:05 |
| lbragstad | pdeore that's a good question | 14:05 |
| lbragstad | pulling up the image API docs | 14:06 |
| lbragstad | it looks like most of the image API is exposed to project-members | 14:09 |
| pdeore | yes, except publicize_image and some metadef apis | 14:10 |
| lbragstad | with the exception of copy_image, manage_image_cache, delete_image_location, and publicize_image (which all require role:admin) | 14:10 |
| pdeore | yes | 14:10 |
| lbragstad | so - i guess if there is a use case to expose one of those to a project-manager, then maybe? | 14:11 |
| lbragstad | i doubt poublicize_image would fall into that category, since it affects every project in the deployment, that should remain project-admin specific | 14:11 |
| pdeore | right | 14:12 |
| lbragstad | i think image location APIs (delete_image_location) requires knowledge of the underlying storage configuration ( dansmith can keep me honest here) | 14:12 |
| lbragstad | so - i'm not sure how useful it is to expose that to privileged end-users | 14:12 |
| lbragstad | manage_image_cache and copy_image feel like that fall into the same category - where they require knowledge about the deployment, right? | 14:13 |
| pdeore | yes | 14:14 |
| lbragstad | so - maybe the project-manager personas isn't necessary useful for glance (at least initially) | 14:15 |
| lbragstad | persona* | 14:15 |
| pdeore | hmm looks so... | 14:15 |
| lbragstad | but - glance doesn't need to use it if there isn't a valid use case for it - it'll be there if presents itself in the future though | 14:16 |
| lbragstad | if one presents* | 14:16 |
| pdeore | yeah, atm I don't see any valid use case in glance, but I think it would be more clear if abhishekk or dansmith give ack on this.. :) | 14:20 |
| lbragstad | ++ | 14:20 |
| pdeore | and same with system scope right? there won't be system personas required for glance, right? | 14:22 |
| rosmaita | probably for image sharing ... you might not just want any ol' member in your project to share images | 14:32 |
| rosmaita | (for project-manager use-case ^^) | 14:32 |
| dansmith | hmm, I was going to say probably nothing for manager, but yeah sharing might be legit | 14:38 |
| dansmith | it's member now, AFAIK, but maybe if we *had* the extra level, it would make sense to go there | 14:38 |
| *** whoami-rajat__ is now known as whoami-rajat | 17:42 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!