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>
86 lines
2.5 KiB
Plaintext
86 lines
2.5 KiB
Plaintext
[DEFAULT]
|
|
|
|
|
|
[swift-hash]
|
|
# random unique string that can never change (DO NOT LOSE)
|
|
swift_hash_path_suffix = gluster
|
|
|
|
|
|
# The swift-constraints section sets the basic constraints on data
|
|
# saved in the swift cluster.
|
|
|
|
[swift-constraints]
|
|
|
|
# max_file_size is the largest "normal" object that can be saved in
|
|
# the cluster. This is also the limit on the size of each segment of
|
|
# a "large" object when using the large object manifest support.
|
|
# This value is set in bytes. Setting it to lower than 1MiB will cause
|
|
# some tests to fail.
|
|
# Default is 1 TiB = 2**30*1024
|
|
max_file_size = 1099511627776
|
|
|
|
|
|
# max_meta_name_length is the max number of bytes in the utf8 encoding
|
|
# of the name portion of a metadata header.
|
|
|
|
#max_meta_name_length = 128
|
|
|
|
|
|
# max_meta_value_length is the max number of bytes in the utf8 encoding
|
|
# of a metadata value
|
|
|
|
#max_meta_value_length = 256
|
|
|
|
|
|
# max_meta_count is the max number of metadata keys that can be stored
|
|
# on a single account, container, or object
|
|
|
|
#max_meta_count = 90
|
|
|
|
|
|
# max_meta_overall_size is the max number of bytes in the utf8 encoding
|
|
# of the metadata (keys + values)
|
|
|
|
#max_meta_overall_size = 4096
|
|
|
|
|
|
# max_object_name_length is the max number of bytes in the utf8 encoding of an
|
|
# object name: Gluster FS can handle much longer file names, but the length
|
|
# between the slashes of the URL is handled below. Remember that most web
|
|
# clients can't handle anything greater than 2048, and those that do are
|
|
# rather clumsy.
|
|
|
|
max_object_name_length = 2048
|
|
|
|
# max_object_name_component_length (GlusterFS) is the max number of bytes in
|
|
# the utf8 encoding of an object name component (the part between the
|
|
# slashes); this is a limit imposed by the underlying file system (for XFS it
|
|
# is 255 bytes).
|
|
|
|
max_object_name_component_length = 255
|
|
|
|
# container_listing_limit is the default (and max) number of items
|
|
# returned for a container listing request
|
|
|
|
#container_listing_limit = 10000
|
|
|
|
|
|
# account_listing_limit is the default (and max) number of items returned
|
|
# for an account listing request
|
|
|
|
#account_listing_limit = 10000
|
|
|
|
|
|
# max_account_name_length is the max number of bytes in the utf8 encoding of
|
|
# an account name: Gluster FS Filename limit (XFS limit?), must be the same
|
|
# size as max_object_name_component_length above.
|
|
|
|
max_account_name_length = 255
|
|
|
|
|
|
# max_container_name_length is the max number of bytes in the utf8 encoding
|
|
# of a container name: Gluster FS Filename limit (XFS limit?), must be the same
|
|
# size as max_object_name_component_length above.
|
|
|
|
max_container_name_length = 255
|