openstack/swift
Code Issues Proposed changes

Edits based on input

Browse Source
This commit is contained in:
Anne Gentle 2010-11-24 10:55:29 -06:00
parent a342d6a9a4
commit 05658b8f8f
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/source/howto_installmultinode.rst
View File

@ -48,7 +48,7 @@ that is as isolated as possible from other nodes (separate servers, network,
power, even geography). The ring guarantees that every replica is stored
in a separate zone. For more information about the ring and zones, see: :doc:`The Rings <overview_ring>`.
As your object store grows you may need to add additional Proxy servers for performance which is described in :ref:`add-proxy-server`.
To increase reliability, you may want to add additional Proxy servers for performance which is described in :ref:`add-proxy-server`.
Network Setup Notes
-------------------
@ -391,11 +391,11 @@ You run these commands from the Auth node.
Adding a Proxy Server
---------------------
Once you see a need for additional proxy servers, you can set up the proxy node in the same manner that you set up the first proxy node but with additional configuration steps.
For reliability's sake you may want to have more than one proxy server. You can set up the additional proxy node in the same manner that you set up the first proxy node but with additional configuration steps.
Once you have more than two proxies, you also want to load balance between the two, which means your storage endpoint also changes. You can select from different strategies for load balancing. For example, you could use round robin dns, or an actual load balancer (like pound) in front of the two proxies, and point your storage url to the load balancer.
See :ref:`config-proxy` for the initial setup, then follow these additional steps.
See :ref:`config-proxy` for the initial setup, and then follow these additional steps.
#. Update the list of memcache servers in /etc/swift/proxy-server.conf for all the added proxy servers. If you run multiple memcache servers, use this pattern for the multiple IP:port listings: `10.1.2.3:11211,10.1.2.4:11211` in each proxy server's conf file.::
@ -407,11 +407,13 @@ See :ref:`config-proxy` for the initial setup, then follow these additional step
[app:auth-server]
use = egg:swift#auth
default_cluster_url = https://<LOAD_BALANCER_HOSTNAME>:8080/v1
default_cluster_url = https://<LOAD_BALANCER_HOSTNAME>/v1
# Highly recommended to change this key to something else!
super_admin_key = devauth
#. Next, copy all the ring information to all the nodes, proxy and storage nodes. You can write a script to use scp to copy all the rings to all the nodes, set up cron jobs on the nodes that rsynch the rings from a set location, or set up a simple web server that serves the rings so that you can do a wget on the storage nodes to pull new rings.
#. After you change the default_cluster_url setting, you have to delete the auth database and recreate the Swift users, or manually update the auth database with the correct URL for each account.
#. Next, copy all the ring information to all the nodes, including your new proxy nodes, and ensure the ring info gets to all the storage nodes as well.
#. After you sync all the nodes, make sure the admin has the keys in /etc/swift and the ownership for the ring file is correct.