Pyparsing library was recently updated in golab requiremnts [1].
Since version 3.0.0 operatorPrecedence method was renamed to infixNotation [2].
[1]62f92c0187
[2]16b766b97c/CHANGES (L598)
Change-Id: I3bfefe5b9bc601f383e0b9d80046de387e420fd8
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: Ibfb162f88cb04c0b2af3fbf41cfcd96bc7e351be
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
-Bump the lower constraints for required deps which added python3.8 support
in their later version.
-Changing the way to install and configure Zookeeper.
Installing Zookeeper from official Apache's tarball.
Adding the possiblity to set the specific Zookeeper version.
Minor change in zookeeper logger.
-Use mariadb JDBC for monasca-thresh in devstack, since Drizzle isn't
compatible with MySql Server v8.0.x which is default in Focal
-Python 3.8 doesn't seem to like dictionary keys changing during
iteration.
Fixing RuntimeError: dictionary keys changed during iteration.
Tech. details:
It runs well in py27: 5 iterations
It runs risky in py37: 7 iterations
It is forbbiden in py38: raised RuntimeError
Fixed with list(dic.items()) or tuple(dic.items())
dic = {'1': 'a', '2': 'b', '3': 'c', '4': 'd', '5': 'e'}
for key, value in dic.items():
print("Key: {0} Value: {1}".format(key,value))
del dic[key]
print(dic)
dic[key] = value
print(dic)
Story: #2007865
Task: #40197
Depends-On: https://review.opendev.org/756859
Change-Id: Ieb4cf38038ffb4d1a152f8ab3b64a14098c7cbb3
The change updates the imports to use simplejson library and
monasca_api.common.rest instead of monasca_common.rest, since
it was moved to this project during the API's merge.
Temporarily set following jobs as non-voting:
* monasca-tempest-python3-influxdb
* build-monasca-docker-image
* publish-monasca-api-docker-image
Change-Id: Ife3d2c9795a9dc406c2927cc9a077dda01c183c6
Story: 2007549
Task: 39389
The change introduces the possibility to run the API with the new
confluent-kafka client. It has to be enabled in the configuration file.
Story: 2003705
Task: 35859
Depends-On: https://review.opendev.org/680653
Change-Id: Id513e01c60ea584548c954a8d2e61b9510eee8de
Kombu 4.6.4 causes issues with eventlet 0.23.0 and 0.25.0[1].
Due to an upper-constraint version bump, we're seeing failures
on openstack gate.
This patch fixes the issue.
[1] https://review.opendev.org/#/c/678078
Change-Id: Ibec126bba7991f22611b476449e760d4faf5b8e8
Falcon 2.0.0 introduces some breaking changes. The relevant ones here are:
- falcon.testing.TestCase.api property was removed
- falcon.testing.TestBase class was removed
Additionally, the default behaviour for handling trailing slashes on
URIs also changed:
https://falcon.readthedocs.io/en/latest/user/faq.html#how-does-falcon-
handle-a-trailing-slash-in-the-request-path
This commit adds support for using the new release. It currently makes
no effort to be backwards compatible with older releases.
The change also updates the requirements for influxdb and sphinx
libraries to match global requirements.
Until monasca-log-api implementation is not updated to support the new
version of Falcon, `monascalog-python3-tempest` is marked to be
non-voting as agreed in the team meeting.
Story: 2005695
Task: 31015
Change-Id: I03bc8d502a333a7a71d9c12b8ddc7c5dc0a4f588
Add a tool to run before upgrading a Monasca installation
that will check for potential issues and report on readiness to upgrade.
For Monasca, this initial version effectively does nothing, but gives a
framework for future checks to be included.
This is a community-wide story for Stein [1].
Story: 2003657
Task: 26142
[1] https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html
Change-Id: I799602caa4029d67f59307bf1ca0d1e8f254d415
Added policies and used policy enforcement engine
from monasca-common.
- Replaced security with oslo.policy
- Updated unit tests and implemented some new tests
- Added a new entry point for generating sample policy file by tox
story: 2001233
task: 6355
Change-Id: I4aa444fe6ec883160c03c201145c77994b6615f9
Signed-off-by: Amir Mofakhar <amofakhar@op5.com>
We will manage the eventlet version using constraints now. See the
thread starting at
http://lists.openstack.org/pipermail/openstack-dev/2018-April/129096.html
for more details.
Additionally:
* add funcsigs to lower-constraints.txt
* set lower-constraint for sphinx=1.6.2
Change-Id: Ia9d795125a00d4bbe6d52738f0d8dc286ed4c676
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Following replaces usage of standard
json with monasca-common rest layer.
Depends-On: I186abe4cdafd58d998f8aaf36d866795771a9e0a
Change-Id: I2f9d22a2c5e18826c8f9bb1e817ad963731b390f
Use create_engine in oslo.db instead of the sqlalchemy one to get
the optimization benefit from oslo.db.
Breaking change would be replacing database.url with
database.connection therefore database.url will be still
supported until Pike is released. database.url
has been marked as deprecated option.
Change-Id: Id3cdafa791a7d2558a5b065022a9afc6ff31e004
Closes-bug: #1640419
Versions of Influx or Cassandra between tox and devstack
env were different. Now in both places OpenStack requirements
are used.
Additionally:
- moved Influx and Cassandra to test-requirements.
Change-Id: I5be1be023b605a0b7efe718796877b90f9dc06f0
Related-Bug: #1628719
Because kafka-python is now forked and embedded in monasca-common monasca-api
needs to use those interfaces instead of using kafka-python directly.
Change-Id: I3b30721c46af3e472947cf8d776604b33c82aa8a
Similar to other openstack projects,
monasca-api should provide information
about request's context in the log information.
This is done by:
* implementing custom Request that creates context (oslo.context)
* changing logging configuration to use ContextLogFormatter
Since information like tenant-id can be
retrieved from the context, modified resource code to use
that.
Also moved 'limit' directly to request property.
Change-Id: I917fa2cba99dc668842fea0a62cda2cabd796d09
Ghanshyam Mann