directory /var/cache/swift /srv/node should be created.

For multiple node swift cluster setup, these directories should be
created in the setup steps. Otherwise, when start up storage servers
there will be errors. The error messages won't tell if it is because
of missing the directory.

Change-Id: I67d74abb7743b76739b5e747d6dcbd3214b00774
Fixes: bug #1158519
This commit is contained in:
tong li 2013-03-26 14:56:44 -04:00 committed by Gerrit Code Review
parent 2927dcc967
commit f1aefcbc13

View File

@ -96,6 +96,17 @@ General OS configuration and partitioning for each node
mkdir -p /var/run/swift
chown swift:swift /var/run/swift
#. Create directory /var/cache/swift and /srv/node. Change the ownership of the
directory /var/cache/swift to the user and group which Swift account, container
or object services will run under. These directories are needed only for storage
node (account, container or object server). The ownership of /srv/node should
be root:root, this is to ensure that when storage disks unmounted unexpectedly,
the objects for swift will not be created in the directory /srv/node. If you have
a node only runs proxy server, you can skip this step.::
mkdir -p /var/cache/swift /srv/node/
chown swift:swift /var/cache/swift
.. note::
The random string of text in /etc/swift/swift.conf is
used as a salt when hashing to determine mappings in the ring.
@ -237,14 +248,15 @@ Configure the Storage nodes
apt-get install swift-account swift-container swift-object xfsprogs
#. For every device on the node, setup the XFS volume (/dev/sdb is used
as an example)::
as an example), add mounting option inode64 when your disk is bigger than
1TB to archive a better performance.::
fdisk /dev/sdb (set up a single partition)
mkfs.xfs -i size=1024 /dev/sdb1
mkfs.xfs -i size=512 /dev/sdb1
echo "/dev/sdb1 /srv/node/sdb1 xfs noatime,nodiratime,nobarrier,logbufs=8 0 0" >> /etc/fstab
mkdir -p /srv/node/sdb1
mount /srv/node/sdb1
chown -R swift:swift /srv/node
chown swift:swift /srv/node/sdb1
#. Create /etc/rsyncd.conf::