summaryrefslogtreecommitdiff
path: root/doc/todo/special_remote_for_amazon_glacier.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-09-04 14:58:11 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-09-04 14:58:11 -0400
commitb43580ac6fd1e4a5370089d970f4f781a964e55c (patch)
tree4c3225cdc97986356d23fcc6f4ae6b7e235b7aff /doc/todo/special_remote_for_amazon_glacier.mdwn
parent6c4682b47bce2f6d866124b0b8b23ed34e913693 (diff)
add glacier todo page
Diffstat (limited to 'doc/todo/special_remote_for_amazon_glacier.mdwn')
-rw-r--r--doc/todo/special_remote_for_amazon_glacier.mdwn19
1 files changed, 19 insertions, 0 deletions
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]]