
This commit adds playbooks and roles to the ops tooling setup to build, deploy, and operate environments with skydive within in it. Skydive is a network analyzer which will allow users to explore their topology in real-time using a defined storage back-end for captures, alerts, and more. The initial implementation of skydive deploys agents throughout the environment and wires them all back to a cluster of analyzers which leverage elasticsearch for its persistent storage back-end. Storage back-ends are load balanced from the within the analyzer nodes using the traefik light-weight reverse proxy. This setup gives skydive a fully fault tolerant deployment. Tests have been added to ensure the binary installation process is validated. While these jobs are non-voting today, they'll be iterated on and made passing in the subsequent PRs. All jobs are following the selective pattern which allows these tools to be gated in the mono-repo without impacting all other tools within the environment. Change-Id: Iaa1152566f2b615d67a33dc94ebdbebb1b492a9d Signed-off-by: Kevin Carter <kevin@cloudnull.com>
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.