)]}'
{"doc/source/overview_container_sync.rst":[{"author":{"_account_id":860,"name":"Donagh McCabe","email":"donagh.mccabe@gmail.com","username":"donagh-mccabe"},"change_message_id":"73ec233fbd163f388a55b436b9fb3c0cadc89e04","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Create a container_sync_realms.conf file specifying the allowable clusters"},{"line_number":33,"context_line":"and their information::"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    [realm1]"},{"line_number":36,"context_line":"    key \u003d realm1key"},{"line_number":37,"context_line":"    cluster_name1 \u003d https://host1/v1/"},{"line_number":38,"context_line":"    cluster_name2 \u003d https://host2/v1/"}],"source_content_type":"text/x-rst","patch_set":4,"id":"AAAATn%2F9A9U%3D","line":35,"updated":"2013-12-17 17:40:55.000000000","message":"Can key be a list of two keys? Similar to tempurl. It allows you to change keys without disruption (i.e., while container_sync_realms.conf is being rolled out to different clusters).","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"},{"author":{"_account_id":1216,"name":"gholt","email":"z-launchpad@brim.net","username":"gholt"},"change_message_id":"6fa989e575aa408bd0d6f6a47b807398e1a1cb37","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Create a container_sync_realms.conf file specifying the allowable clusters"},{"line_number":33,"context_line":"and their information::"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"    [realm1]"},{"line_number":36,"context_line":"    key \u003d realm1key"},{"line_number":37,"context_line":"    cluster_name1 \u003d https://host1/v1/"},{"line_number":38,"context_line":"    cluster_name2 \u003d https://host2/v1/"}],"source_content_type":"text/x-rst","patch_set":4,"id":"AAAATn%2F9A08%3D","line":35,"in_reply_to":"AAAATn%2F9A9U%3D","updated":"2013-12-17 17:49:52.000000000","message":"Good call. I\u0027ll add that.","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"},{"author":{"_account_id":860,"name":"Donagh McCabe","email":"donagh.mccabe@gmail.com","username":"donagh-mccabe"},"change_message_id":"73ec233fbd163f388a55b436b9fb3c0cadc89e04","unresolved":false,"context_lines":[{"line_number":40,"context_line":"    [realm2]"},{"line_number":41,"context_line":"    key \u003d realm2key"},{"line_number":42,"context_line":"    cluster_name3 \u003d https://host3/v1/"},{"line_number":43,"context_line":"    cluster_name4 \u003d https://host4/v1/"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Each section name is the name of a sync realm. A sync realm is a set of"}],"source_content_type":"text/x-rst","patch_set":4,"id":"AAAATn%2F9A6Q%3D","line":43,"updated":"2013-12-17 17:40:55.000000000","message":"Would it be possible to make this work for a legacy setup. e.g., something like:\n\n    [realm3]\n    key \u003d realm3key\n    sync_to \u003d https://my.legacy.url/v1\n\nSo anywhere container-sync found a x-container-sync-to that did not start with \"//\" AND the value started with \"sync_to\" , it could act as if the user had replaced the metadata with //realm3/https://my.legacy.url/v1/a/c","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"},{"author":{"_account_id":1216,"name":"gholt","email":"z-launchpad@brim.net","username":"gholt"},"change_message_id":"6fa989e575aa408bd0d6f6a47b807398e1a1cb37","unresolved":false,"context_lines":[{"line_number":40,"context_line":"    [realm2]"},{"line_number":41,"context_line":"    key \u003d realm2key"},{"line_number":42,"context_line":"    cluster_name3 \u003d https://host3/v1/"},{"line_number":43,"context_line":"    cluster_name4 \u003d https://host4/v1/"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Each section name is the name of a sync realm. A sync realm is a set of"}],"source_content_type":"text/x-rst","patch_set":4,"id":"AAAATn%2F9A0s%3D","line":43,"in_reply_to":"AAAATn%2F9A6Q%3D","updated":"2013-12-17 17:49:52.000000000","message":"Not sure I understand on this one. Can you describe it a bit more? The main issue I have with the existing sync urls is that they could be anything.","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"},{"author":{"_account_id":860,"name":"Donagh McCabe","email":"donagh.mccabe@gmail.com","username":"donagh-mccabe"},"change_message_id":"73ec233fbd163f388a55b436b9fb3c0cadc89e04","unresolved":false,"context_lines":[{"line_number":238,"context_line":""},{"line_number":239,"context_line":"    You must be the account admin on the account to set synchronization targets"},{"line_number":240,"context_line":"    and keys."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"This is for the old-style of container syncing using allowed_sync_hosts. "},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"You simply tell each container where to sync to and give it a secret"}],"source_content_type":"text/x-rst","patch_set":4,"id":"AAAATn%2F9A54%3D","line":241,"updated":"2013-12-17 17:40:55.000000000","message":"whitespace","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"},{"author":{"_account_id":1216,"name":"gholt","email":"z-launchpad@brim.net","username":"gholt"},"change_message_id":"6fa989e575aa408bd0d6f6a47b807398e1a1cb37","unresolved":false,"context_lines":[{"line_number":238,"context_line":""},{"line_number":239,"context_line":"    You must be the account admin on the account to set synchronization targets"},{"line_number":240,"context_line":"    and keys."},{"line_number":241,"context_line":""},{"line_number":242,"context_line":"This is for the old-style of container syncing using allowed_sync_hosts. "},{"line_number":243,"context_line":""},{"line_number":244,"context_line":"You simply tell each container where to sync to and give it a secret"}],"source_content_type":"text/x-rst","patch_set":4,"id":"AAAATn%2F9A0g%3D","line":241,"in_reply_to":"AAAATn%2F9A54%3D","updated":"2013-12-17 17:49:52.000000000","message":"So picky. ;P","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"}],"etc/container_sync_realms.conf-sample":[{"author":{"_account_id":860,"name":"Donagh McCabe","email":"donagh.mccabe@gmail.com","username":"donagh-mccabe"},"change_message_id":"73ec233fbd163f388a55b436b9fb3c0cadc89e04","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"# Each section name is the name of a sync realm. A sync realm is a set of"},{"line_number":19,"context_line":"# clusters that have agreed to allow container syncing with each other. Realm"},{"line_number":20,"context_line":"# names will be considered case insensitive."},{"line_number":21,"context_line":"# "},{"line_number":22,"context_line":"# The key is the overall cluster-to-cluster key used in combination with the"},{"line_number":23,"context_line":"# external users\u0027 key that they set on their containers\u0027 X-Container-Sync-Key"}],"source_content_type":"application/octet-stream","patch_set":4,"id":"AAAATn%2F9A5w%3D","line":20,"updated":"2013-12-17 17:40:55.000000000","message":"whitespace","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"},{"author":{"_account_id":1216,"name":"gholt","email":"z-launchpad@brim.net","username":"gholt"},"change_message_id":"6fa989e575aa408bd0d6f6a47b807398e1a1cb37","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"# Each section name is the name of a sync realm. A sync realm is a set of"},{"line_number":19,"context_line":"# clusters that have agreed to allow container syncing with each other. Realm"},{"line_number":20,"context_line":"# names will be considered case insensitive."},{"line_number":21,"context_line":"# "},{"line_number":22,"context_line":"# The key is the overall cluster-to-cluster key used in combination with the"},{"line_number":23,"context_line":"# external users\u0027 key that they set on their containers\u0027 X-Container-Sync-Key"}],"source_content_type":"application/octet-stream","patch_set":4,"id":"AAAATn%2F9A0Q%3D","line":20,"in_reply_to":"AAAATn%2F9A5w%3D","updated":"2013-12-17 17:49:52.000000000","message":"Will fix","commit_id":"209c25dd7b937d6e9001c9c15fe418036ac6a0ce"}],"swift/common/container_sync_realms.py":[{"author":{"_account_id":1009,"name":"Greg Lange","email":"greglange@gmail.com","username":"greglange"},"change_message_id":"02eeaf0c57c4c2f5c0f7e0b9b53487c77bf0bef4","unresolved":false,"context_lines":[{"line_number":142,"context_line":"        the information given."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":"        :param request_method: HTTP method of the request."},{"line_number":145,"context_line":"        :param path: The path to the resource."},{"line_number":146,"context_line":"        :param nonce: A unique value for the request."},{"line_number":147,"context_line":"        :param realm_key: Shared secret at the cluster operator level."},{"line_number":148,"context_line":"        :param user_key: Shared secret at the user\u0027s container level."}],"source_content_type":"text/x-python","patch_set":5,"id":"AAAATn%2F81uw%3D","line":145,"updated":"2013-12-19 21:24:48.000000000","message":"Missing x_timestamp","commit_id":"1c7458bb95c738df2ffb772b2eeeeccff40fa7c6"}]}