#2151 closed enhancement (wontfix)

consider changes needed to allow use of Amazon Glacier

Reported by: daira Owned by:
Priority: normal Milestone: undecided
Component: code-storage Version: cloud-branch
Keywords: cloud-backend s3 glacier LeastAuthority Cc:
Launchpad Bug:

Description

See https://aws.amazon.com/glacier/. There would presumably need to be some way to bring a subdirectory tree back into short-term-accessible storage without actually trying to access it. That would be difficult given the way directories are currently implemented, although one option is to only store files in Glacier.

Change History (2)

comment:1 Changed at 2014-01-14T01:39:24Z by daira

Note that Glacier's pricing model for data retrieval is very complicated, and optimizing the cost of retrieval while still doing it within a reasonable time may be tricky.

comment:2 Changed at 2020-10-30T12:35:44Z by exarkun

  • Resolution set to wontfix
  • Status changed from new to closed

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.

Note: See TracTickets for help on using tickets.