On 15/08/2013, at 3:02 AM, Jay Pipes jaypi...@gmail.com wrote:
On 08/14/2013 12:25 PM, Mac Innes, Kiall wrote:
So, Are we saying that UIs built on OpenStack APIs shouldn't be able to
show traditional pagination controls? Or am I missing how this should
work with marker/limit?
No, not
So, Are we saying that UIs built on OpenStack APIs shouldn't be able to
show traditional pagination controls? Or am I missing how this should
work with marker/limit?
e.g. for 11 pages of content, something like: 1 2 3 .. 10 11
Thanks,
Kiall
On 13/08/13 22:45, Jay Pipes wrote:
On 08/13/2013
On 08/14/2013 12:25 PM, Mac Innes, Kiall wrote:
So, Are we saying that UIs built on OpenStack APIs shouldn't be able to
show traditional pagination controls? Or am I missing how this should
work with marker/limit?
No, not quite what I'm saying. The operation to get the total number of
pages
, August 12, 2013 8:22 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [keystone] Pagination
On Mon, Aug 12, 2013 at 7:51 PM, Jamie Lennox jlen...@redhat.com wrote:
I'm not sure where it would make sense within the API to return the name
of the page/per_page variables
, August 12, 2013 5:27 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [keystone] Pagination
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
I'm working on extending the pagination into the backends. Right now, we
handle the pagination in the v3 controller class
*To:* openstack-dev@lists.openstack.org
*Subject:* Re: [openstack-dev] [keystone] Pagination
** **
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
** **
I'm working on extending the pagination into the backends. Right now, we
handle the pagination in the v3 controller class
On 08/13/2013 03:05 AM, Yee, Guang wrote:
Passing the query parameters, whatever they are, into the driver if the
given driver supports pagination and allowing the driver to override the
manager default pagination functionality seem reasonable to me.
Please do use the standards that are
Jay,
Thanks for all the various links - most useful.
To map this into keystone context, if we were to follow this logic we would:
1) Support 'limit' and 'marker' (as opposed to 'page', 'page_szie', or anything
else). These would be standard, independent of what backing store keystone was
@lists.openstack.org
Subject: Re: [openstack-dev] [keystone] Pagination
On 08/13/2013 12:55 PM, Lyle, David (Cloud Services) wrote:
The marker/limit pagination scheme is inferior.
A bold statement that flies in the face of experience and the work already done
in all the other projects.
The use
I have been one of the earliest, loudest, and most consistent PITA's about
pagination, so I probably oughta speak up. I would like to state three facts:
1. Marker + limit (e.g. forward-only) pagination is horrific for building a
user interface.
2. Pagination doesn't scale.
3. OpenStack's APIs
On 14/08/2013, at 7:40 AM, Jay Pipes jaypi...@gmail.com wrote:
On 08/13/2013 05:04 PM, Gabriel Hurley wrote:
I have been one of the earliest, loudest, and most consistent PITA's about
pagination, so I probably oughta speak up. I would like to state three facts:
1. Marker + limit (e.g.
Hi
I'm working on extending the pagination into the backends. Right now, we
handle the pagination in the v3 controller classand in fact it is disabled
right now and we return the whole list irrespective of whether page/per-page is
set in the query string, e.g.:
def paginate(cls,
The way paginated links are defined by the v3 API (via `next` and
`previous` links), it can be completely up to the driver as to what the
query parameters look like. So, the client shouldn't have (nor require) any
knowledge of how to build query parameters for pagination. It just needs to
follow
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
I'm working on extending the pagination into the backends. Right now,
we handle the pagination in the v3 controller classand in fact it
is disabled right now and we return the whole list irrespective of
whether page/per-page is set in the
On 08/12/2013 08:27 PM, Adam Young wrote:
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
I'm working on extending the pagination into the backends. Right now,
we handle the pagination in the v3 controller classand in fact it
is disabled right now and we return the whole list irrespective of
On 08/12/2013 08:33 PM, Jay Pipes wrote:
On 08/12/2013 08:27 PM, Adam Young wrote:
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
I'm working on extending the pagination into the backends. Right now,
we handle the pagination in the v3 controller classand in fact it
is disabled right now and
I'm not sure where it would make sense within the API to return the name
of the page/per_page variables to the client that doesn't involve having
already issued the call (ie returning the names within the links box
means you've already issued the query). If we standardize on the
page/per_page
for another command.
Mark
From: Adam Young [mailto:ayo...@redhat.com]
Sent: Monday, August 12, 2013 5:27 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [keystone] Pagination
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
I'm working on extending the pagination into the backends
On Mon, Aug 12, 2013 at 7:51 PM, Jamie Lennox jlen...@redhat.com wrote:
I'm not sure where it would make sense within the API to return the name
of the page/per_page variables to the client that doesn't involve having
already issued the call (ie returning the names within the links box
means
]
*Sent:* Monday, August 12, 2013 5:27 PM
*To:* openstack-dev@lists.openstack.org
*Subject:* Re: [openstack-dev] [keystone] Pagination
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
I'm working on extending the pagination into the backends. Right
now, we handle the pagination in the v3
20 matches
Mail list logo
