01352a45f6
Currently it is possible for the elk_beat_setup flag not to trigger the beat_setup role when no kibana nodes are present. This means that there is no way to update the index templates in this situation, so beats will just use a default index setup, and ILM policies will not be applied. This can lead to inconsistent configurations where manual deletion of default-templated indices is required. This can happen during an ELK version upgrade, where new templates should be created but aren't. This commit ensures that the beat setup role is run whenever the elk_beat_setup flag is set to true. As a result, the user can force index templates to be updated even when no kibana nodes are present to ensure consistency. It also documents the previously undocumented elk_beat_setup var in both the Beat role defaults and the beat_setup role itself Change-Id: Ife0d0f12d6b300b84b63c3af14add1732747d44f
Team and repository tags
OpenStack-Ansible Operator Tooling
This repository is a collecting point for various scripts and tools which OpenStack-Ansible Developers and Operators have found to be useful and want to share and collaboratively improve.
The contents of this repository are not strictly quality managed and are only tested by hand by the contributors and consumers. Anyone using the tooling is advised to very clearly understand what it is doing before using it on a production environment.
- Documentation for the project can be found at:
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/openstack-ansible-ops/
- The project source code repository is located at:
- The project home is at:
- The project bug tracker is located at:
Galaxy roles
OpenStack Ansible backup
This role will perform backups for OpenStack-Ansible deployments and it needs to run on the deploy node. It will backup data on container and then synchronize backup files to the deploy node.