From 7439918490cdc697b7f2804ef84319b6e77327e7 Mon Sep 17 00:00:00 2001 From: Saravanakumar Arumugam Date: Tue, 28 Feb 2017 11:21:00 +0530 Subject: Adding gluster-object to gluster docker hub. Current changes are for CentOS. Refer docker-gluster-swift/README.md for setting up gluster-object Docker container. Signed-off-by: Saravanakumar Arumugam --- .../etc/swift/object-server.conf | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 gluster-object/CentOS/docker-gluster-swift/etc/swift/object-server.conf (limited to 'gluster-object/CentOS/docker-gluster-swift/etc/swift/object-server.conf') diff --git a/gluster-object/CentOS/docker-gluster-swift/etc/swift/object-server.conf b/gluster-object/CentOS/docker-gluster-swift/etc/swift/object-server.conf new file mode 100644 index 0000000..2c7df2e --- /dev/null +++ b/gluster-object/CentOS/docker-gluster-swift/etc/swift/object-server.conf @@ -0,0 +1,55 @@ +[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 object-server workers start, +# you can *consider* setting this value to "false" to reduce the per-request +# overhead it can incur. +mount_check = false +bind_port = 6010 +# +# Maximum number of clients one worker can process simultaneously (it will +# actually accept N + 1). Setting this to one (1) will only handle one request +# at a time, without accepting another request concurrently. By increasing the +# number of workers to a much higher value, one can prevent slow file system +# operations for one request from starving other requests. +max_clients = 1024 +# +# If not doing the above, setting this value initially to match the number of +# CPUs is a good starting point for determining the right value. +workers = 1 +# Override swift's default behaviour for fallocate. +disable_fallocate = true + +[pipeline:main] +pipeline = object-server + +[app:object-server] +use = egg:gluster_swift#object +user = root +log_facility = LOG_LOCAL2 +log_level = WARN +# The following parameters are used by object-expirer and needs to be same +# across all conf files! +auto_create_account_prefix = gs +expiring_objects_account_name = expiring +# +# For performance, after ensuring things are running in a stable manner, you +# can turn off normal request logging for the object server to reduce the +# per-request overhead and unclutter the log files. Warnings and errors will +# still be logged. +log_requests = off +# +# Adjust this value to match the stripe width of the underlying storage array +# (not the stripe element size). This will provide a reasonable starting point +# for tuning this value. +disk_chunk_size = 65536 +# +# Adjust this value match whatever is set for the disk_chunk_size initially. +# This will provide a reasonable starting point for tuning this value. +network_chunk_size = 65536 -- cgit v1.2.3