Open Stack

We are tickled pink to announce the release of:

python-tackerclient 0.2.1: CLI and Client Library for OpenStack Tacker

This release is part of the liberty stable release series.

With package available at:

    https://pypi.python.org/pypi/python-tackerclient

For more details, please see below.

Changes in python-tackerclient 0.2.0..0.2.1
-------------------------------------------

7b93e46 Add default branch to stable/liberty
ec0629c Clean up references to neutron
9399c8d Fix summary and author in setup.cfg
16c31a2 Deprecating "device" API and CLI in stable/liberty branch
fd38742 update requirements according to global requ
13ab0b9 Remove service instance related stuff and fix unittests

Diffstat (except docs and test files)
-------------------------------------

.gitreview                                         |   1 +
.testr.conf                                        |   2 +-
HACKING.rst                                        |   2 +-
requirements.txt                                   |  17 ++-
setup.cfg                                          |   4 +-
setup.py                                           |   3 +-
tackerclient/common/constants.py                   |   3 +-
tackerclient/common/utils.py                       |  15 ++
tackerclient/tacker/v1_0/vm/device.py              |  29 +---
tackerclient/tacker/v1_0/vm/device_template.py     |   6 +
tackerclient/v1_0/client.py                        |  10 ++
test-requirements.txt                              |  15 +-
tox.ini                                            |   8 +-
19 files changed, 93 insertions(+), 292 deletions(-)


Requirements updates
--------------------

diff --git a/requirements.txt b/requirements.txt
index c09cd7b..c70aea0 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1 +1,4 @@
-pbr>=0.6,!=0.7,<1.0
+# 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.
+pbr>=1.6
@@ -3 +6 @@ argparse
-cliff>=1.4.3
+cliff>=1.14.0 # Apache-2.0
@@ -5,5 +8,5 @@ iso8601>=0.1.9
-netaddr>=0.7.6
-requests>=1.1
-python-keystoneclient>=0.9.0
-simplejson>=2.0.9
-six>=1.6.0
+netaddr>=0.7.12,!=0.7.16
+requests>=2.5.2,!=2.8.0,!=2.9.0
+python-keystoneclient>=1.6.0,!=1.8.0
+simplejson>=2.2.0
+six>=1.9.0
diff --git a/test-requirements.txt b/test-requirements.txt
index 402590b..7bf0a86 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -1,2 +1,4 @@
-hacking>=0.8.0,<0.9
-
+# 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.10.2,<0.11
@@ -6 +8 @@ discover
-fixtures>=0.3.14
+fixtures>=1.3.1
@@ -7,0 +10,3 @@ mox>=0.5.3
+flake8>=2.2.4,<=2.4.1
+pep8==1.5.7
+pyflakes==0.8.1
@@ -9 +14 @@ python-subunit>=0.0.18
-sphinx>=1.1.2,<1.2
+sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
@@ -11 +16 @@ testrepository>=0.0.18
-testtools>=0.9.34
+testtools>=1.4.0