diff options
author | Peter Portante <peter.portante@redhat.com> | 2013-09-26 15:47:36 -0400 |
---|---|---|
committer | Peter Portante <peter.portante@redhat.com> | 2013-09-30 10:23:04 -0400 |
commit | e8a07c4ca784f958e33044c267212925d6452979 (patch) | |
tree | 1879b4f911e6c46480ff0242a4386b7a79c06a6a | |
parent | 5eea524d3ea6d29c2b6f34927c0130090e7ed44d (diff) | |
download | swift-e8a07c4ca784f958e33044c267212925d6452979.tar.gz |
Fedora 19 updates
Change-Id: I95138852e45aa7632218a7107e0e7ba1f6ef373c
Signed-off-by: Peter Portante <peter.portante@redhat.com>
-rw-r--r-- | doc/source/development_saio.rst | 51 |
1 files changed, 42 insertions, 9 deletions
diff --git a/doc/source/development_saio.rst b/doc/source/development_saio.rst index 092c46d7c..39af5d668 100644 --- a/doc/source/development_saio.rst +++ b/doc/source/development_saio.rst @@ -110,6 +110,8 @@ If you want to use a loopback device instead of another partition, follow these mkdir -p /var/run/swift chown <your-user-name>:<your-group-name> /var/run/swift + Note that on some systems you might have to create `/etc/rc.local`. + .. _rsync-section: ---------------- @@ -196,16 +198,30 @@ Setting up rsync read only = false lock file = /var/lock/object6040.lock - #. On Ubuntu, edit the following line in /etc/default/rsync:: + #. On Ubuntu, edit the following line in `/etc/default/rsync`:: RSYNC_ENABLE=true - On Fedora, edit the following line in /etc/xinetd.d/rsync:: + On Fedora, edit the following line in `/etc/xinetd.d/rsync`:: disable = no - #. On Ubuntu, run `service rsync restart`, on xinetd based systems - run `service xinetd restart`. + #. On platforms with SELinux in `Enforcing` mode, either set to `Permissive`:: + + setenforce Permissive + + Or just allow rsync full access:: + + setsebool -P rsync_full_access 1 + + #. On Ubuntu, run `service rsync restart` + + On Fedora, run:: + + systemctl enable rsyncd.service + systemctl start rsyncd.service + + On other xinetd based systems run `service xinetd restart`. #. Verify rsync is accepting connections for all servers:: @@ -266,10 +282,18 @@ Optional: Setting up rsyslog for individual logging $PrivDropToGroup adm #. `mkdir -p /var/log/swift/hourly` + + #. On Ubuntu: + #. `chown -R syslog.adm /var/log/swift` #. `chmod -R g+w /var/log/swift` #. `service rsyslog restart` + #. On Fedora: + #. `chown -R root:adm /var/log/swift` + #. `chmod -R g+w /var/log/swift` + #. `systemctl restart rsyslog.service` + ---------------- Getting the code ---------------- @@ -287,13 +311,18 @@ You can do the following commands as administrator user. #. Install swift's test dependencies `sudo pip install -r swift/test-requirements.txt` -Do the following commands as root, but verify that Swift has access -to resulting configuration files. +Fedora 19 or later users might have to perform the following if development +installation of swift fails:: + + pip install -U xattr dnspython --------------------- Configuring each node --------------------- +Do the following commands as root, but verify that Swift has access +to resulting configuration files. + Sample configuration files are provided with all defaults in line-by-line comments. #. Create `/etc/swift/proxy-server.conf`:: @@ -704,11 +733,15 @@ Setting up scripts for running Swift #. `mkdir ~/bin` - #. Create `~/bin/resetswift.` + #. Create `~/bin/resetswift`. + + If you are using a loopback device substitute `/dev/sdb1` with + `/srv/swift-disk` in the `mkfs` step. - If you are using a loopback device substitute `/dev/sdb1` with `/srv/swift-disk`. + If you did not set up rsyslog for individual logging, remove the `find + /var/log/swift...` line. - If you did not set up rsyslog for individual logging, remove the `find /var/log/swift...` line:: + On Fedora, replace `service `<name>` restart` with `systemctl restart `<name>`.service`:: #!/bin/bash |