22f997f7fa
This change will ensure that the upper and lower memory limits are set to whole numbers when dynamically setting the memory limits. Before this change a memory limit could be a float, and in certain versions of ansible + python the option could evaluate to 0, which would break everything. Change-Id: Ibfb8af60db6566937cbf77243b0e6848d542665d Signed-off-by: cloudnull <kevin@cloudnull.com> |
||
|---|---|---|
| ansible_tools | ||
| bootstrap-embedded-ansible | ||
| bowling_ball | ||
| cluster_metrics | ||
| doc | ||
| elements/slow-network | ||
| elk_metrics | ||
| elk_metrics_6x | ||
| generate_requirements | ||
| grafana | ||
| graylog | ||
| leap-upgrades | ||
| multi-node-aio | ||
| osa-gate-profile | ||
| osquery | ||
| overlay-inventories | ||
| prometheus | ||
| pxelinux-provisioning | ||
| releasenotes | ||
| 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:
-
https://git.openstack.org/cgit/openstack/openstack-ansible-os_ops
- 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.