| *** mhen_ is now known as mhen | 01:50 | |
| *** ioannis is now known as Guest6418 | 07:49 | |
| sylvr | Good morning ! I'm reading the doc at https://stackhpc-kayobe-config.readthedocs.io/en/stackhpc-2024.1/configuration/cephadm.html to try to deploy a ceph cluster through kayobe, but there's a directory I never encountered before and seems to be deployment specific and I'd like to know more about it `etc/kayobe/environments/<env>/` what are "environments" in this scenario ? | 08:52 |
|---|---|---|
| sylvr | Thanks ! :) | 08:52 |
| __Piotrek | Hello, I've created this stackoverflow question and was wondering if I could get some help trying to understand how to set up my policy configuration to allow selected user(s) the ability to list all flavors (private and belonging to other projects): https://stackoverflow.com/questions/79066658/is-there-a-way-to-list-flavors-belonging-to-other-projects-as-non-admin | 15:00 |
| DHE | in general, why would you want to see flavours you can't use? | 15:04 |
| __Piotrek | Well, the user in question has the authorization privileges to update project-specific properties. In this case, we'd like the user to associate a flavor with the corresponding project, based on predefined criteria. | 15:15 |
| __Piotrek | So, we'd like the user to get the list of all flavours and then consult project-specific criteria w.r.t. each of the flavours. | 15:16 |
| __Piotrek | So, to rephrase my question from earlier: is there a policy configuration for accessing /flavors in nova's api to allow users other than admin? | 18:20 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!