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 (not for
Stephen
Mike is right, it is mostly (possibly only?) extensions that do double
lookups. Your plan looks sensible, and definitely useful. I guess I'll
see if I can actually break it once the review is up :-) I mostly
wanted to give a heads-up - there are people who are way better at
reviewing this
Duncan,
Thanks for the reply. The sorting is done in the common
sqlalchemy.utils.paginate_query function, which takes an ORM model class as
an argument
(https://github.com/openstack/oslo-incubator/blob/master/openstack/common/db/sqlalchemy/utils.py#L82).
The only valid sort columns are
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
