summaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-devtools/python/python-swift/cluster.conf
diff options
context:
space:
mode:
authorVu Tran <vu.tran@windriver.com>2014-04-09 19:59:09 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2014-04-11 14:15:28 -0400
commit322d51de8417142c6ffbf024b198b26069a53f46 (patch)
tree7dc20eedcd969ecff64b57061a5263387fe1b424 /meta-openstack/recipes-devtools/python/python-swift/cluster.conf
parentc173214e9c25409944144c9b4bd9892949a834ba (diff)
downloadmeta-cloud-services-322d51de8417142c6ffbf024b198b26069a53f46.tar.gz
swift: add setup package
Introduce swift setup package. At boot time, this package setups a simple swift cluster including: * 3 zones * each zone has 1 storage device which are based on loopback devices which the backing files size is controlled by variable SWIFT_BACKING_FILE_SIZE The script /etc/swift/swift_setup.sh is also provided to ease the task of setting up a complicated Swift cluster. It reads a cluster config file, which describes what storage devices are included in what rings, and constructs the cluster. For details of how to use swift_setup.sh and the format of Swift cluster config file please refer to the script's help: $ swift_setup.sh Signed-off-by: Vu Tran <vu.tran@windriver.com>
Diffstat (limited to 'meta-openstack/recipes-devtools/python/python-swift/cluster.conf')
-rw-r--r--meta-openstack/recipes-devtools/python/python-swift/cluster.conf32
1 files changed, 32 insertions, 0 deletions
diff --git a/meta-openstack/recipes-devtools/python/python-swift/cluster.conf b/meta-openstack/recipes-devtools/python/python-swift/cluster.conf
new file mode 100644
index 0000000..3cab8bd
--- /dev/null
+++ b/meta-openstack/recipes-devtools/python/python-swift/cluster.conf
@@ -0,0 +1,32 @@
1# Swift cluster config file
2#
3# Each line specifies one storage device with the following format:
4#
5# <dev file>, <dev format>, <zone>, <ring names>, <weight>
6#
7# <dev file>: full path to a block device or full path to regular
8# file which is used for backing up a loopback device.
9# If <dev file> is empty string then this device is
10# backed up by a directory in local filesystem.
11# <dev format>: the disk format type, e.g. ext4, xfs...
12# <zone>: the zone id which this block device belongs to
13# <ring names>: a list (separated by space) ring name ("account", "container",
14# or "object") which this device is added to
15# <weight>: weight of this device in Swift zone
16#
17# Examples:
18#
19# /dev/sda1, ext4, 1, account, 1
20# /dev/sda2, ext4, 1, container, 1
21# /dev/sda3, ext4, 1, object, 1
22# /dev/sdb1, ext4, 2, account container object, 1
23# /dev/sdb2, ext4, 2, account container object, 1
24# /dev/sdb3, ext4, 2, account container object, 1
25# , ext4, 1, account container object, 1
26# , ext4, 2, account container object, 1
27# , ext4, 3, account container object, 1
28
29
30%SWIFT_BACKING_FILE_1%, ext4, 1, account container object, 1
31%SWIFT_BACKING_FILE_2%, ext4, 2, account container object, 1
32%SWIFT_BACKING_FILE_3%, ext4, 3, account container object, 1