7dd097344f
Neither elastic nor logstash elements were present in container_skel while they were referenced in component_skel which is not valid for dynamic_inventory. So attempt to generate it resulted in: KeyError: 'elastic-logstash' here [1] Also elaborate more on conf.env sample as per the intents of https://review.opendev.org/c/openstack/openstack-ansible-ops/+/707849 [1] https://opendev.org/openstack/openstack-ansible/src/branch/master/osa_toolkit/generate.py#L266 Change-Id: I74a4788ff25c5ef45c064d1f8309002b1731ad7a
46 lines
931 B
YAML
46 lines
931 B
YAML
# For the puposes of this example, the kibana nodes have been added to
|
|
# different host machines that the logging nodes. You can also split out
|
|
# elastic-logstash into separate containers and put elasticsearch on
|
|
# more suited hosts. The intention here is to show that the different
|
|
# components can scale independently of one another.
|
|
|
|
kibana_hosts:
|
|
infra01:
|
|
ip: 172.22.8.24
|
|
infra02:
|
|
ip: 172.22.8.25
|
|
infra03:
|
|
ip: 172.22.8.26
|
|
|
|
elastic-logstash_hosts:
|
|
logging01:
|
|
ip: 172.22.8.27
|
|
logging02:
|
|
ip: 172.22.8.28
|
|
logging03:
|
|
ip: 172.22.8.29
|
|
|
|
#elastic_hosts:
|
|
# elastic01:
|
|
# ip: 172.22.8.30
|
|
# elastic02:
|
|
# ip: 172.22.8.31
|
|
# elastic03:
|
|
# ip: 172.22.8.32
|
|
|
|
#logstash_hosts:
|
|
# logging01:
|
|
# ip: 172.22.8.27
|
|
# logging02:
|
|
# ip: 172.22.8.28
|
|
# logging03:
|
|
# ip: 172.22.8.29
|
|
|
|
apm-server_hosts:
|
|
logging01:
|
|
ip: 172.22.8.27
|
|
logging02:
|
|
ip: 172.22.8.28
|
|
logging03:
|
|
ip: 172.22.8.29
|