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
This change defaults the warning-as-error to True:
https://review.openstack.org/#/c/559348/
Which is causing our documentation jobs to fail locally and in the
gate/check queues.
This commit fixes both issues that are causing failures so that
we can get the doc jobs passing again.
Change-Id: I5dd71b6c69b975f8dd922aa3cab9d027f535f422
This part does not really belong to the contributor guide. Also
following up on the comment from the previous review [1].
[1] https://review.opendev.org/729270
Change-Id: Id49130044c3be3ec3c4b00736f678b541bdc5dfa
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Ia65588ae734c6995c060332e5198afb95b105084
At present, all time series are accumulated in the same database in
InfluxDB. This makes queries slow for tenants that have less data. This
patch enables the option to use separate database per tenancy.
This changeset implements the changes on monasca-api which handles read
requests to InfluxDB database.
It also updates the relevant docs providing link to the migration tool
which enables users to migrate their existing data to a database per
tenant model.
Change-Id: I7de6e0faf069b889d3953583b29a876c3d82c62c
Story: 2006331
Task: 36073
The change adds reviews prioritisation process description. It also adds
link to the Gerrit dashboard with the list of prioritized code changes.
Change-Id: If183de198c8ad90553ee5b54b6ba0a9cef86d25c
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: I89f2de245df7d5393a066d5c225897887978b03e
api-config.conf is the deprecated path for the configuration file. The
new path is /etc/monasca/monasca-api.conf .
Story: 2004708
Task: 28987
Change-Id: If06d9114529c3ef4520247dfc7c32d3769f07084
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
References to Monasca boards and worklists are added to contributor
documentation at https://docs.openstack.org/monasca-api
Story: 2004093
Task: 27495
Change-Id: I4378c50e598e5eea6ea982877229c26892ae024b
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
- make pep8 working by removing ChangeLog that is not generated
- make maven working by removing condidation for user
- make legacy dsvm working by using $USER intstead of hardcoded jenkins
Change-Id: I30f2edc4d34d0fad63f961f99dcecaf5c767f57f
The document shortly describes how to report bugs and propose new
features. Specifications are introduced to the workflow to allow
describing and reviewing more complex features and to document team's
priorities.
Change-Id: I2fd9df1d242d9be4378eb497e1b5edfc41ac518c
Depends-On: Ie2d6f4391f8d711aa057c6cc3ff6fd475ee73754
Story: 2001171
Task: 4905
Change migrates the monasca-api to use oslo-config-generator in
order to always build newest configuration file. That removes
the need of maintaning the file along with changes to oslo configuration.
The example of the file is also included in the documentation.
Also:
* ported case for launching api under WSGI and allowing the argument
parsing of oslo to take place
Story: 2000970
Task: 4865
Story: 2000964
Task: 4106
Change-Id: I57547b0e2122e40f58db5f949773900b76214526
Hasan Acar