Ansible role to setup Grafana.
Family | Distribution | Version | Test Status |
---|---|---|---|
Debian | Debian | Jessie | |
Debian | Debian | Wheezy | |
Debian | Ubuntu | Xenial | |
Debian | Ubuntu | Trusty | |
Debian | Ubuntu | Precise | |
Debian | Ubuntu | Vivid |
- ansible >= 1.9.6
- grafana_admin_password: password for the Grafana administrator account.
- grafana_admin_user: user name for the Grafana administrator account.
- grafana_apt_dependencies: packages needed to be able to run this playbook or install Grafana.
- grafana_conf_file: the file that will contain Grafana's configuration.
- grafana_conf_data: the contents of Grafana's configuration file.
- grafana_default: the contents of Grafana's init script environment.
- grafana_dir_conf: the directory where the Grafana configuration file will be stored.
- grafana_dir_data: the directory where the Grafana data will be stored.
- grafana_dir_home: the Grafana home directory.
- grafana_dir_log: the directory where the Grafana log files will be stored.
- grafana_dir_plugins: the directory where the Grafana plugins will be stored.
- grafana_http_port: the port where the Grafana service will be running.
- grafana_group: the Grafana group.
- grafana_pid_file_dir: directory where PID file will be written to.
- grafana_pid_file: path to PID file.
- grafana_user: the Grafana user.
Unless stated otherwise a default value is provided for each of the variables mentioned above in the defaults
directory.
None.
- hosts: servers
roles:
- role: ansiblebit.grafana
- configuration: configuration tasks.
- debug: task to debug role variables.
- installation: installation tasks.
- validation: task to validate role variables.
To run the tests you will need to install:
To run all tests against all pre-defined OS/distributions * ansible versions:
$ tox
To run tests for trusty64
:
$ cd tests
$ bash test_idempotence.sh --box trusty64.vagrant.dev
# log file will be stores under tests/log
To perform debugging on a specific environment:
$ cd tests
$ vagrant up trusty64.vagrant.dev
# to provision using the test.yml playbook (as many time as you need)
$ vagrant provision trusty64.vagrant.dev
# to access the Vagrant box
$ vagrant ssh trusty64.vagrant.dev