openstack/kolla
Code Issues Proposed changes

Remove some outdated info from swift-guide

Browse Source 
Change-Id: Ib74e69ee7c5755ccae4e2ecb7b976f110bdae7c1
backport: liberty
This commit is contained in:
Paul Bourke 2015-10-13 12:03:25 +00:00
parent ba3b1bcf90
commit 684db305df
1 changed files with 3 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/swift-guide.rst
View File

@ -3,22 +3,13 @@ Swift in Kolla
Overview Overview
-------- --------
Currently Kolla can deploy the "core" services required for a working Swift, in either an AIO or Kolla can deploy a full working Swift setup in either a AIO or multi node setup.
multi node setup:
- swift-proxy
- swift-account
- swift-container
- swift-object
There are a variety of other services such the replicator, expirer, rsyncd, etc. which actually make
Swift useful, which are in progress and hope to be finished in liberty-rc1.
Prerequisites Prerequisites
------------- -------------
Before running Swift we need to generate "rings", which are binary compressed files that at a high Before running Swift we need to generate "rings", which are binary compressed files that at a high
level let the various Swift services know where data is in the cluster. Again, we hope to be able to level let the various Swift services know where data is in the cluster. We hope to automate this
generate these automatically for liberty-rc1. process in a future release.
Swift also expects block devices to be available and partitioned on the host, which Swift uses in Swift also expects block devices to be available and partitioned on the host, which Swift uses in
combination with the rings to store data. Swift demos commonly just use directories created under combination with the rings to store data. Swift demos commonly just use directories created under