4fe837b26c
We want to default to running all tox environments under python 3, so set the basepython value in each environment. We do not want to specify a minor version number, because we do not want to have to update the file every time we upgrade python. We do not want to set the override once in testenv, because that breaks the more specific versions used in default environments like py35 and py36. Change-Id: Id8547917da6ffae8b4967ff90d9989f79734ce6f Signed-off-by: Doug Hellmann <doug@doughellmann.com> |
||
|---|---|---|
| ansible_tools | ||
| 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 | ||
| prometheus | ||
| pxelinux-provisioning | ||
| releasenotes | ||
| scripts | ||
| 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:
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.