Operations-related content for OpenStack-Ansible
Go to file
Doug Hellmann 00f668d9aa Update reno for stable/newton
Change-Id: I3097f91ad27bbd92af6ee1d4d1782a75b2325388
2016-09-30 19:31:37 +00:00
ansible_tools Playbook to mount drives in swift object nodes 2016-08-02 10:33:21 +05:30
cluster_metrics Merge "Added playbook to deploy Kapacitor" 2016-09-28 14:43:19 +00:00
doc Remove osa-differ 2016-09-14 12:23:48 -05:00
generate_requirements Add generate_requirements tool 2016-08-02 13:52:54 -04:00
multi-node-aio Add test to ensure that directories are not empty 2016-09-07 16:40:00 +00:00
releasenotes Update reno for stable/newton 2016-09-30 19:31:37 +00:00
.gitignore Add base test scaffolding for repo 2016-06-14 15:32:40 +00:00
.gitreview Added .gitreview 2016-05-27 11:57:18 +00:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 20:57:24 +02:00
CONTRIBUTING.rst Add base test scaffolding for repo 2016-06-14 15:32:40 +00:00
LICENSE Add base test scaffolding for repo 2016-06-14 15:32:40 +00:00
README.rst Add Galaxy role section and add OSA backup role 2016-07-27 17:47:16 +00:00
run_tests.sh Add base test scaffolding for repo 2016-06-14 15:32:40 +00:00
setup.cfg Update home page link in cfg file 2016-09-20 12:09:10 +05:30
setup.py Updated from global requirements 2016-07-15 03:57:35 +00:00
test-requirements.txt Updated from global requirements 2016-09-28 16:58:09 +00:00
tox.ini Use centralised test scripts 2016-09-27 17:18:43 +01:00

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.

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.