Re: [openstack-dev] [keystone] Weekly Policy Meeting

2016-11-16 Thread Steve Martinelli
May I could suggest another action item? I think we need clear use cases. What policy and authorization capabilities are users expecting keystone to have? What are the short-comings of the implementation we have today? On Wed, Nov 16, 2016 at 1:06 PM, Lance Bragstad wrote:

Re: [openstack-dev] [keystone] Weekly Policy Meeting

2016-11-16 Thread Lance Bragstad
We had some issues using Hangouts because we hit the maximum limit of attendees. To make it so that everyone could participate equally, we moved the meeting to #openstack-keystone [0]. I have an action item to propose an official meeting to the irc-meetings repository. Patch for the meeting is

Re: [openstack-dev] [keystone] Weekly Policy Meeting

2016-11-16 Thread Lance Bragstad
Just sending out a reminder that we'll be having our first meeting in 90 minutes. You can find all information about our agenda in the etherpad [0] as well as a link to the hangout [1]. See you there! [0] https://etherpad.openstack.org/p/keystone-policy-meeting [1]

Re: [openstack-dev] [keystone] Weekly Policy Meeting

2016-11-11 Thread Lance Bragstad
I've added some initial content to the etherpad [0], to get things rolling. Since this is going to be a recurring thing, I'd like our first meeting to level set the playing field for everyone. Let's spend some time getting familiar with policy concepts, understand exactly how OpenStack policy

Re: [openstack-dev] [keystone] Weekly Policy Meeting

2016-11-10 Thread Steve Martinelli
Thanks for taking the initiative Lance! It'll be great to hear some ideas that are capable of making policy more fine grained, and keeping things backwards compatible. On Thu, Nov 10, 2016 at 3:30 PM, Lance Bragstad wrote: > Hi folks, > > After hearing the recaps from the

[openstack-dev] [keystone] Weekly Policy Meeting

2016-11-10 Thread Lance Bragstad
Hi folks, After hearing the recaps from the summit, it sounds like policy was a hot topic (per usual). This is also reinforced by the fact every release we have specifications proposed to re-do policy in some way. It's no doubt policy in OpenStack needs work. Let's dedicate an hour a week to