<html><body>
<p><font size="2" face="sans-serif">I have submitted a session for the Juno summit for this work: <a href="http://summit.openstack.org/cfp/details/265">http://summit.openstack.org/cfp/details/265</a></font><br>
<br>
<font size="2" face="sans-serif">Thanks,</font><br>
<br>
<font size="2" face="sans-serif">Steven Kaufer<br>
</font><br>
<tt><font size="2">Duncan Thomas <duncan.thomas@gmail.com> wrote on 04/06/2014 01:21:57 AM:<br>
<br>
> From: Duncan Thomas <duncan.thomas@gmail.com></font></tt><br>
<tt><font size="2">> To: "OpenStack Development Mailing List (not for usage questions)" <br>
> <openstack-dev@lists.openstack.org>, </font></tt><br>
<tt><font size="2">> Date: 04/06/2014 01:28 AM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] Support for multiple sort keys and sort<br>
> directions in REST GET APIs</font></tt><br>
<tt><font size="2">> <br>
> Stephen<br>
> <br>
> Mike is right, it is mostly (possibly only?) extensions that do double<br>
> lookups. Your plan looks sensible, and definitely useful. I guess I'll<br>
> see if I can actually break it once the review is up :-) I mostly<br>
> wanted to give a heads-up - there are people who are way better at<br>
> reviewing this than me.<br>
> <br>
> <br>
> <br>
> On 3 April 2014 19:15, Mike Perez <thingee@gmail.com> wrote:<br>
> > Duncan, I think the point you raise could happen even without thischange. In<br>
> > the example of listing volumes, you would first query for the list in some<br>
> > multi-key sort. The API extensions for example that add additional response<br>
> > keys will do another lookup on that resource for the appropriate column it's<br>
> > retrieving. There are some extensions that still do this unfortunately, but<br>
> > quite a few got taken care of in Havana in using cache instead of <br>
> doing these<br>
> > wasteful lookups.<br>
> ><br>
> > Overall Steven, I think this change is useful, especially from one of the<br>
> > Horizon sessions I heard in Hong Kong for filtering/sorting.<br>
> ><br>
> > --<br>
> > Mike Perez<br>
> ><br>
> > On 11:18 Thu 03 Apr , Duncan Thomas wrote:<br>
> >> Some of the cinder APIs do weird database joins and double lookups and<br>
> >> things, making every field sortable might have some serious database<br>
> >> performance impact and open up a DoS attack. Will need more<br>
> >> investigation to be sure.<br>
> >><br>
> >> On 2 April 2014 19:42, Steven Kaufer <kaufer@us.ibm.com> wrote:<br>
> >> > I have proposed blueprints in both nova and cinder for <br>
> supporting multiple<br>
> >> > sort keys and sort directions for the GET APIs (servers and <br>
> volumes). I am<br>
> >> > trying to get feedback from other projects in order to have a <br>
> more uniform<br>
> >> > API across services.<br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > OpenStack-dev@lists.openstack.org<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
> <br>
> <br>
> -- <br>
> Duncan Thomas<br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
</font></tt></body></html>