Monasca common classes
Go to file
Laszlo Hegedus bfc88d4f05 Add unit tests for common Kafka module
Add tests for kafka producer and consumer modules. The test coverage
of monasca_common was was 9%. This is improved in this commit.

Show test coverage when running tox. Change the nosetests command to
show test coverage for the whole module.

Change-Id: I771a539aee5fa92c065ee16b5bb94c9ae7e7a09b
2016-05-17 10:50:12 +02:00
java Merge "Add Period to hibernate notification method" 2016-05-07 22:24:20 +00:00
monasca_common Add unit tests for common Kafka module 2016-05-17 10:50:12 +02:00
.gitignore initial python monasca-common code in monasca_common 2015-09-01 13:56:39 -06:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:30:45 +00:00
HACKING.rst Change repositories from stackforge to openstack 2015-10-19 09:50:12 +05:30
LICENSE Added license file 2014-05-01 16:22:06 -07:00
README.md Change repositories from stackforge to openstack 2015-10-19 09:50:12 +05:30
mkdocs.yml Change repositories from stackforge to openstack 2015-10-19 09:50:12 +05:30
pom.xml Change repositories from stackforge to openstack 2015-10-19 09:50:12 +05:30
requirements.txt Updating kafka requirements 2016-03-08 11:53:25 -07:00
run_maven.sh Fail main maven build if java maven build fails 2015-02-19 12:53:22 -07:00
setup.cfg Change repositories from stackforge to openstack 2015-10-19 09:50:12 +05:30
setup.py initial python monasca-common code in monasca_common 2015-09-01 13:56:39 -06:00
test-requirements.txt Remove sphinx requires from test-requirements 2016-03-29 19:52:32 +02:00
tox.ini Add unit tests for common Kafka module 2016-05-17 10:50:12 +02:00

README.md

Overview

monasca-common is a collection of sub-projects containing reusable application and platform code for building monitoring related services.

Build Instructions

Download and do mvn install.

cd java
mvn clean install

There is a pom.xml in the base directory but that should only be used for the StackForge build. The issue is that currently StackForge's bare-precise system only has Maven 2 on it and at least one of the modules of monasca-common requires Maven 3.

In order to get around this problem, the pom.xml in the base directory uses the exec-maven-plugin to run the script run_maven.sh. This script checks if the version of mvn is Maven 3 and if it is not, it downloads Maven 3 and then uses it to run the build in the java directory.

In addition, the run_maven.sh script copies the jar files that get built from java/*/target directories to the target directory in the base project directory. This is because the StackForge "monasca-common-localrepo-upload" job uploads any jar files from that directory to http://tarballs.openstack.org/ci/monasca-common. Copying the jar files to that directory made it so there didn't have to be changes made to the "monasca-common-localrepo-upload" job. The build for monasca-thresh downloads the jars it depends on from that location on tarballs.openstack.org.

A change has been submitted to StackForge to switch to bare-trusty for this build in the hopes that those systems will have maven 3, but it is not known how long that change will take to be accepted.

Application Specific Sub-Projects

Platform Sub-Projects

python monasca-common

To install the python monasca-common modules, git clone the source and run the following command::

sudo python setup.py install

To run the python monasca-common tests use::

nosetests monasca_common/tests