openstack
/
monasca-api
Code Issues Proposed changes
2,338 Commits 8 Branches 35 Tags 26 MiB
Commit Graph

8 Commits

Author SHA1 Message Date
Hasan Acar a24fd834d0 fix: migrate CI to jammy 
fix: change tox.ini

fix: change queries for list_dimension_names and list_dimension_values because of influxdb time filter problem

fix: remove build_sphinx group from setup.cfg

fix: handle hashlib security problem

Change-Id: I0d31a8db5ed71c70e7b878ce5e7940e041d0fa43

Change-Id: I6f7066da10e834550cbf0c053c7bf425ac0ead93

Change-Id: If9575aee73d600bbc84fcdf58deb1c57b508d9c2

Change-Id: If515eaeee7539da3ca49997e88785dc65572b334
 2024-02-22 14:35:03 +00:00
Ghanshyam Mann dea6f95c15 [goal] Deprecate the JSON formatted policy file 
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
 2021-02-02 14:36:06 +00:00
kuangcx 721d5e8fb5 make the variable name more detailed 
Change-Id: I67961eca692e4fe79fd74ba16f3cf25edb7ee3ea
 2020-08-05 16:33:18 +08:00
Hervé Beraud 72bc9a91ab Stop to use the __future__ module. 
The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: Ifd61bc8e043ac9af446ae31bffd82f67f34facbc
 2020-06-02 20:24:41 +02:00
Andreas Jaeger abad342eb2 Update hacking for Python3 
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.

Fix problems found by updated hacking version.

Remove hacking and friends from lower-constraints, they are not needed
there at all.

Change-Id: I35d848e9af297d3561ea2838a4808166d1c36601
 2020-04-22 07:37:55 +00:00
Thomas Bechtold 73b4c4ab41 Support standard config file path for monasca-api 
The standard path is /etc/monasca/monasca-api.conf (instead of
/etc/monasca/api.conf).

/etc/monasca/api.conf and /etc/monasca/api-config.conf are still
supported (in case the new file paths are not available) but a
deprectation message is printed.

Story: 2004708
Task:  28738

Depends-On: https://review.openstack.org/#/c/628936/
Change-Id: I94e853f869db7b0a434a1a05517255ae62131132
 2019-01-08 12:17:05 +01:00
Joseph Davis 22be5aa57f Add "monasca-status upgrade check" for pre-upgrade 
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
 2018-11-12 11:24:21 -08:00
Johannes Grassler 0250f81cdc Add monasca_db command line tool 
This commit adds a schema management tool for the Monasca
configuration database. Apart from the usual OpenStack schema
management tool subcommands (stamp, upgrade, version) it has
two extra subcommands:

* fingerprint: for computing a SHA1 fingerprint of the
               currently currently active database schema.
* detect-revision: for identifiying the Alembic revision
                   (if any) corresponding to a database
                   schema that was created with one of the
                   legacy SQL scripts.

The data provided by the detect-revision subcommand can be
used for stamping the database with Alembic version metadata
when transitioning an existing Monasca configuration database
to Alembic based database migrations.

Story: 2001654
Task: 14341

Change-Id: Ibdd877a23ab5d6d1bbf8d83515c0197554098526
 2018-08-01 11:10:14 +00:00