We are glad to announce the release of: tricircleclient 0.1.1: Python client library for Tricircle This is the first release of tricircleclient. This release is part of the pike release series. The source is available from: http://git.openstack.org/cgit/openstack/python-tricircleclient Download the package from: https://tarballs.openstack.org/python-tricircleclient/ Please report issues through launchpad: http://bugs.launchpad.net/python-tricircleclient For more details, please see below. Changes in tricircleclient 2dfca6255186b6604781a32424932d4308348f26..0.1.1 -------------------------------------------------------------------------- 0ad3c60 Replace six.iteritems() with .items() d65488d Unit Test to delete pod c948f44 Drop py34 target in setup.cfg 8d4d607 Updated from global requirements 4d1769a Unit Test to list pods e5c280c Unit Test to show pod details f1f64e7 Remove log translations 4bebbc9 Fix bug while creating a pod 4eead1c Updated from global requirements 14b5424 Fix gate-python-tricircleclient-requirements f151f8b Add a threashold for coverage code 833564c Fix all tox execution c41dce2 Add routing resouces CLI commands 6fed050 Cosmetic changes for Pods CLI e9cc28d Complete create and list methods for pod management 205d7b6 Add handle exception process Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index 0972287..6e37ac4 100644 --- a/requirements.txt +++ b/requirements.txt @@ -5,8 +5,9 @@ -pbr<2.0,>=1.4 -cliff>1.16.0 # Apache-2.0 -osc-lib>=0.3.0 # Apache-2.0 -oslo.serialization>=1.4.0 # Apache-2.0 -oslo.utils>=2.0.0 # Apache-2.0 -keystoneauth1>=1.0.0 -six -futurist +pbr>=2.0.0 # Apache-2.0 +cliff>=2.3.0 # Apache-2.0 +osc-lib>=1.2.0 # Apache-2.0 +oslo.log>=3.22.0 # Apache-2.0 +oslo.serialization>=1.10.0 # Apache-2.0 +oslo.utils>=3.20.0 # Apache-2.0 +keystoneauth1>=2.18.0 # Apache-2.0 +six>=1.9.0 # MIT +futurist!=0.15.0,>=0.11.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt new file mode 100644 index 0000000..3f19d11 --- /dev/null +++ b/test-requirements.txt @@ -0,0 +1,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. + +fixtures>=3.0.0 # Apache-2.0/BSD +coverage>=4.0 # Apache-2.0 +mock>=2.0 # BSD +testrepository>=0.0.18 # Apache-2.0/BSD +testtools>=1.4.0 # MIT