
The following piece of documentaion is added to account,container,object.cong-gluster file "default gluster mount point to be used for object store,can be changed by setting the following value in {account,container,object}-server.conf files." BUG:https://bugs.launchpad.net/gluster-swift/+bug/1267718 Change-Id: I7993336b75637034f2cdaf3b41f0960220f7b390 Signed-off-by: Pushpesh Sharma <psharma@redhat.com> Reviewed-on: http://review.gluster.org/6680 Reviewed-by: Chetan Risbud <crisbud@redhat.com> Tested-by: Chetan Risbud <crisbud@redhat.com> Reviewed-by: Luis Pabon <lpabon@redhat.com> Tested-by: Luis Pabon <lpabon@redhat.com>
37 lines
1.1 KiB
Plaintext
37 lines
1.1 KiB
Plaintext
[DEFAULT]
|
|
#
|
|
# Default gluster mount point to be used for object store,can be changed by
|
|
# setting the following value in {account,container,object}-server.conf files.
|
|
# It is recommended to keep this value same for all the three services but can
|
|
# be kept different if environment demands.
|
|
devices = /mnt/gluster-object
|
|
#
|
|
# Once you are confident that your startup processes will always have your
|
|
# gluster volumes properly mounted *before* the container-server workers
|
|
# start, you can *consider* setting this value to "false" to reduce the
|
|
# per-request overhead it can incur.
|
|
mount_check = true
|
|
bind_port = 6011
|
|
#
|
|
# Override swift's default behaviour for fallocate.
|
|
disable_fallocate = true
|
|
#
|
|
# One or two workers should be sufficient for almost any installation of
|
|
# Gluster.
|
|
workers = 1
|
|
|
|
[pipeline:main]
|
|
pipeline = container-server
|
|
|
|
[app:container-server]
|
|
use = egg:gluster_swift#container
|
|
user = root
|
|
log_facility = LOG_LOCAL2
|
|
log_level = WARN
|
|
#
|
|
# After ensuring things are running in a stable manner, you can turn off
|
|
# normal request logging for the container server to unclutter the log
|
|
# files. Warnings and errors will still be logged.
|
|
log_requests = off
|
|
|