On Sat, Aug 15, 2015 at 11:02 AM Morgan Fainberg <[email protected]> wrote:
> Please do not construe a major api change as backwards incompatible. This > pagination was never supported in v3 properly/at all. > Sure, let's argue semantics! That's a useful path forward :). As we move towards tools like FreeIPA Or something similar, we will be > addressing the gap. > Is there a cross-project spec with assigned resources? I'd love to comment on it. I also assert horizon should not be managing users in the same way Keystone > should not be managing users. Horizon should show what users have access to > openstack (and this *can* be paginated) and allow for searching for a user > that is visible to keystone but does not have access to openstack so that > they can be grants access. > Is there a horizon spec that defines this? I'd love to comment on it. > The user management service would be FreeIPA in my previous example (or AD > in the environments that deploy it, etc). > > 1: you do not get to list every user visible to keystone via v3. This is > where the problems lie. > > 2: you can search for users that are visible but do not have an active > assignment (this may need some work - and is a reasonable ask). > > 2a: if the list of users is small the filter/search could return all users > > 3: you can list users with an active assignment (using the assignment > apis) and this *can* be paginated (if it does not already support > pagination) > > 4: (future view) leverage an already existing open source solution for > user management such as FreeIPA and remove/deprecate the sql-based data > store that is missing basic user management features > Hey, all of the above looks like a spec! Neat! You should propose it! Michael Code Trumps Conversation
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
