Doug Hellmann 2a362bea97 ignore python2-specific code under python3 for pep8
The type 'long' no longer exists under python 3. The runtime execution
of the code using it in the metrics module already detects the python
version, but when the linter is run under python 3 it does not apply
the same check. Add a noqa pragma to tell the linter to ignore the
line where 'long' is referenced to avoid an error.

Change-Id: If806e6461358ea523708eceed6fdcc3dfb8d75a9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-06-06 17:03:33 -04:00
2018-04-04 14:39:41 +00:00
2015-10-17 22:30:45 +00:00
2018-03-22 15:47:51 -04:00
2017-04-12 18:16:38 +02:00
2014-05-01 16:22:06 -07:00
2017-12-19 13:12:53 -08:00
2017-03-02 19:51:04 +01:00
2017-03-02 11:47:03 +00:00
2018-04-10 08:40:11 +00:00

Team and repository tags

Team and repository tags

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

To install the Python monasca-common 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
Description
Monasca common classes
Readme 4.8 MiB
Languages
Java 56.7%
Python 40.5%
Shell 1.3%
Dockerfile 1.1%
ANTLR 0.4%