4851e29e9c
It is currently assumed that the elasticsearch data nodes and the logstash nodes are co-located within the same container during deployment of the ELK stack. This commit is intended to remove that assumption by requiring specification of separate elastic and logstash groups. This is particularly important where instances of elasticsearch and logstash are separated for resource reasons, a common setup for an elastic cluster. The default setup for the elastic nodes has been simplified, with all non-coordinating nodes being both data and ingest nodes unless otherwise specified. This was previously defined algorithmically, with the elastic node setup tightly coupled to the placement of the logstash instances. Change-Id: Id06eb78b52705aefea9cfe1247f53bac58badd52
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.