From a6ccc44f893038d12d62a0409849b78ed188d5a6 Mon Sep 17 00:00:00 2001 From: Anne Gentle Date: Thu, 28 Oct 2010 17:01:50 -0500 Subject: [PATCH] Updated SAIO to point to RHEL instructions on wiki --- doc/source/development_saio.rst | 3 +++ doc/source/getting_started.rst | 3 +-- doc/source/index.rst | 2 +- doc/source/ratelimit.rst | 2 +- 4 files changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/source/development_saio.rst b/doc/source/development_saio.rst index 605081e015..3b031bf6b9 100644 --- a/doc/source/development_saio.rst +++ b/doc/source/development_saio.rst @@ -17,6 +17,9 @@ virtual machine will emulate running a four node Swift cluster. * Create guest virtual machine from the Ubuntu image. +Additional information about setting up a Swift development snapshot on Fedora, CentOS, or RHEL (Red Hat Enterprise Linux) is available on +the wiki at http://wiki.openstack.org/RhelInstructions. + ----------------------------------------- Installing dependencies and the core code ----------------------------------------- diff --git a/doc/source/getting_started.rst b/doc/source/getting_started.rst index 4ce0d934c0..7c7bfc4c16 100644 --- a/doc/source/getting_started.rst +++ b/doc/source/getting_started.rst @@ -37,5 +37,4 @@ Production ---------- We do not have documentation yet on how to set up and configure Swift for a -production cluster, but hope to begin work on those soon. - +production cluster, but hope to begin work on those soon. \ No newline at end of file diff --git a/doc/source/index.rst b/doc/source/index.rst index 66f4d1cc7a..7ebd61ff10 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -40,7 +40,7 @@ Deployment: .. toctree:: :maxdepth: 1 - + deployment_guide admin_guide debian_package_guide diff --git a/doc/source/ratelimit.rst b/doc/source/ratelimit.rst index 37785a9565..80db870773 100644 --- a/doc/source/ratelimit.rst +++ b/doc/source/ratelimit.rst @@ -4,7 +4,7 @@ Rate Limiting Rate limiting in swift is implemented as a pluggable middleware. Rate limiting is performed on requests that result in database writes to the -account and container sqlite dbs. It uses memcached and is dependant on +account and container sqlite dbs. It uses memcached and is dependent on the proxy servers having highly synchronized time. The rate limits are limited by the accuracy of the proxy server clocks.