12f4aca8db
* ensure you define [graphite] and [grafana] in your hosts file. * The grafana service is lightweight and can live on the same host as the graphite host. However, it can also be separated to run on its own server if desired. * Once the graphite-web services are deployed (which also sets up the carbon-cache service), and the grafana service is deployed, you will need to define the data source for your graphite host in the grafana instance. * The grafana service runs on port 3000, and has the default user/pass of admin/admin. * username / password for graphite is set in install/group_vars/all * firewalld is disabled on the grafana and graphite hosts If firewalls are needed, iptables-service is suggested but left us to deployment team. * Added gen_hostfile.sh updates for the needed hosts entries, with comments to the user on what needs to be in 'hosts' file. graphite db sets up Change-Id: I27660b6ecbf019699c124b02b4b4fd6185547a54
10 lines
109 B
YAML
10 lines
109 B
YAML
---
|
|
#
|
|
# Playbook to install grafana
|
|
#
|
|
|
|
- hosts: grafana
|
|
remote_user: root
|
|
roles:
|
|
- { role: grafana }
|