
Elasticsearch fails to start on first run when duplicate entries in the cluster.initial_master_nodes variable are present, as they are all required during the initial bootstrapping. It is currently possible for duplicates to be present in this when nodes are forced to be master-eligible using elasticsearch_node_master: true due to the master node setting algorithm within data-node-variables. This commit ensures that all values within the Ansible master_nodes variable are unique, whilst keeping the total count of master nodes the same, preventing Elasticsearch from crashing during initial cluster discovery. Change-Id: I3763b22ea47c9b5b0f534793ccc6a887f96dc649
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.
Description
Languages
Jinja
82.1%
Shell
12.1%
Python
4.7%
PHP
1.1%