On Wed, Sep 21, 2016, at 11:05 AM, Alexander Makarov wrote: > What if policy will be manageable using RESTful API? > I'd like to validate the idea to handle policies in keystone or > affiliated service: https://review.openstack.org/#/c/325326/
As Matt said, that's unrelated to what he's asking about. However, I have asked twice now on the review what the benefit of doing this is and haven't received a response so I'll ask here. The proposal would add additional latency to nearly every API operation in a service and in return what do they get? Now that it's possible to register sane policy defaults within a project most operators do not even need to think about policy for projects that do that. And any policy changes that are necessary are easily handled by a config management system. I would expect to see a pretty significant benefit in exchange for moving policy control out of Nova, and so far it's not clear to me what that would be. > > On 21.09.2016 17:49, Matt Riedemann wrote: > > Nova has policy defaults in code now and we can generate the sample > > using oslopolicy-sample-generator but we'd like to get the default > > policy sample in the Nova developer documentation also, like we have > > for nova.conf.sample. > > > > I see we use the sphinxconfiggen extension for building the > > nova.conf.sample in our docs, but I don't see anything like that for > > generating docs for a sample policy file. > > > > Has anyone already started working on that, or is interested in > > working on that? I've never written a sphinx extension before but I'm > > guessing it could be borrowed a bit from how sphinxconfiggen was > > written in oslo.config. > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev