c52b889657
By storing the functional tests configuration files in the repo, we can now run the functional_tests.sh to setup, run the functional tests, and teardown. Most likely this will be able to be run as a user from the same directory as the repo, but at the moment, the configuration files are copied to /etc/swift. The only requirements are: 1. /etc/swift does not exist. That way the tests will not interfere with an existing deployment. 2. /mnt/gluster-object/test and /mnt/gluster-object/test2 must have been created and setup correctly on an XFS or GlusterFS volume 3. sudo rights without password prompt 4. glusterfs-openstack-swift-* rpm must not be installed on the system Once the requirements are met, you can execute the tests as follows: $ bash tools/functional_tests.sh Change-Id: Icdbcd420355b02e64f294df7298a3e473b343655 Signed-off-by: Luis Pabon <lpabon@redhat.com> Reviewed-on: http://review.gluster.org/5281 Reviewed-by: Peter Portante <pportant@redhat.com>
20 lines
290 B
Plaintext
20 lines
290 B
Plaintext
[DEFAULT]
|
|
devices = /mnt/gluster-object
|
|
mount_check = false
|
|
bind_port = 6012
|
|
user = root
|
|
log_facility = LOG_LOCAL2
|
|
|
|
[pipeline:main]
|
|
pipeline = account-server
|
|
|
|
[app:account-server]
|
|
use = egg:gluster_swift#account
|
|
|
|
[account-replicator]
|
|
vm_test_mode = yes
|
|
|
|
[account-auditor]
|
|
|
|
[account-reaper]
|