Dmitriy Rabotjagov d0e8674f92 Basic implementation of masakari-monitors
With this change masakari-monitors will be installed on hosts
which are in group masakari-monitor (supposed to be nova compute hosts)

hostmonitor depends on pacemaker with corosync, which are implemented by
https://github.com/mit-scripts/ansible-pacemaker-corosync

Masakari api/engine config was simplified and unneccesary defaults
were removed from it.

Role now uses default ``systemd_service`` role for systemctl configuration

Co-Authored-By: Jesse Pretorius <jesse.pretorius@rackspace.co.uk>
Implements: blueprint masakari-ansible-plugin
Change-Id: I334877c0111a45d3f3a74e7f56931786f4301713
2018-11-06 19:46:53 +02:00

75 lines
829 B
Plaintext

[all]
localhost
infra1
masakari1
openstack1
compute1
[all_containers]
infra1
openstack1
masakari1
[oslomsg_rpc_all]
infra1
[oslomsg_notify_all]
infra1
[rabbitmq_all]
infra1
[galera_all]
infra1
[memcached_all]
infra1
[service_all:children]
rabbitmq_all
galera_all
memcached_all
[keystone_all]
openstack1
[masakari_all:children]
masakari_api
masakari_engine
masakari_monitor
[utility_all]
openstack1
[masakari_api]
masakari1
[masakari_engine]
masakari1
[masakari_monitor]
compute1
[nova_compute]
compute1
[nova_conductor]
openstack1
[nova_console]
[nova_api_metadata]
[nova_api_os_compute]
openstack1
[nova_scheduler]
[nova_api_placement]
openstack1
[nova_all:children]
nova_compute
nova_conductor
nova_api_os_compute
nova_api_placement