We need to specify doc requirements in doc/requirements.txt to avoid problems with the pip resolver  for the release team . Removing specific doc requirements from test-requirements.txt. The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements . This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error. This project meet the conditions leading to the bug. /!\/!\/!\ Notice that I voluntarily added the doc directory even if no docs are generated here because zuul will try to pull this requirements from there first and the contained requirements are needed for reno but AFAIK the releasenotes dir is ignored by zuul. c.f  for further details. /!\/!\/!\ Bump a series of lower-constraints and requirements to work with new pip resolver, testing with steps outlined at  Fix Flake8 E741   http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html  http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html  http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html  https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36  http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019285.html  https://www.flake8rules.com/rules/E741.html Change-Id: Ic1504a18a780b0f517c5aa3dd3bfb04998d42e74
|2 years ago|
|common||4 years ago|
|config-generator||4 years ago|
|doc||2 years ago|
|docker||2 years ago|
|etc/monasca||4 years ago|
|java||3 years ago|
|monasca_persister||2 years ago|
|perf||4 years ago|
|playbooks||4 years ago|
|releasenotes||2 years ago|
|.coveragerc||4 years ago|
|.gitignore||4 years ago|
|.gitreview||4 years ago|
|.stestr.conf||5 years ago|
|.zuul.yaml||2 years ago|
|CONTRIBUTING.rst||3 years ago|
|LICENSE||9 years ago|
|README.rst||3 years ago|
|bindep.txt||6 years ago|
|lower-constraints.txt||2 years ago|
|pom.xml||5 years ago|
|requirements.txt||2 years ago|
|run_maven.sh||7 years ago|
|setup.cfg||2 years ago|
|setup.py||3 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||2 years ago|
The Monasca Persister consumes metrics and alarm state transitions from the Apache Kafka message queue and stores them in the time series database.
To install the Python monasca-persister modules, git clone the source and run the following command:
$ pip install -c https://releases.openstack.org/constraints/upper/master -e ./monasca-persister
To run the unit tests use:
$ tox -e py36
To start the persister run:
$ monasca-persister --config-file=monasca-persister.conf
A sample configuration file can be generated using the Oslo standards used in other OpenStack projects.
tox -e genconfig
The result will be in ./etc/monasca/monasca-persister.conf.sample
If the deployment is using the Docker files, the configuration template can be found in docker/monasca-persister.conf.j2.
For information on Java implementation see java/Readme.rst.
Contributing and Reporting Bugs
Ongoing work for the Monasca project is tracked in Storyboard.
Copyright (c) 2014 Hewlett-Packard Development Company, L.P.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.