rename docker-gluster-swift as docker-gluster-s3 and the top

level directory gluster-object as gluster-s3object

Update README and test scripts to reflect name change.

Signed-off-by: Saravanakumar <sarumuga@redhat.com>

1 files changed, 0 insertions, 61 deletions

diff --git a/gluster-object/CentOS/docker-gluster-swift/etc/swift/object-expirer.conf b/gluster-object/CentOS/docker-gluster-swift/etc/swift/object-expirer.conf
deleted file mode 100644
index 8be8626..0000000
--- a/gluster-object/CentOS/docker-gluster-swift/etc/swift/object-expirer.conf
+++ /dev/null
@@ -1,61 +0,0 @@
-[DEFAULT]
-user = root
-# 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.
-devices = /mnt/gluster-object
-
-[object-expirer]
-user = root
-log_facility = LOG_LOCAL2
-log_level = INFO
-
-# 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
-
-# The expirer will re-attempt expiring if the source object is not available
-# up to reclaim_age seconds before it gives up and deletes the entry in the
-# queue. In gluster-swift, you'd almost always want to set this to zero.
-reclaim_age = 0
-
-# Do not retry DELETEs on getting 404. Hence default is set to 1.
-request_tries = 1
-
-# The swift-object-expirer daemon will run every 'interval' number of seconds
-# interval = 300
-
-# Emit a log line report of the progress so far every 'report_interval'
-# number of seconds.
-# report_interval = 300
-
-# concurrency is the level of concurrency to use to do the work, this value
-# must be set to at least 1
-# concurrency = 1
-
-# processes is how many parts to divide the work into, one part per process
-# that will be doing the work
-# processes set 0 means that a single process will be doing all the work
-# processes can also be specified on the command line and will override the
-# config value
-# processes = 0
-
-# process is which of the parts a particular process will work on
-# process can also be specified on the command line and will overide the config
-# value
-# process is "zero based", if you want to use 3 processes, you should run
-# processes with process set to 0, 1, and 2
-# process = 0
-
-
-[pipeline:main]
-pipeline = catch_errors cache proxy-server
-
-[app:proxy-server]
-use = egg:gluster_swift#proxy
-
-[filter:cache]
-use = egg:swift#memcache
-
-[filter:catch_errors]
-use = egg:swift#catch_errors