ebddcb6d8f
The difference between these tests and those under the functional directory, is that these tests do not run under tox, and so require a full OpenStack Swift + swiftonfile deployment. The conf files where copies of the gswauth test, but I modified them to be able to do a mount check. The purpose of this tests is to confirm the quality of the software in a deployed system. The tests require the following: - GlusterFS Volumes: test, test2, gsmetadata - Directory /mnt/gluster-object - OpenStack Swift + swiftonfile to be installed. Signed-off-by: Luis Pabon <lpabon@redhat.com>
33 lines
920 B
Plaintext
33 lines
920 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 account-server workers start,
|
|
# you can *consider* setting this value to "false" to reduce the per-request
|
|
# overhead it can incur.
|
|
#
|
|
# *** Keep false for Functional Tests ***
|
|
mount_check = true
|
|
bind_port = 6012
|
|
#
|
|
# 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 = account-server
|
|
|
|
[app:account-server]
|
|
use = egg:gluster_swift#account
|
|
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 account server to unclutter the log
|
|
# files. Warnings and errors will still be logged.
|
|
log_requests = off
|