x/monasca-vagrant
Code Issues Proposed changes

Fix monasca_checks host_alive YAML configuration

Browse Source 
The YAML structure for monasca_checks' host_alive was incorrect in the
playbooks, preventing host_alive checks from functioning.  One would
see no host_alive_status metrics, and this error in collector.log:

.host_alive(services_checks.py:92) | Each service check must have a name

Change-Id: I52a91362d7c958d27087933ccd91de326da9392e
This commit is contained in:
David Schroeder 2014-12-03 15:47:42 -07:00
parent fbf1a0074c
commit 219facab24
2 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
devstack.yml
View File

@ -18,10 +18,9 @@
ssh_timeout: 0.5 ssh_timeout: 0.5
ping_timeout: 1 ping_timeout: 1
instances: instances:
- mini-mon: - name: mini-mon
name: mini-mon host_name: 192.168.10.4
host_name: 192.168.10.4 alive_test: ssh
alive_test: ssh
keystone_url: http://192.168.10.5:35357/v3 keystone_url: http://192.168.10.5:35357/v3
keystone_admin_token: ADMIN keystone_admin_token: ADMIN
keystone_users: keystone_users:

7
mini-mon.yml
View File

@ -59,10 +59,9 @@
ssh_timeout: 0.5 ssh_timeout: 0.5
ping_timeout: 1 ping_timeout: 1
instances: instances:
- devstack: - name: devstack
name: devstack host_name: 192.168.10.5
host_name: 192.168.10.5 alive_test: ssh
alive_test: ssh
mysql_host: "{{mini_mon_host}}" mysql_host: "{{mini_mon_host}}"
mysql_users: mysql_users:
notification: password notification: password