Hello,
We are trying to understand how the various GET REST APIs handle
sorting/filtering in different NLS environments. For example, when
retrieving sorted String data (ie, display name), the order of the results
should vary based on the NLS of the caller (as opposed to having everything
I am investigating some pagination enhancements in nova and cinder (see
nova blueprint
https://blueprints.launchpad.net/nova/+spec/nova-pagination).
In cinder, it appears that all filtering is done after the volumes are
retrieved from the database (see the API.get_all function in
/1287813
Thanks for pointing this out
On 28 February 2014 20:52, Steven Kaufer kau...@us.ibm.com wrote:
I am investigating some pagination enhancements in nova and cinder(see
nova
blueprint https://blueprints.launchpad.net/nova/+spec/nova-pagination).
In cinder, it appears that all
,
sort data, etc.) that are also replicated across many components.
If no existing work is done in this area, how should this be tackled? As a
blueprint for Juno?
Thanks,
Steven Kaufer
Cloud Systems Software
kau...@us.ibm.com 507-253-5104
Dept HMYS / Bld 015-2 / G119 / Rochester, MN
First, here is some background on this topic:
http://www.gossamer-threads.com/lists/openstack/dev/2777
Does anyone have any insight as to why offset is not supported in the REST
API calls that support pagination? I realize that there are tradeoffs
when using a offset (vs. marker) but I
Jay Pipes jaypi...@gmail.com wrote on 03/18/2014 12:02:50 PM:
From: Jay Pipes jaypi...@gmail.com
To: openstack-dev@lists.openstack.org,
Date: 03/18/2014 12:15 PM
Subject: Re: [openstack-dev] Offset support in REST API pagination
On Tue, 2014-03-18 at 11:31 -0500, Steven Kaufer wrote
Please review the following blueprints, both are scoped to supporting
multiple sort key and sort directions on the API request when retrieving
volumes and servers.
https://blueprints.launchpad.net/cinder/+spec/cinder-pagination
https://blueprints.launchpad.net/nova/+spec/nova-pagination
Note
I have proposed blueprints in both nova and cinder for supporting multiple
sort keys and sort directions for the GET APIs (servers and volumes). I am
trying to get feedback from other projects in order to have a more uniform
API across services.
Problem description from nova proposal:
There
will update it
accordingly.
Does this address your concern?
Thanks,
Steven Kaufer
Duncan Thomas duncan.tho...@gmail.com wrote on 04/03/2014 05:18:47 AM:
From: Duncan Thomas duncan.tho...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
I have submitted a session for the Juno summit for this work:
http://summit.openstack.org/cfp/details/265
Thanks,
Steven Kaufer
Duncan Thomas duncan.tho...@gmail.com wrote on 04/06/2014 01:21:57 AM:
From: Duncan Thomas duncan.tho...@gmail.com
To: OpenStack Development Mailing List
I am trying to address the following use case:
- Assume that the REST APIs support returning data based on a user-defined
sort key (assuming that this get approved:
https://review.openstack.org/#/c/84451/)
- UI contains a table showing items (servers, volumes, etc.) and their
status (as a
codepaths that assume that the existing English key values would be
returned from the DB.
Is there an existing layer that would perform the mapping between the enum
values in the DB and the String keys?
Thanks,
Steven Kaufer
Jay Pipes jaypi...@gmail.com wrote on 04/23/2014 02:56:14 PM:
From: Jay
column in cinder and nova but I suspect that the
same issue exists in other components.
Thanks,
Steven Kaufer
Kevin L. Mitchell kevin.mitch...@rackspace.com
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
Adding [horizon] to the title line to get feedback from the Horizon team.
Thanks,
Steven Kaufer
Hi Steven, thx for the detailed email. Some comments inline...
On Wed, 2014-04-23 at 13:59 -0500, Steven Kaufer wrote:
I am trying to address the following use case:
- Assume that the REST
if the
migration has not completed).
Thanks,
Steven Kaufer
Jay Pipes jaypi...@gmail.com wrote on 04/28/2014 09:05:51 AM:
From: Jay Pipes jaypi...@gmail.com
To: openstack-dev@lists.openstack.org,
Date: 04/28/2014 09:07 AM
Subject: Re: [openstack-dev] [Globalization] REST API sorting by
status severity vs
in this design, please add me as a reviewer when the
blueprint is created.
Thanks!
Steven Kaufer
Best,
-jay
zhangleiqiang (Trump)
Best Regards
*From:*laserjetyang [mailto:laserjety...@gmail.com]
*Sent:* Tuesday, April 29, 2014 1:49 PM
*To:* OpenStack Development Mailing List
Here are a few ML threads on this topic:
http://lists.openstack.org/pipermail/openstack-dev/2014-March/030322.html
http://www.gossamer-threads.com/lists/openstack/dev/2777
http://lists.openstack.org/pipermail/openstack-dev/2013-November/018861.html
Thanks,
Steven Kaufer
Roman Podoliaka rpodoly
on the existence of a query parameter (ie,
include_count=1).
The details will have to be in limbo a bit until this gets resolved:
https://review.openstack.org/#/c/133660/
Thanks,
Steven Kaufer
Sean Dague s...@dague.net wrote on 11/20/2014 10:48:05 AM:
From: Sean Dague s...@dague.net
To: openstack-dev
This is a follow up to this thread from a few weeks ago:
https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg40287.html
I've updated the nova spec in this area to include the total server count
in the server_links based on the existence of an include_count query
parameter (eg: GET
The cinder client supports passing a sort key via the --sort_key argument.
The client restricts the sort keys that the user can supply to the
following:
https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/volumes.py#L28-L29
This list of sort keys is not complete. As far
servers with limit and
IP address filter
On Jan 28, 2015, at 7:05 AM, Steven Kaufer kau...@us.ibm.com wrote:
Vishvananda Ishaya vishvana...@gmail.com wrote on 01/27/2015 04:29:50
PM:
From: Vishvananda Ishaya vishvana...@gmail.com
To: OpenStack Development Mailing List (not for usage
Hello,
When applying an IP address filter to a paginated servers query (eg,
supplying servers/detail?ip=192.168limit=100), the IP address filtering is
only being applied against the non-filtered page of servers that were
retrieved from the DB; see [1].
I believe that the IP address filtering
at the DB layer.
[1]: https://review.openstack.org/#/c/131460/
Thanks,
Steven Kaufer
On Jan 27, 2015, at 2:00 PM, Steven Kaufer kau...@us.ibm.com wrote:
Hello,
When applying an IP address filter to a paginated servers query (eg,
supplying servers/detail?ip=192.168limit=100), the IP address
-cinder.2015-02-12.log
Thanks,
Steven Kaufer
On Fri, Feb 13, 2015 at 7:09 AM, Danny Al-Gaaf danny.al-g...@bisect.de
wrote:
Hi Jay,
do you have a link to the etherpad?
Danny
Am 13.02.2015 um 05:54 schrieb Jay S. Bryant:
All,
Several members of the Cinder team and I were discussing
The nova, cinder, and glance REST APIs support listing instances, volumes,
and images in a specific order. In general, the REST API supports
something like:
?sort_key=key1sort_dir=ascsort_key=key2sort_dir=desc
This sorts the results using 'key1' as the primary key (in ascending
order),
This is a follow up thread to [1]
In order to have consistency across clients, I am proposing that the client
side sorting has the following syntax: --sort key[:direction]
Where the --sort parameter is comma-separated and is used to specify one or
more sort keys and directions. The direction
. It would be a general CLI guidelines spec
which we could expand over time to include common patterns that we
prefer CLIs use when interfacing with their users.
-Sean
Thanks for the feedback.
Spec up for review at: https://review.openstack.org/#/c/145544/
Thanks,
Steven Kaufer
--
Sean
I am trying to understand which projects support a previous link for
pagination and how that support is implemented.
I believe that supporting a next link is quite common and is implemented
as:
1. Caller includes a marker query string parameter which represents the
ID of the last item in the
28 matches
Mail list logo
