openstack/swift
Code Issues Proposed changes

Spell check on .rst files for Swift, should be minimal impact. Example is changing "to of from" to "to or from" in the overview_architecture.rst file.

Browse Source
This commit is contained in:
Anne Gentle 2010-10-14 19:07:08 +00:00 committed by Tarmac
commit 2a0f3f8c4b
5 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/admin_guide.rst
View File

@ -209,7 +209,7 @@ Debugging Tips and Tools
When a request is made to Swift, it is given a unique transaction id. This When a request is made to Swift, it is given a unique transaction id. This
id should be in every log line that has to do with that request. This can id should be in every log line that has to do with that request. This can
be usefult when looking at all the services that are hit by a single request. be useful when looking at all the services that are hit by a single request.
If you need to know where a specific account, container or object is in the If you need to know where a specific account, container or object is in the
cluster, `swift-get-nodes` will show the location where each replica should be. cluster, `swift-get-nodes` will show the location where each replica should be.

4
doc/source/development_auth.rst
View File

@ -39,8 +39,8 @@ will be omitted.
It is highly recommended that authentication server implementers prefix their It is highly recommended that authentication server implementers prefix their
tokens and Swift storage accounts they create with a configurable reseller tokens and Swift storage accounts they create with a configurable reseller
prefix (`AUTH_` by default with the included DevAuth). This prefix will allow prefix (`AUTH_` by default with the included DevAuth). This prefix will avoid
deconflicting with other authentication servers that might be using the same conflicts with other authentication servers that might be using the same
Swift cluster. Otherwise, the Swift cluster will have to try all the resellers Swift cluster. Otherwise, the Swift cluster will have to try all the resellers
until one validates a token or all fail. until one validates a token or all fail.

2
doc/source/getting_started.rst
View File

@ -15,7 +15,7 @@ most Linux platforms with the following software:
And the following python libraries: And the following python libraries:
* Eventlet 0.9.8 * Eventlet 0.9.8
* Webob 0.9.8 * WebOb 0.9.8
* Setuptools * Setuptools
* Simplejson * Simplejson
* Xattr * Xattr

4
doc/source/overview_architecture.rst
View File

@ -18,7 +18,7 @@ example, if a server is unavailable for an object PUT, it will ask the
ring for a handoff server and route there instead. ring for a handoff server and route there instead.
When objects are streamed to or from an object server, they are streamed When objects are streamed to or from an object server, they are streamed
directly through the proxy server to of from the user -- the proxy server directly through the proxy server to or from the user -- the proxy server
does not spool them. does not spool them.
-------- --------
@ -32,7 +32,7 @@ container, or account, they need to interact with the appropriate ring to
determine its location in the cluster. determine its location in the cluster.
The Ring maintains this mapping using zones, devices, partitions, and replicas. The Ring maintains this mapping using zones, devices, partitions, and replicas.
Each partition in the ring is replicated, by default, 3 times accross the Each partition in the ring is replicated, by default, 3 times across the
cluster, and the locations for a partition are stored in the mapping maintained cluster, and the locations for a partition are stored in the mapping maintained
by the ring. The ring is also responsible for determining which devices are by the ring. The ring is also responsible for determining which devices are
used for handoff in failure scenarios. used for handoff in failure scenarios.

2
doc/source/overview_reaper.rst
View File

@ -28,7 +28,7 @@ delete times out, the container won't be able to be deleted later and therefore
the account won't be deleted either). The overall process continues even on a the account won't be deleted either). The overall process continues even on a
failure so that it doesn't get hung up reclaiming cluster space because of one failure so that it doesn't get hung up reclaiming cluster space because of one
troublesome spot. The account reaper will keep trying to delete an account troublesome spot. The account reaper will keep trying to delete an account
until it evetually becomes empty, at which point the database reclaim process until it eventually becomes empty, at which point the database reclaim process
within the db_replicator will eventually remove the database files. within the db_replicator will eventually remove the database files.
------- -------