<html><body>
<p><tt><font size="2">Duncan Thomas <duncan.thomas@gmail.com> wrote on 03/04/2014 07:53:49 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: 03/04/2014 08:06 AM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [Cinder] Get volumes REST API with <br>
> filters and limit</font></tt><br>
<tt><font size="2">> <br>
> Definitely file a bug... a script to reproduce would be fantastic.<br>
> Needs to be fixed... I don't think you need a blueprint if the fix is<br>
> simple, but if you're making deep changes then a blueprint always<br>
> helps.#</font></tt><br>
<br>
<tt><font size="2">Bug created: </font></tt><tt><font size="2"><a href="https://bugs.launchpad.net/cinder/+bug/1287813">https://bugs.launchpad.net/cinder/+bug/1287813</a></font></tt><br>
<tt><font size="2"><br>
> <br>
> Thanks for pointing this out<br>
> <br>
> On 28 February 2014 20:52, Steven Kaufer <kaufer@us.ibm.com> wrote:<br>
> > I am investigating some pagination enhancements in nova and cinder(see nova<br>
> > blueprint <a href="https://blueprints.launchpad.net/nova/+spec/nova-pagination">https://blueprints.launchpad.net/nova/+spec/nova-pagination</a>).<br>
> ><br>
> > In cinder, it appears that all filtering is done after the volumes are<br>
> > retrieved from the database (see the API.get_all function in<br>
> > <a href="https://github.com/openstack/cinder/blob/master/cinder/volume/api.py">https://github.com/openstack/cinder/blob/master/cinder/volume/api.py</a>).<br>
> > Therefore, the usage combination of filters and limit will only work if all<br>
> > volumes matching the filters are in the page of data being retrieved from<br>
> > the database.<br>
> ><br>
> > For example, assume that all of the volumes with a name of "foo" would be<br>
> > retrieved from the database starting at index 100 and that you query for all<br>
> > volumes with a name of "foo" while specifying a limit of 50. In this case,<br>
> > the query would yield 0 results since the filter did not match any of the<br>
> > first 50 entries retrieved from the database.<br>
> ><br>
> > Is this a known problem?<br>
> > Is this considered a bug?<br>
> > How should this get resolved? As a blueprint for juno?<br>
> ><br>
> > I am new to the community and am trying to determine how this should be<br>
> > addressed.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Steven Kaufer<br>
> ><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>
> -- <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>
Thanks,</font></tt><br>
<br>
<tt><font size="2">Steven Kaufer</font></tt></body></html>