swift/swift/container
Peter Portante 07fcf50c3a Rework use of constraints to ease testing
Prior to this patch both mainline code and testing modules imported
and used constraints directly into their own namespace, or relied on
the namespace of other modules that were not the constraints
module. This meant that if a unit test wanted to change a constraint
for its operation, it had to know how that module was using the
constraint, instead of referencing the constraint module itself.

This patch unifies the use of constraints so that all constraints are
referenced via the constraints module. In turn, this allows a test to
leverage the re-loadable nature of the constraints in the constraints
module.

It addition, a number of functional tests where using the default
values for constraints, instead of the configured value discovered in
a test.conf or in an existing swift.conf. This patch removes those
direct references in favor of the load_constraint() method from the
test/functional/tests.py module.

Change-Id: Ia5313d653c667dd9ca800786de59b59334c34eaa
2014-04-02 23:48:01 -04:00
..
__init__.py Initial commit of Swift code 2010-07-12 17:03:45 -05:00
auditor.py Relocate DATADIR to backends 2014-04-01 23:22:22 -06:00
backend.py Relocate DATADIR to backends 2014-04-01 23:22:22 -06:00
replicator.py Relocate DATADIR to backends 2014-04-01 23:22:22 -06:00
server.py Rework use of constraints to ease testing 2014-04-02 23:48:01 -04:00
sync.py Relocate DATADIR to backends 2014-04-01 23:22:22 -06:00
updater.py Relocate DATADIR to backends 2014-04-01 23:22:22 -06:00