Update from global requirements

Change-Id: Idb108f9253ccb4f7eeece234b027339e44779275

requirements.txt

@@ -4,13 +4,13 @@
 pbr>=0.6,!=0.7,<1.0
 anyjson>=0.3.3
 Babel>=1.3
-eventlet>=0.15.1
+eventlet>=0.16.1,!=0.17.0
 iso8601>=0.1.9
 kombu>=2.5.0
-oslo.config>=1.4.0  # Apache-2.0
+oslo.config>=1.9.3,<1.10.0  # Apache-2.0
 PyYAML>=3.1.0
-six>=1.7.0
-stevedore>=1.0.0  # Apache-2.0
+six>=1.9.0
+stevedore>=1.3.0,<1.4.0  # Apache-2.0
 semantic_version>=2.3.1
 
 # not listed in global requirements

setup.py

@@ -17,6 +17,14 @@
 # THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT
 import setuptools
 
+# In python < 2.7.4, a lazy loading of package `pbr` will break
+# setuptools if some other modules registered functions in `atexit`.
+# solution from: http://bugs.python.org/issue15881#msg170215
+try:
+    import multiprocessing  # noqa
+except ImportError:
+    pass
+
 setuptools.setup(
     setup_requires=['pbr'],
     pbr=True)

test-requirements.txt

@@ -1,8 +1,11 @@
+# The order of packages is significant, because pip processes them in the order
+# of appearance. Changing the order has an impact on the overall integration
+# process, which may cause wedges in the gate later.
 hacking>=0.8.0,<0.9
 unittest2
 coverage>=3.6
 discover
 mock>=1.0
-sphinx>=1.1.2
-testtools>=0.9.32
+sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
+testtools>=0.9.36,!=1.2.0
 testrepository>=0.0.18