From 0eeeae664e0ff805d5e3c6ac7bdf4394cdc96d85 Mon Sep 17 00:00:00 2001 From: John Dickinson Date: Tue, 14 Jun 2011 11:04:06 -0500 Subject: [PATCH 1/3] renamed st to swift --- bin/{st => swift} | 0 doc/source/development_saio.rst | 2 +- doc/source/howto_installmultinode.rst | 30 +++++++++++++-------------- doc/source/overview_large_objects.rst | 20 +++++++++--------- setup.py | 2 +- swift/common/middleware/staticweb.py | 12 +++++------ 6 files changed, 33 insertions(+), 33 deletions(-) rename bin/{st => swift} (100%) diff --git a/bin/st b/bin/swift similarity index 100% rename from bin/st rename to bin/swift diff --git a/doc/source/development_saio.rst b/doc/source/development_saio.rst index bbce6fdeb0..a6dc0060b6 100644 --- a/doc/source/development_saio.rst +++ b/doc/source/development_saio.rst @@ -625,7 +625,7 @@ Setting up scripts for running Swift #. `recreateaccounts` #. Get an `X-Storage-Url` and `X-Auth-Token`: ``curl -v -H 'X-Storage-User: test:tester' -H 'X-Storage-Pass: testing' http://127.0.0.1:8080/auth/v1.0`` #. Check that you can GET account: ``curl -v -H 'X-Auth-Token: ' `` - #. Check that `st` works: `st -A http://127.0.0.1:8080/auth/v1.0 -U test:tester -K testing stat` + #. Check that `swift` works: `swift -A http://127.0.0.1:8080/auth/v1.0 -U test:tester -K testing stat` #. `cp ~/swift/trunk/test/functional/sample.conf /etc/swift/func_test.conf` #. `cd ~/swift/trunk; ./.functests` (Note: functional tests will first delete everything in the configured accounts.) diff --git a/doc/source/howto_installmultinode.rst b/doc/source/howto_installmultinode.rst index 6f10e30757..abe7647db8 100644 --- a/doc/source/howto_installmultinode.rst +++ b/doc/source/howto_installmultinode.rst @@ -372,34 +372,34 @@ You run these commands from the Proxy node. curl -k -v -H 'X-Auth-Token: ' -#. Check that ``st`` works (at this point, expect zero containers, zero objects, and zero bytes):: +#. Check that ``swift`` works (at this point, expect zero containers, zero objects, and zero bytes):: - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass stat + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass stat -#. Use ``st`` to upload a few files named 'bigfile[1-2].tgz' to a container named 'myfiles':: +#. Use ``swift`` to upload a few files named 'bigfile[1-2].tgz' to a container named 'myfiles':: - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload myfiles bigfile1.tgz - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload myfiles bigfile2.tgz + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload myfiles bigfile1.tgz + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload myfiles bigfile2.tgz -#. Use ``st`` to download all files from the 'myfiles' container:: +#. Use ``swift`` to download all files from the 'myfiles' container:: - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass download myfiles + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass download myfiles -#. Use ``st`` to save a backup of your builder files to a container named 'builders'. Very important not to lose your builders!:: +#. Use ``swift`` to save a backup of your builder files to a container named 'builders'. Very important not to lose your builders!:: - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload builders /etc/swift/*.builder + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass upload builders /etc/swift/*.builder -#. Use ``st`` to list your containers:: +#. Use ``swift`` to list your containers:: - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass list + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass list -#. Use ``st`` to list the contents of your 'builders' container:: +#. Use ``swift`` to list the contents of your 'builders' container:: - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass list builders + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass list builders -#. Use ``st`` to download all files from the 'builders' container:: +#. Use ``swift`` to download all files from the 'builders' container:: - st -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass download builders + swift -A https://$PROXY_LOCAL_NET_IP:8080/auth/v1.0 -U system:root -K testpass download builders .. _add-proxy-server: diff --git a/doc/source/overview_large_objects.rst b/doc/source/overview_large_objects.rst index 01f4990732..923afb872a 100644 --- a/doc/source/overview_large_objects.rst +++ b/doc/source/overview_large_objects.rst @@ -14,24 +14,24 @@ concatenated as a single object. This also offers much greater upload speed with the possibility of parallel uploads of the segments. ---------------------------------- -Using ``st`` for Segmented Objects +Using ``swift`` for Segmented Objects ---------------------------------- -The quickest way to try out this feature is use the included ``st`` Swift Tool. +The quickest way to try out this feature is use the included ``swift`` Swift Tool. You can use the ``-S`` option to specify the segment size to use when splitting a large file. For example:: - st upload test_container -S 1073741824 large_file + swift upload test_container -S 1073741824 large_file This would split the large_file into 1G segments and begin uploading those -segments in parallel. Once all the segments have been uploaded, ``st`` will +segments in parallel. Once all the segments have been uploaded, ``swift`` will then create the manifest file so the segments can be downloaded as one. -So now, the following ``st`` command would download the entire large object:: +So now, the following ``swift`` command would download the entire large object:: - st download test_container large_file + swift download test_container large_file -``st`` uses a strict convention for its segmented object support. In the above +``swift`` uses a strict convention for its segmented object support. In the above example it will upload all the segments into a second container named test_container_segments. These segments will have names like large_file/1290206778.25/21474836480/00000000, @@ -43,7 +43,7 @@ the segment name format of /// is so that an upload of a new file with the same name won't overwrite the contents of the first until the last moment when the manifest file is updated. -``st`` will manage these segment files for you, deleting old segments on +``swift`` will manage these segment files for you, deleting old segments on deletes and overwrites, etc. You can override this behavior with the ``--leave-segments`` option if desired; this is useful if you want to have multiple versions of the same large object available. @@ -53,14 +53,14 @@ Direct API ---------- You can also work with the segments and manifests directly with HTTP requests -instead of having ``st`` do that for you. You can just upload the segments like +instead of having ``swift`` do that for you. You can just upload the segments like you would any other object and the manifest is just a zero-byte file with an extra ``X-Object-Manifest`` header. All the object segments need to be in the same container, have a common object name prefix, and their names sort in the order they should be concatenated. They don't have to be in the same container as the manifest file will be, which -is useful to keep container listings clean as explained above with ``st``. +is useful to keep container listings clean as explained above with ``swift``. The manifest file is simply a zero-byte file with the extra ``X-Object-Manifest: /`` header, where ```` is diff --git a/setup.py b/setup.py index 49b6ed278f..1d12283511 100644 --- a/setup.py +++ b/setup.py @@ -76,7 +76,7 @@ setup( ], install_requires=[], # removed for better compat scripts=[ - 'bin/st', 'bin/swift-account-auditor', + 'bin/swift', 'bin/swift-account-auditor', 'bin/swift-account-audit', 'bin/swift-account-reaper', 'bin/swift-account-replicator', 'bin/swift-account-server', 'bin/swift-container-auditor', diff --git a/swift/common/middleware/staticweb.py b/swift/common/middleware/staticweb.py index 81225a90ea..f04d4a7d55 100644 --- a/swift/common/middleware/staticweb.py +++ b/swift/common/middleware/staticweb.py @@ -74,36 +74,36 @@ the .../listing.css style sheet. If you "view source" in your browser on a listing page, you will see the well defined document structure that can be styled. -Example usage of this middleware via ``st``: +Example usage of this middleware via ``swift``: Make the container publicly readable:: - st post -r '.r:*' container + swift post -r '.r:*' container You should be able to get objects directly, but no index.html resolution or listings. Set an index file directive:: - st post -m 'web-index:index.html' container + swift post -m 'web-index:index.html' container You should be able to hit paths that have an index.html without needing to type the index.html part. Turn on listings:: - st post -m 'web-listings: true' container + swift post -m 'web-listings: true' container Now you should see object listings for paths and pseudo paths that have no index.html. Enable a custom listings style sheet:: - st post -m 'web-listings-css:listings.css' container + swift post -m 'web-listings-css:listings.css' container Set an error file:: - st post -m 'web-error:error.html' container + swift post -m 'web-error:error.html' container Now 401's should load 401error.html, 404's should load 404error.html, etc. """ From c4f0b5561ae048a406c6bd3b4310d5795de5ae88 Mon Sep 17 00:00:00 2001 From: John Dickinson Date: Tue, 14 Jun 2011 11:29:22 -0500 Subject: [PATCH 2/3] updated changelog with 1.4.1 changes --- CHANGELOG | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/CHANGELOG b/CHANGELOG index ff74a19d57..c2e56f2edd 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,3 +1,19 @@ +swift (1.4.1) + + * st renamed to swift + + * swauth was separated froms swift. It is now its own project and can be + found at https://github.com/gholt/swauth. + + * tempauth middleware added as an extremely limited auth system for dev + work. + + * Account and container listings now properly labeled UTF-8 (previously the + label was "utf8"). + + * Accounts are auto-created if an auth token is valid when the + account_autocreate proxy config parameter is set to true. + swift (1.4.0) * swift-bench now cleans up containers it creates. From 28f74380cafc542d0c1866276e1b54f4475293e7 Mon Sep 17 00:00:00 2001 From: John Dickinson Date: Tue, 14 Jun 2011 11:39:30 -0500 Subject: [PATCH 3/3] bumped version to 1.4.2 --- swift/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/swift/__init__.py b/swift/__init__.py index c26a554fbd..36791d4794 100644 --- a/swift/__init__.py +++ b/swift/__init__.py @@ -14,7 +14,7 @@ class Version(object): return '%s-dev' % (self.canonical_version,) -_version = Version('1.4.1', False) +_version = Version('1.4.2', False) __version__ = _version.pretty_version __canonical_version__ = _version.canonical_version