EC2 API does not support filters

Bug #734912 reported by justinsb
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

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.

Related branches

Revision history for this message
Devin Carlen (devcamcar) wrote :

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

Revision history for this message
Donal Lafferty (donal-lafferty) wrote :

There is a blueprint, see

However, above and the blueprint offer no reference to the EC2 interface specification. An intro to the functionality is available at

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.

Revision history for this message
Jay Pipes (jaypipes) wrote :

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 :)

Revision history for this message
justinsb (justin-fathomdb) wrote :

(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)

Revision history for this message
Jay Pipes (jaypipes) wrote :

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

Changed in nova:
status: New → Invalid
Revision history for this message
John Tran (jtran) wrote :

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

Revision history for this message
Thierry Carrez (ttx) wrote :

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers