Open Stack

On 10/16/2013 12:23 PM, Dolph Mathews wrote:
> I'll be finalizing the design summit schedule [1] for keystone
> following the weekly meeting [2] on Tuesday, October 22nd 18:00 UTC.
> Please have your proposals submitted before then.
>
> So far I think everyone has done a GREAT job self-organizing the
> proposed sessions to avoid overlap, but we currently have two more
> proposals than we do slots. During the meeting, we'll review which
> sessions should be split, combined or cut.
>
> Lastly, if you have comments on a particular session regarding scope
> or scheduling, *please* take advantage of the new comments section at
> the bottom of each session proposal. Such feedback is highly
> appreciated!
>
> [1]: http://summit.openstack.org/cfp/topic/10
> [2]: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting
>
> Thanks!
>
> -Dolph
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Some suggestions:

V3 API Domain scoped tokens, and Henry Nash's purification of 
Assignments proposal are both dealing with the scoped and binding of 
authorization decisions.


Internal API stabilization and Extensions are both about code 
management, and can be combined.  I think

Auditing is going to be bigger than just Keystone, as it happens based 
on Policy enforcement.  I suspect that this session should be where we 
discuss the Keystone side of Policy.

Token Revocation and the client and auth_token middleware are all 
related topics.

We discussed Quota storage in Keystone last summit.  We have pretty good 
progress on the blueprint.  Do we really need to discuss this again, or 
do we just need to implement

The HTML talk should probably pull in members from the Horizon team.  I 
would almost want to merge it with 
http://summit.openstack.org/cfp/details/3 "UX and Future Direction of 
OpenStack Dashboard"  or
http://summit.openstack.org/cfp/details/161 "Separate Horizon and 
OpenStack Dashboard"  as we can discuss how we will split responsibility 
for managing administration and customization.  If they have an open 
slot, we might be able to move this to a Horizon talk.