EC2 API does not support filters

[justinsb]

OpenStack's implementation of the EC2 API does not support filters. Some EC2 methods use filters instead of specified parameters (e.g. DescribeSnapshots has no way of specifying a particular volume without filters). As a user of the EC2 API, I use filters, and not having filters makes OpenStack's EC2 implementation incompatible.

[Devin Carlen (devcamcar)]

I think this would be better as a blueprint than a bug.

[Donal Lafferty (donal-lafferty)]

There is a blueprint, see https://blueprints.launchpad.net/nova/+spec/support-ec2-filters

However, above and the blueprint offer no reference to the EC2 interface specification. An intro to the functionality is available at http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?Using_Filtering.html

The terms of use for the site above indicate that it's protected by copyright, so the implementation of filters should be open. The list of patents governing the site is both extensive and non-exhaustive, but I would be surprised were there not prior art in the area list filtering.

[Jay Pipes (jaypipes)]

Sorry, Donal, but I'm not quite understanding whether you are saying we should *not* do this, or that we *should* do this, but can implement filtering however we like? Or something else? Sorry, IANAL and all that :)

[justinsb (justin-fathomdb)]

(To be fair to Devin, I think I only opened that blueprint yesterday... largely in response to his request, and also so that we can discuss this at the design summit)

[Jay Pipes (jaypipes)]

Marking Invalid as we'll just track this on the blueprint...

[John Tran (jtran)]

Any idea if this is going to make it to diablo?

[Thierry Carrez (ttx)]

Hey John, Justin has been difficult to reach lately, so I don't really know. His branch definitely needs some refresh before it can get in Diablo. Please followup status at https://blueprints.launchpad.net/nova/+spec/support-ec2-filters