Opened at 2013-02-11T22:52:21Z
Closed at 2020-10-30T12:35:44Z
#1919 closed defect (wontfix)
cloud backend OpenStack: send MD5 ETag
| Reported by: | davidsarah | Owned by: | davidsarah |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | code-storage | Version: | 1.9.2 |
| Keywords: | reliability storage openstack cloud-backend | Cc: | |
| Launchpad Bug: |
Description
For PUTting an OpenStack? object, the API doc says:
You can ensure end-to-end data integrity by including an MD5 checksum of your object's data in the ETag header. You are not required to include the ETag header, but it is recommended to ensure that the storage system successfully stored your object's content.
We should probably do this.
Change History (1)
comment:1 Changed at 2020-10-30T12:35:44Z by exarkun
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.
If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).
If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.
Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.