From b43580ac6fd1e4a5370089d970f4f781a964e55c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 4 Sep 2012 14:58:11 -0400 Subject: add glacier todo page --- doc/todo/special_remote_for_amazon_glacier.mdwn | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/todo/special_remote_for_amazon_glacier.mdwn (limited to 'doc/todo/special_remote_for_amazon_glacier.mdwn') diff --git a/doc/todo/special_remote_for_amazon_glacier.mdwn b/doc/todo/special_remote_for_amazon_glacier.mdwn new file mode 100644 index 000000000..abc7a239c --- /dev/null +++ b/doc/todo/special_remote_for_amazon_glacier.mdwn @@ -0,0 +1,19 @@ +Amazon's new glacier service would be a nice special remote to support for +long-term archival. + +The main difficulty is that glacier is organized into vaults, and accessing +a file in a vault takes ~4 hours. A naive implementation would make `git +annex get` wait for 4 hours, which is certianly not reasonable. + +One approach I am pondering is to make each glacier vault a separate +special remote. You could then request git-annex to spin up a remote, and +come back later, and be able to access the data stored in it (need to check +if glacier would also allow adding new data to it then). This is +conceptually similar to using git-annex with offline removable drives, +except with glacier, you have a controllable robot to get them plugged in. :) + +Ideally, git-annex would arrange for glacier to send it a message when the +vault becomes available, and the user could queue a list of commands to +run, or files to transfer, at that point. + +--[[Joey]] -- cgit v1.2.3