<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/17/2015 09:53 PM, David Lyle
wrote:<br>
</div>
<blockquote
cite="mid:CAFFhzB6kLjf3jbn4A061Q9dFmjEMnYa8hgHEfT8DEmT4D5wZgg@mail.gmail.com"
type="cite">
<p dir="ltr">I think we've conveniently been led off track here.
The original request/subject was regarding pagination of
projects in the v3 API. Since this is purely a keystone
construct it seems implausible to me that ldap or the IdP of
choice would be limiting the ability to return a paginated list
of all projects. Or groups or domains or roles for that matter.</p>
</blockquote>
<br>
Yeah, SQL can support it. LDAP assignment can't. But that is not
going to have a long life.<br>
<br>
With Hierarchical projects, we'll probably also have to keep nesting
in mind for how we display a project list: do we always show a flat
list, or is a tree closer to what users expect?<br>
<br>
Both are going to work poorly for some deployments and work well for
others.<br>
<br>
<blockquote
cite="mid:CAFFhzB6kLjf3jbn4A061Q9dFmjEMnYa8hgHEfT8DEmT4D5wZgg@mail.gmail.com"
type="cite">
<p dir="ltr">There is no reason to punt on pagination across the
API for one resource type, which actually would also work with
select backends. Give me something that I can exhaustively list
in the API I can build from. </p>
</blockquote>
<blockquote
cite="mid:CAFFhzB6kLjf3jbn4A061Q9dFmjEMnYa8hgHEfT8DEmT4D5wZgg@mail.gmail.com"
type="cite">
<p dir="ltr">David</p>
<div class="gmail_quote">On Aug 17, 2015 10:53 AM, "Fox, Kevin M"
<<a moz-do-not-send="true" href="mailto:Kevin.Fox@pnnl.gov">Kevin.Fox@pnnl.gov</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">1. yes, but
probably only if its a short list. It may be feasible to show
it only if there are 5 or less pages, and maybe just load all
pages of data and paginate it on the client. If too big, ask
the user to refine their search? Or always paginate to 5, and
then the 6th page have a page requesting further refinement?<br>
<br>
2. Not sure what the difference between searching and
filtering is in this context? something like facets? If so,
probably the 5 or less thing would work here too.<br>
<br>
3. Yes, but again, probably within a smaller set of pages?<br>
<br>
Thanks,<br>
Kevin<br>
________________________________________<br>
From: Kruithof, Piet [<a moz-do-not-send="true"
href="mailto:pieter.c.kruithof-jr@hp.com">pieter.c.kruithof-jr@hp.com</a>]<br>
Sent: Sunday, August 16, 2015 9:41 AM<br>
To: <a moz-do-not-send="true"
href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: Re: [openstack-dev] [UX] [Keystone] [Horizon]
Pagination support for Identity dashboard entities<br>
<br>
I like Michael’s response because it moved the thread towards
identifying actual user needs before digging into the
technical feasibility. IMHO, it would be helpful to have a
few people on the list answer his questions:<br>
<br>
1 - Do users want to page through search results?<br>
<br>
<br>
2 - Do users want to page through filter results? (do they use
filter results?)<br>
<br>
<br>
3 - If they want to page, do they want to be able to go back a
page and/or know their current page?<br>
<br>
<br>
I understand that even if we answer “yes” to all three
questions that there could be issues around implementation,
but at least we’ll know a gap exists.<br>
<br>
<br>
Piet Kruithof<br>
Sr UX Architect, HP Helion Cloud<br>
PTL, OpenStack UX project<br>
<br>
"For every complex problem, there is a solution that is
simple, neat and wrong.”<br>
<br>
H L Menken<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>