9cd0d2836c
Using "python setup.py check -r -s" method of checking the package has been deprecated with the new recommendation to build the sdist and wheel, then running "twine check" against the output. Luckily, there is already a job that covers this that only runs when the README, setup.py, or setup.cfg files change, making running this in the pep8 job redundant. This covered by the test-release-openstack-python3 that is defined in the publish-to-pypi-python3 template. More details can be found in this mailing list post: http://lists.openstack.org/pipermail/openstack-dev/2018-October/136136.html Change-Id: I7a3555dd0f0c4bcd1969ca7d3669369d7517a6be Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> Depends-On: https://review.openstack.org/615557
Team and repository tags
Overview
monasca-common is a collection of modules containing
reusable application and platform code for building monitoring related
services.
Python
To install the Python monasca-common modules, git clone the source and run the following command:
$ sudo python setup.py installTo run the unit tests use:
$ tox -e py27,py35For information on contributing, see Contribution Guidelines.
- License: Apache License, Version 2.0
- Source: https://git.openstack.org/cgit/openstack/monasca-common
- Bugs: https://storyboard.openstack.org/#!/project/865
Java
Build Instructions
Download and do mvn install.
$ cd java
$ mvn clean installCaution
There is a pom.xml in the base directory but that should only be used for the Zuul 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
- monasca-common-model - Common domain and event models for monitoring services.
Platform Sub-Projects
- monasca-common-dropwizard - Utilities for building and testing dropwizard services.
- monasca-common-hibernate - Hibernate based model of Monasca SQL schema
- monasca-common-influxdb - InfluxDB related utilities.
- monasca-common-kafka - Various utilities for working with Kafka.
- monasca-common-persistence - Persistence related infrastructure and utilities.
- monasca-common-streaming - Streaming related utilities.
- monasca-common-testing - A set of testing related dependencies.
- monasca-common-util - Various utilities such as for serialization, dependency injection, date and time, invocation retries, concurrency, etc.