Operations-related content for OpenStack-Ansible
de88293f24
/usr/lib/systemd/system/elasticsearch.service comes with a TimeoutStartSec=75, which is not enough time for a somewhat busy E5-2430L v2 @ 2.40GHz to get things going. We don't want to permanently override that with a default of 75 in case they decide to bump or remove that timeout in the future. Change-Id: Ida8668f5548a15a8f597839bd9002585aeea5d1a |
||
|---|---|---|
| ansible_tools | ||
| bootstrap-embedded-ansible | ||
| bowling_ball | ||
| cluster_metrics | ||
| doc | ||
| elements/slow-network | ||
| elk_metrics | ||
| elk_metrics_6x | ||
| elk_metrics_7x | ||
| generate_requirements | ||
| grafana | ||
| graylog | ||
| leap-upgrades | ||
| multi-node-aio | ||
| osa-gate-profile | ||
| osquery | ||
| overlay-inventories | ||
| prometheus | ||
| pxelinux-provisioning | ||
| rabbit-rescue | ||
| scripts | ||
| skydive | ||
| tests | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| multi-node-aio-xenial-ansible | ||
| README.rst | ||
| run_tests.sh | ||
| tox.ini | ||
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.