Operations-related content for OpenStack-Ansible
df54d05bb8
The default Filebeat prospectors currently look for all log files in /var/log/. This can cause conflicts with auditbeat, which also monitors audit log files in /var/log and can fail to get a lock on the appropriate log files, subsequently failing. This commit explicitly removes audit log files from the Filebeat prospector path to remove this conflict. Change-Id: I2146bd6f4980610f32d27896406167458e08dffe |
||
|---|---|---|
| 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 | ||
| scripts | ||
| skydive | ||
| tests | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| multi-node-aio-xenial-ansible | ||
| README.rst | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| 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.