Hi Sam,
I've been trying to wrangle folks into discussions to see how we can
improve policy as a whole across OpenStack [0] [1]. So far, we've had some
involvement from a couple operators, but more feedback would be even better.
My goal is to try and generate a bunch of discussion prior to the PT
I think one of the problems we're seeing now is that a lot of operators
have actually already scratched some of these missing functionality itches
like quota management and project nesting by handling those scenarios in
external management systems. I know we certainly did at DataCentred. That
proba
Looping this into the operator's list, too!
On Wed, Jan 18, 2017 at 2:13 PM, Lance Bragstad wrote:
> Thanks to Morgan in today's policy meeting [0], we were able to shed some
> light on the reasons for keystone having two policy files. The main reason
> a second policy file was introduced was to
I would love it if all the projects policy.json was actually usable. Too many
times the policy.json isn’t the only place where authN happens with lots of
hard coded is_admin etc.
Just the ability to to have a certain role to a certain thing would be amazing.
It makes it really hard to have read
On Thu, Jan 12, 2017 at 8:40 PM, Emilien Macchi wrote:
> Greetings OpenStack community,
>
> I have been looking for a Community Goal [1] that would directly help
> Operators and I found the "run API via WSGI" useful.
> So I've decided to propose this one as a goal for Pike but I'll stay
> open to
hi,
unfortunately i noticed this thread never made it to the operators list.
there is a thread regarding the removal of Ceilometer Event API in
Ocata[1]. this is only related to the storage and access of events. the
generation of events remains in Ceilometer.
as a quick summary: the telemetry
