Open Stack

The network info for an instance is cached as a blob of data (neutron has the canonical version in most installs), so it isn’t particularly easy to do at the database layer. You would likely need a pretty complex stored procedure to do it accurately.

Vish

On Jan 27, 2015, at 2:00 PM, Steven Kaufer <kaufer at us.ibm.com> wrote:

> Hello,
> 
> When applying an IP address filter to a paginated servers query (eg, supplying servers/detail?ip=192.168&limit=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 should be done before the limit is applied, returning up to <limit> servers that match the IP address filter.  Currently, if the servers in the page of data returned from the DB do not happen to match the IP address filter (applied in the compute API), then no servers will be returned by the REST API (even if there are servers that match the IP address filter).
> 
> This seems like a bug to me, shouldn't all filtering be done at the DB layer?
> 
> [1]: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L2037-L2042
> 
> Thanks,
> Steven Kaufer
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150127/a1085302/attachment.html>