Re: [openstack-dev] [keystone] design summit outcomes

2013-11-14 Thread Steven Hardy
On Wed, Nov 13, 2013 at 10:04:04AM -0600, Dolph Mathews wrote: I guarantee there's a few things I'm forgetting, but this is my collection of things we discussed at the summit and determined to be good things to pursue during the icehouse timeframe. The contents represent a high level mix of

Re: [openstack-dev] [keystone] design summit outcomes

2013-11-14 Thread Adam Young
On 11/14/2013 10:03 AM, Steven Hardy wrote: On Wed, Nov 13, 2013 at 10:04:04AM -0600, Dolph Mathews wrote: I guarantee there's a few things I'm forgetting, but this is my collection of things we discussed at the summit and determined to be good things to pursue during the icehouse timeframe.

[openstack-dev] [keystone] design summit outcomes

2013-11-13 Thread Dolph Mathews
I guarantee there's a few things I'm forgetting, but this is my collection of things we discussed at the summit and determined to be good things to pursue during the icehouse timeframe. The contents represent a high level mix of etherpad conclusions and hallway meetings.

Re: [openstack-dev] [keystone] design summit outcomes

2013-11-13 Thread Dolph Mathews
On Wed, Nov 13, 2013 at 11:00 AM, David Chadwick d.w.chadw...@kent.ac.ukwrote: Hi Dolph I have one comment concerning Refactoring: role assignment tables in SQL backend should be unified into a SQL table which lacks referential integrity I am not quite sure what this means, but I did

Re: [openstack-dev] [keystone] design summit outcomes

2013-11-13 Thread David Chadwick
Hi Henry I dont think the two proposals are incompatible. One table defines the attributes, similar to LDAP schema, whilst the other stores the actual assignments. I was talking about the former and you the latter in our emails. But we did discuss the former in the dev lounge as well