Brad Klein b1b3b3f1d7 Don't log the entire token if auth failure
This change comes as a recommendation from our keystone
engineer, not good practice to log full tokens.  Also change
this log message:

'monasca.common.middleware.TokenAuth: 401 No token found.'

to debug level to avoid filling the log with these
messages as the result of a load balancer calling HEAD
without a token.

Change-Id: I6a04e98c398e163fb972020be1e580869b2538d7
2016-04-12 10:25:21 -06:00
2015-10-17 22:30:45 +00:00
2014-05-01 16:22:06 -07:00
2016-03-08 11:53:25 -07:00

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