rpi_exporter

Ansible Role: rpi_exporter

Description

Deploy rpi-exporter using ansible.

Requirements

Ansible >= 2.7 (It might work on previous versions, but we cannot guarantee it)

Role Variables

All variables which can be overridden are stored in defaults/main.yml file as well as in table below.

Name	Default Value	Description
`rpi_exporter_version`	0.6.0	rpi-exporter packaged version. Also accepts `latest` as parameter.
`rpi_exporter_web_listen_address`	"0.0.0.0:9243"	Address on which rpi_exporter will listen
`rpi_exporter_system_group`	"rpi-exporter"	System group used to run rpi-exporter
`rpi_exporter_system_user`	"rpi-exporter"	System user used to run rpi-exporter

Example

Playbook

Use it in a playbook as follows:

- hosts: all
  roles:
    - paulfantom.rpi_exporter

Local Testing

The preferred way of locally testing the role is to use Docker and molecule (v2.x). You will have to install Docker on your system. See "Get started" for a Docker package suitable to for your system. We are using tox to simplify process of testing on multiple ansible versions. To install tox execute:

pip3 install tox

To run tests on all ansible versions (WARNING: this can take some time)

tox

To run a custom molecule command on custom environment with only default test scenario:

tox -e py35-ansible28 -- molecule test -s default

For more information about molecule go to their docs.

If you would like to run tests on remote docker host just specify DOCKER_HOST variable before running tox tests.

Travis CI

Combining molecule and travis CI allows us to test how new PRs will behave when used with multiple ansible versions and multiple operating systems. This also allows use to create test scenarios for different role configurations. As a result we have a quite large test matrix which will take more time than local testing, so please be patient.