Hervé Beraud 37411e792a Add doc/requirements
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].

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 [4].

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 [4] for further details.
/!\/!\/!\

Bump a series of lower-constraints and requirements to work with new pip
resolver, testing with steps outlined at [5]

Fix Flake8 E741 [6]

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36
[5] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019285.html
[6] https://www.flake8rules.com/rules/E741.html

Change-Id: Ic1504a18a780b0f517c5aa3dd3bfb04998d42e74
2021-01-18 10:55:41 +01:00
2021-01-18 10:55:41 +01:00
2019-09-17 10:29:34 +02:00
2021-01-18 10:55:41 +01:00
2019-01-22 13:32:21 +08:00
2019-04-15 15:04:28 +02:00
2019-04-05 13:33:43 +02:00
2019-02-19 10:46:25 +00:00
2019-04-19 19:26:25 +00:00
2017-09-22 14:13:18 +02:00
2020-10-15 11:30:50 +00:00
2017-04-12 18:10:55 +02:00
2020-05-19 16:25:13 +02:00
2021-01-18 10:55:41 +01:00
2018-01-15 16:39:54 +08:00
2020-11-24 15:10:57 +01:00
2020-04-05 09:58:52 +02:00
2021-01-18 10:55:41 +01:00
2021-01-18 10:55:41 +01:00

Monasca Persister

image

The Monasca Persister consumes metrics and alarm state transitions from the Apache Kafka message queue and stores them in the time series database.

Running

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

Configuration

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.

Java

For information on Java implementation see java/Readme.rst.

Contributing and Reporting Bugs

Ongoing work for the Monasca project is tracked in Storyboard.

License

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

http://www.apache.org/licenses/LICENSE-2.0

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.

Description
Monasca Database Persister
Readme 5.7 MiB
Languages
Java 49.4%
Python 45%
Shell 3.9%
Jinja 1.1%
Dockerfile 0.6%