path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* Automate functional testsLuis Pabon2013-07-031-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By storing the functional tests configuration files in the repo, we can now run the 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/ Change-Id: Icdbcd420355b02e64f294df7298a3e473b343655 Signed-off-by: Luis Pabon <> Reviewed-on: Reviewed-by: Peter Portante <>
* Add DiskDir unit test skeleton and pep8 filterPeter Portante2013-05-241-0/+5
| | | | | | | | | | | | | | | | | The new DiskDir unit test skeleton is quite incomplete, but gets the DiskDir module on the board for modules covered, explicitly exposing the fact that we need to get test coverage. This is a first step. At the same time, we also update all the modules we have applying the fix for pep8 errors now run under tox. We can then add a Jenkins pre-commit job to fail on pep8 errors. This brings our code to parity with what they are doing in OpenStack Swift. Change-Id: Ia0565606512efda6e73f67bd00269177b89db858 Signed-off-by: Peter Portante <> Reviewed-on: Reviewed-by: Luis Pabon <> Tested-by: Luis Pabon <>
* Remove "ufo" directory, promoting contents to top-levelPeter Portante2013-05-101-0/+6
Additionally, we drop the "ufo" references from, spec file and README, and add the HISTORY file describing how the repo was initially created. We also update the RPM spec file to use the name "gluster-for-swift" to avoid colliding with existing RPM names from RHS 2.0 (the spec file's description was also updated, along with the version number). Change-Id: If804224a94208d57896e4189c63736ffc9e01d5e Signed-off-by: Peter Portante <> Reviewed-on: Reviewed-by: Luis Pabon <> Reviewed-by: Mohammed Junaid <> Reviewed-by: Kaleb KEITHLEY <> Reviewed-by: Peter Portante <> Tested-by: Peter Portante <>