OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 day ago|
|common||1 year ago|
|config-generator||2 months ago|
|docker||3 days ago|
|etc/monasca||6 months ago|
|java||5 months ago|
|monasca_persister||1 week ago|
|perf||2 months ago|
|playbooks||5 days ago|
|releasenotes||2 weeks ago|
|.coveragerc||2 weeks ago|
|.gitignore||2 months ago|
|.gitreview||1 day ago|
|.stestr.conf||1 year ago|
|.testr.conf||2 years ago|
|.zuul.yaml||3 days ago|
|LICENSE||5 years ago|
|README.rst||1 month ago|
|bindep.txt||2 years ago|
|lower-constraints.txt||2 months ago|
|pom.xml||1 year ago|
|requirements.txt||1 year ago|
|run_maven.sh||3 years ago|
|setup.cfg||2 months ago|
|setup.py||2 years ago|
|test-requirements.txt||2 months ago|
|tox.ini||5 days ago|
The Monitoring Persister consumes metrics and alarm state transitions from the Message Queue and stores them in the Metrics and Alarms database.
Although the Persister isn't primarily a Web service it uses DropWizard, https://dropwizard.github.io/dropwizard/, which provides a nice Web application framework to expose an http endpoint that provides an interface through which metrics about the Persister can be queried as well as health status.
The basic design of the Persister is to have one Kafka consumer publish to a Disruptor, https://github.com/LMAX-Exchange/disruptor, that has output processors. The output processors use prepared batch statements to write to the Metrics and Alarms database.
The number of output processors/threads in the Persister can be specified to scale to more messages. To horizontally scale and provide fault-tolerance any number of Persisters can be started as consumers from the Message Queue.
Requires monasca-common from https://github.com/openstack/monasca-common. Download and build following instructions in its README.md. Then build monasca-persister by:
mvn clean package
A sample configuration file is available in java/src/deb/etc/persister-config.yml-sample.
A second configuration file is provided in java/src/main/resources/persister-config.yml for use with the vagrant "mini-mon" development environment.
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.
To install the Python monasca-persister modules, git clone the source and run the following command:
$ sudo python setup.py install
To run the unit tests use:
$ tox -e py27,py35