Out of date with AWS API
Bug #520265 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eucalyptus |
Fix Released
|
Undecided
|
chris grzegorczyk | ||
eucalyptus (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
This is a wishlist really: Amazon AWS versions their API and as they add features the API moves; it would be great to support the latest and greatest API facilities, but its not trivial.
One thing that could be done to make this better is documentation: Amazon clearly document the API version they support and provide docs for each release (and you can use old releases too). We should document the API version we are current with (searching for UEC API version doesn't return anything remotely useful).
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in eucalyptus: | |
assignee: | nobody → chris grzegorczyk (chris-grze) |
status: | New → Triaged |
To post a comment you must log in.
While not addressing the entire issue you indicate, the current lucid package (which is r1180) includes fixes which restore client compatibility for the SOAP interface up to api-2009-11-30 and tools-46266:
------- ------- ------- ------- ------- ------- ------- ------- ---- ------- ------- ------- ------- ------- ------- ------- ----
revno: 1176
committer: decker <decker@hawaii>
branch nick: 1.6.2
timestamp: Fri 2010-02-05 04:17:25 -0800
message:
fixes for common operations to restore client compatibility for ec2 41510, 41620, 42584, 45772, 46266.
-------