cc0777f091
Change-Id: I4f63bf4d1a8eb62fed5a9cc9b43f54de0127d3e4 Signed-off-by: Luis Pabon <lpabon@redhat.com> Reviewed-on: http://review.gluster.org/5445 Tested-by: Peter Portante <pportant@redhat.com> Reviewed-by: Peter Portante <pportant@redhat.com> Reviewed-on: http://review.gluster.org/5507
32 lines
887 B
Plaintext
32 lines
887 B
Plaintext
[DEFAULT]
|
|
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
|
|
|