Open Stack

We are glad to announce the release of:

python-monascaclient 1.1.0: Monasca API Client Library

This release is part of the newton release series.

With package available at:

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

For more details, please see below.

Changes in python-monascaclient 1.0.30..1.1.0
---------------------------------------------

7a9f7a0 Remove the debian folder
b62c096 Oslo.utils safe_decode
bb1ed7f Update copyright in monascaclient
4c103fd Adding keystoneauth sessions support
962f2de Graduate to oslo.utils strutils
b72eaa4 Graduate to using oslo.utils importutils
a6542c3 Graduate to oslo.serialization jsonutils
257b892 [python-monascaclient] Change tox to use https instead of git
c753513 Add period field to notification methods
d3a6bed code compatibility with py3
1c4d13c Constraint tox targets with upper-constraints.txt
887e1d5 Fix the homepage in setup.cfg
5758fe3 Add support for group_by to measurements and statistics resources
5a099c8 Manually sync with global-requirements
29f9d57 [Trivial] Remove executable privilege of setup.py
4568736 Add --tenant-id option for some commands
4790bd9 Specify match_by in alarm-definition-update help message
0dc4b03 Alarm def update/patch failed with empty param
731a38b Change tox file
d32548f Implement monasca metric-name-list
e288e8a Fix metric dimensions having only key
bfb5453 Allow sorting notifications
25deb49 remove python 2.6 trove classifier

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

README.rst                                       |  42 +++--
client_api_example.py                            |  10 +-
debian/changelog                                 |   6 -
debian/compat                                    |   1 -
debian/control                                   |  15 --
debian/copyright                                 |   4 -
debian/rules                                     |   4 -
monascaclient/__init__.py                        |  15 ++
monascaclient/common/http.py                     | 111 +++++++++--
monascaclient/common/monasca_manager.py          |   7 +-
monascaclient/common/utils.py                    |   8 +-
monascaclient/exc.py                             |   2 +-
monascaclient/ksclient.py                        | 112 +++++++-----
monascaclient/openstack/common/apiclient/base.py |   3 +-
monascaclient/openstack/common/importutils.py    |  67 -------
monascaclient/openstack/common/jsonutils.py      | 183 -------------------
monascaclient/openstack/common/strutils.py       | 223 -----------------------
monascaclient/openstack/common/timeutils.py      | 205 ---------------------
monascaclient/shell.py                           |  91 ++++-----
monascaclient/v2_0/__init__.py                   |   2 +-
monascaclient/v2_0/client.py                     |  24 ++-
monascaclient/v2_0/shell.py                      | 143 +++++++++++++--
openstack-common.conf                            |   2 +-
requirements.txt                                 |  36 ++--
setup.cfg                                        |   5 +-
setup.py                                         |  12 +-
test-requirements.txt                            |  23 ++-
tools/install_venv.py                            |   5 +-
tools/tox_install.sh                             |  57 ++++++
tox.ini                                          |   7 +-
32 files changed, 590 insertions(+), 940 deletions(-)


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

diff --git a/requirements.txt b/requirements.txt
index 9a0de05..a94c38d 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,8 +1,11 @@
-oslo.config
-oslo.concurrency
-oslo.i18n
-oslo.log
-oslo.middleware
-oslo.serialization
-oslo.service
-oslo.utils
+# 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.
+oslo.config>=3.9.0 # Apache-2.0
+oslo.concurrency>=3.5.0 # Apache-2.0
+oslo.i18n>=2.1.0 # Apache-2.0
+oslo.log>=1.14.0 # Apache-2.0
+oslo.middleware>=3.0.0 # Apache-2.0
+oslo.serialization>=1.10.0 # Apache-2.0
+oslo.service>=1.0.0 # Apache-2.0
+oslo.utils>=3.5.0 # Apache-2.0
@@ -10 +13 @@ oslo.utils
-python-keystoneclient
+keystoneauth1>=2.1.0 # Apache-2.0
@@ -12,8 +15,7 @@ python-keystoneclient
-argparse
-babel
-iso8601>=0.1.9
-pbr>=0.11
-PrettyTable>=0.7
-PyYAML>=3.1.0
-requests>=1.1
-six>=1.7.0
+Babel!=2.3.0,!=2.3.1,!=2.3.2,!=2.3.3,>=1.3 # BSD
+iso8601>=0.1.11 # MIT
+pbr>=1.6 # Apache-2.0
+PrettyTable<0.8,>=0.7 # BSD
+PyYAML>=3.1.0 # MIT
+requests!=2.9.0,>=2.8.1 # Apache-2.0
+six>=1.9.0 # MIT
diff --git a/test-requirements.txt b/test-requirements.txt
index b1aa55d..ddc9e71 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -1,10 +1,13 @@
-coverage>=3.6
-discover
-fixtures>=0.3.14
-hacking>=0.9.2,<0.10
-mock>=1.0
-mox3>=0.7.0
-sphinx>=1.1.2,<1.2
-testrepository>=0.0.18
-testscenarios>=0.4
-testtools>=0.9.34
+# 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.
+coverage>=3.6 # Apache-2.0
+discover # BSD
+fixtures<2.0,>=1.3.1 # Apache-2.0/BSD
+hacking<0.10,>=0.9.2
+mock>=1.2 # BSD
+mox3>=0.7.0 # Apache-2.0
+sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 # BSD
+testrepository>=0.0.18 # Apache-2.0/BSD
+testscenarios>=0.4 # Apache-2.0/BSD
+testtools>=1.4.0 # MIT