Fix leaky S3 ImageService abstraction
Bug #735629 reported by
Rick Harris
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
We still have code in the OpenStack API to work around the S3 ImageService leaking implementation details. Specifically, these methods:
* _convert_
* _translate_keys
* _translate_status
We need to:
* Determine whether this work-around code is still necessary?
* If it is necessary, we need to fix the S3 ImageService abstraction to conform to the BaseImageService contract
* It it's unecessary, we should just remove it
| Changed in nova: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
Revision history for this message
| John Tran (jtran) wrote | #1 |
| tags: | added: ec2 |
Revision history for this message
| Dan Prince (dan-prince) wrote | #2 |
| Changed in nova: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Is there a way to link a bug to another bug? This one is related:
https:/