Open Stack

Henry, Adam, Joe et al

this is how I propose that attribute mapping is integrated into Keystone 
order to minimise code development and wasted effort

1. Henry produces code that stores groups and group memberships in Keystone

2. Henry produces code that retrieves user groups from keystone

3. Henry does not produce code that links groups to roles and that 
iterates through roles to find out who the group members are that have 
the roles. Instead

4. Kristy finishes off the super API, that given a set of input groups, 
returns the set of roles and tenants that the user is a member of. (This 
is already partly written, but is not part of the code that has already 
been submitted to git. But it will use the code that has been submitted)

5. Henry uses Kristy's code

regards

David