diff options
| author | Robert Francis <robefran@ca.ibm.com> | 2015-10-07 15:14:58 -0400 |
|---|---|---|
| committer | Alistair Coles <alistairncoles@gmail.com> | 2017-12-13 21:26:12 +0000 |
| commit | 99b89aea1051208e3d71afa35fcd62035e702628 (patch) | |
| tree | 885752bbe9c35e23695accd63b0714ea28bde579 /doc/source/overview_container_sync.rst | |
| parent | 0e95730eb36648d35e1fab13cf899600f5d9090f (diff) | |
| download | swift-99b89aea1051208e3d71afa35fcd62035e702628.tar.gz | |
Symlink implementation.
Add a symbolic link ("symlink") object support to Swift. This
object will reference another object. GET and HEAD
requests for a symlink object will operate on the referenced object.
DELETE and PUT requests for a symlink object will operate on the
symlink object, not the referenced object, and will delete or
overwrite it, respectively.
POST requests are *not* forwarded to the referenced object and should
be sent directly. POST requests sent to a symlink object will
result in a 307 Error.
Historical information on symlink design can be found here:
https://github.com/openstack/swift-specs/blob/master/specs/in_progress/symlinks.rst.
https://etherpad.openstack.org/p/swift_symlinks
Co-Authored-By: Thiago da Silva <thiago@redhat.com>
Co-Authored-By: Janie Richling <jrichli@us.ibm.com>
Co-Authored-By: Kazuhiro MIYAHARA <miyahara.kazuhiro@lab.ntt.co.jp>
Co-Authored-By: Kota Tsuyuzaki <tsuyuzaki.kota@lab.ntt.co.jp>
Change-Id: I838ed71bacb3e33916db8dd42c7880d5bb9f8e18
Signed-off-by: Thiago da Silva <thiago@redhat.com>
Diffstat (limited to 'doc/source/overview_container_sync.rst')
| -rw-r--r-- | doc/source/overview_container_sync.rst | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/source/overview_container_sync.rst b/doc/source/overview_container_sync.rst index 45a30b42b..a790e46d4 100644 --- a/doc/source/overview_container_sync.rst +++ b/doc/source/overview_container_sync.rst @@ -36,9 +36,15 @@ synchronization key. .. note:: If you are using encryption middleware in the cluster from which objects - are being synced, then you should follow the instructions to configure + are being synced, then you should follow the instructions for :ref:`container_sync_client_config` to be compatible with encryption. +.. note:: + + If you are using symlink middleware in the cluster from which objects + are being synced, then you should follow the instructions for + :ref:`symlink_container_sync_client_config` to be compatible with symlinks. + -------------------------- Configuring Container Sync -------------------------- @@ -440,7 +446,7 @@ then a symlink to the container database is created in a sync-containers sub-directory on the same device. Similarly, when the container sync metadata keys are deleted, the container -server and container-replicator would take care of deleting the symlinks +server and container-replicator would take care of deleting the symlinks from ``sync-containers``. .. note:: |