2505d82815
This provides an infrastructure for swiftkerbauth related functional test cases. More test cases will be added later. Added a section in swiftkerbauth guide about how to run functional tests. test/functional_auth/swiftkerbauth ---------------------------------- A new authentication filter related functional tests and configuration to reside here. The configuration would help setup the environment. All the generic functional tests should run fine with PASSIVE mode of swiftkerbatuh. Please refere to swiftkerbatuh documentation for ACTIVE/PASSIVE mode of working. swiftkerbauth/test_swkrbath_active.py ------------------------------------- This file has all the testcases of active mode of swiftkerbauth. More test cases to be added later. SwiftKerbAuth related test cases are meant to run on the setup where SwiftKerbAuth is setup and installed. Change-Id: Ibc2a3945f5c9b6714475fcec0ee9d153debb48e3 Signed-off-by: Chetan Risbud <crisbud@redhat.com> Reviewed-on: http://review.gluster.org/6925 Reviewed-by: Luis Pabon <lpabon@redhat.com> Tested-by: Luis Pabon <lpabon@redhat.com>
52 lines
2.0 KiB
Plaintext
52 lines
2.0 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 object-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 = 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
|
|
#
|
|
# 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
|