
When running a multi-node ELK stack (5+ nodes) the elasticsearch server needs to be able to mark and identify nodes that will be data and master nodes. This change ensures that the first set of available master nodes is mark accordingly as both data and master and that all other nodes are marked as cluster members with alternating nodes being marked as data nodes. With this change the cluster will be able to grow as well as handle large data sets more efficiently. This change ensures that sharding is correctly started when the cluster is deployed and that the beat services are using the recommended sharding practices. Change-Id: Id555132199f268b21aaa939a84760c744238dd2b Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
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.
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.
Description
Languages
Jinja
82.1%
Shell
12.1%
Python
4.7%
PHP
1.1%