Open Stack

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 <lbragstad at gmail.com> wrote:

> 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
> currently up for review and it will be at the same time, but in
> #openstack-meeting-cp instead of #openstack-keystone [1]. We do have a list
> of action items we came up with during the meeting:
>
>    - ACTION ITEM: ayoung to repropose https://review.openstack.org/#
>    /c/391624/
>    - ACTION ITEM: lbragstad to create an official meeting
>       - Done: https://review.openstack.org/#/c/398500/
>    - ACTION ITEM: the entire group to get familiar with Apache Fortress
>       - Docs: http://directory.apache.org/fortress/
>       - Example: http://xuctarine.blogspot.ru/2016/08/apache-fortress-
>       easiest-way-to-get-full.html
>    - ACTION ITEM: the entire group to get familiar with OpenStack congress
>       - Docs: https://wiki.openstack.org/wiki/Congress
>    - ACTION ITEM: the entire group to get familiar with
>    https://github.com/admiyo/keystone/tree/url_patterns
>    <https://github.com/admiyo/keystone/tree/url_patterns>
>
> The first item on the agenda will be following up on any action items from
> previous meetings. I've already bootstrapped the next agenda in the meeting
> etherpad [2]. Thanks again to everyone who attended and I look forward to
> next week's meeting.
>
>
> [0] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%
> 23openstack-keystone.2016-11-16.log.html#t2016-11-16T16:01:43
> [1] https://review.openstack.org/#/c/398500/
> [2] https://etherpad.openstack.org/p/keystone-policy-meeting
>
> On Wed, Nov 16, 2016 at 8:32 AM, Lance Bragstad <lbragstad at gmail.com>
> wrote:
>
>> 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] https://hangouts.google.com/call/pd36j4qv5zfbldmhxeeatq6f7ae
>>
>>
>> On Fri, Nov 11, 2016 at 8:33 AM, Lance Bragstad <lbragstad at gmail.com>
>> wrote:
>>
>>> 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 works today, then we can start working on writing down what we like
>>> and don't like about the existing implementation. I'm sure most people
>>> interested in this work will already be familiar with the problem, but I
>>> want to make it easy for folks who aren't to ramp up quickly and get them
>>> into the discussion.
>>>
>>> Some have already started contributing to the etherpad! I've slowly
>>> started massaging that information into our first agenda. I'll continue to
>>> do so and send out another email on Tuesday as a reminder to familiarize
>>> yourselves with the etherpad before the meeting.
>>>
>>>
>>> Thanks!
>>>
>>>
>>> [0] https://etherpad.openstack.org/p/keystone-policy-meeting
>>>
>>> On Thu, Nov 10, 2016 at 2:36 PM, Steve Martinelli <
>>> s.martinelli at gmail.com> wrote:
>>>
>>>> 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 <lbragstad at gmail.com>
>>>> wrote:
>>>>
>>>>> 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 policy, analyze what we have currently, design an ideal solution,
>>>>> and aim for that. We can bring our progress to the PTG in Atlanta.
>>>>>
>>>>> We'll hold the meeting openly using Google Hangouts and record our
>>>>> notes using etherpad.
>>>>>
>>>>> Our first meeting will be Wednesday, November 16th from 10:00 AM –
>>>>> 11:00 AM Central (16:00 - 17:00 UTC) and it will reoccur weekly.
>>>>>
>>>>> Hangout: https://hangouts.google.com/call/pd36j4qv5zfbldmhxeeatq6f7ae
>>>>> Etherpad: https://etherpad.openstack.org/p/keystone-policy-meeting
>>>>>
>>>>> Let me know if you have any other questions, comments or concerns. I
>>>>> look forward to the first meeting!
>>>>>
>>>>> Lance
>>>>>
>>>>> ____________________________________________________________
>>>>> ______________
>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>> Unsubscribe: OpenStack-dev-request at lists.op
>>>>> enstack.org?subject:unsubscribe
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>
>>>>>
>>>>
>>>> ____________________________________________________________
>>>> ______________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe: OpenStack-dev-request at lists.op
>>>> enstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>
>
> __________________________________________________________________________
> 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/20161116/f819e226/attachment.html>