Go to file

Antony Messerli 6c101e313c Better handling for resuming leapfrog upgrade

Copies the openstack-release file to another location
so that the original version being upgraded can be referenced
in the event of a failure where openstack-setup-hosts has
replaced the openstack-release file.  That way the list
of versions to upgrade is correct upon re-running the
leapfrog upgrade script.

Change-Id: I63de16bf27813dd623e996a5ac5de7bb8f8668b6

2018-12-12 17:14:12 -06:00

ansible_tools

Added ability to cleanup venv tgz, use find module

2017-12-15 11:11:59 +01:00

bootstrap-embedded-ansible

Merge "add short name for distros"

2018-11-30 04:51:09 +00:00

bowling_ball

Use clouds.yaml

2018-02-13 11:02:27 +00:00

cluster_metrics

Add grafana

2018-04-13 10:31:34 -05:00

doc

Trivial: Update pypi url to new url

2018-04-21 09:03:47 +08:00

elements/slow-network

change the phase we run post-install.d actions

2017-11-28 10:42:44 -06:00

elk_metrics

[Trivial Fix] Replace Chinese punctuation with English punctuation

2018-09-28 09:41:38 +08:00

elk_metrics_6x

Update elk_6x for 6.5.x

2018-11-27 18:56:22 +00:00

generate_requirements

Replaces yaml.load() with yaml.safe_load()

2017-02-04 18:21:33 +08:00

grafana

Update rollback plan and configs

2018-04-26 16:41:51 -05:00

graylog

Add Graylog Central Logging

2018-04-24 21:43:03 +00:00

leap-upgrades

Better handling for resuming leapfrog upgrade

2018-12-12 17:14:12 -06:00

multi-node-aio

MNAIO: Add ability to deploy Ceph

2018-11-27 15:51:46 +00:00

osa-gate-profile

Import osa-gate-profile

2016-11-07 08:19:06 -06:00

osquery

Fix ansible path for elk_metrics_6x tests

2018-11-08 09:45:30 -06:00

prometheus

Add Prometheus node_exporter

2018-08-13 10:17:03 +02:00

pxelinux-provisioning

Pin get-pip.py to 3.2

2018-07-05 07:56:21 -04:00

releasenotes

Update reno for stable/rocky

2018-08-10 16:45:39 +00:00

scripts

update ironic scripts

2018-09-11 10:34:39 -06:00

tests

Remove tests-repo-clone.sh

2018-03-28 10:28:54 +01:00

zuul.d

Remove non-existant 'functional' test

2018-11-28 16:44:28 +00:00

.gitignore

Updated from OpenStack Ansible Tests

2018-10-02 14:51:42 +00:00

.gitreview

Added .gitreview

2016-05-27 11:57:18 +00:00

bindep.txt

Updated from OpenStack Ansible Tests

2017-12-06 00:05:43 +00:00

CONTRIBUTING.rst

Replace Chinese punctuation with English punctuation

2018-09-12 13:09:10 +00:00

LICENSE

Add base test scaffolding for repo

2016-06-14 15:32:40 +00:00

multi-node-aio-xenial-ansible

Combine our two multi-node-aio processes into one

2017-07-28 15:35:23 +00:00

README.rst

Add bugs url link to README

2018-12-04 10:02:13 +00:00

run_tests.sh

Updated from OpenStack Ansible Tests

2018-09-29 04:53:18 +00:00

setup.cfg

Update URLs in documents according to document migration

2017-07-14 13:54:50 +08:00

setup.py

Updated from global requirements

2017-03-02 11:51:26 +00:00

tox.ini

Remove non-existant 'functional' test

2018-11-28 16:44:28 +00:00

README.rst

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:: https://docs.openstack.org/openstack-ansible-ops/latest/
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:: https://launchpad.net/openstack-ansible
The project bug tracker is located at:: https://bugs.launchpad.net/openstack-ansible

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.