monasca/persister repository overview

⁠monasca-persister Dockerfile

This image contains a containerized version of the Monasca persister.

There are two implementations of the monasca-persister:

• python (tagged -python or empty) - Dockerfile⁠
• java (tagged -java) - Dockerfile⁠

Currently the python images are recommended. For more information on the Monasca project, see the wiki⁠.

Source repositories: monasca-persister⁠ · monasca-docker⁠

⁠Tags

The images in this repository follow a few tagging conventions:

• latest: refers to the latest stable Python point release, e.g. 1.3.0-python
• latest-python, latest-java: as above, but specifically referring to the latest stable Python or Java point release, e.g. 1.3.0
• 1.3.0, 1.3, 1: standard semver tags, based on git tags in the official repository⁠
• 1.3.0-python, 1.3-python, 1-python: as above, but specifically referring to python-based images
• mitaka, newton, etc: named versions following OpenStack release names built from the tip of the stable/RELEASENAME branches in the repository
• mitaka-python, newton-python: as above, but specifically Python-based images
• master, master-DATESTAMP: unstable builds from the master branch, not intended for general use

Note that unless otherwise specified, images will be Python-based. All Java-based images will be tagged as such.

⁠Usage

To run, the persister needs to connect to a working Zookeeper and Kafka as well as a database. To do anything of use, one or more monasca-api⁠ instances should output to the Kafka topic as well.

In environments resembling the official Kubernetes environment⁠ the image does not require additional configuration parameters, and can be run like so:

docker run -it monasca/persister:latest

⁠Configuration

If additional values need to be overridden, a new config file or jinja2 template can be provided by mounting a replacement at /etc/monasca-persister/persister.conf.j2. If jinja2 formatting is not desired, the environment variable CONFIG_TEMPLATE can be set to false. Note that the jinja2 template should still be overwritten (rather than the target file without the .j2 suffix) as it will be copied at runtime.

The config file source is available in the repository⁠. If necessary, the generated config file can be viewed at runtime by running:

docker exec -it some_container_id cat /etc/monasca-persister/persister.conf