Open Stack

Not sure how much time it would require at the PTG - but I'd really like to
discuss the ability to add in-code descriptions of oslo.policy objects, and
eventually whatever we need to advertise new defaults. I'm hoping this will
help OpenStack as a whole move towards providing better policy
out-of-the-box.

The keystone group has mentioned a few times that we'd like to vet the
approach nova took towards moving policy into code using oslo.policy. I've
been trying to synchronize keystone's efforts [0] [1] with John Garbutt
(@johnthetubaguy), who is working on the nova side of things [2].

I'd be happy to help organize anything needed to make these discussions as
productive as possible in Atlanta. We can use the cross-project policy
meeting to prepare for this, too [3].


[0] https://review.openstack.org/#/c/428453/
[1] https://review.openstack.org/#/c/428454/
[2] https://review.openstack.org/#/c/427872/
[3] http://eavesdrop.openstack.org/#Keystone_Policy_Meeting

On Mon, Feb 6, 2017 at 2:27 AM, ChangBo Guo <glongwave at gmail.com> wrote:

> Hi folks,
>
> Oslo, as OpenStack project shared common libraries need more ideas and
> suggestiion to make these libraries more useful. PTG is good event to
> collect ideas and solve problems, so please take your ideas, requirements
> or problem to the PTG, and feel free to edit
> https://etherpad.openstack.org/p/oslo-ptg-pike
>
> --
> ChangBo Guo(gcb)
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170206/24e595ad/attachment.html>