Ansible deployment of the Kolla containers
Go to file
Bertrand Lallau 49c083f555 Fix "Enable influxdb datasource" random error
Sometimes the "Enable influxdb datasource" task failed with "503 Service
Unavailable" error. Waiting for grafana port UP seems not always enough,
it requires to wait for application ready.

Change-Id: I3a27b3086698b89a80a3f585beb810831289ae7a
Closes-Bug: #1697213
2017-06-12 10:56:44 +00:00
ansible Fix "Enable influxdb datasource" random error 2017-06-12 10:56:44 +00:00
contrib Merge "Add tacker contrib demo" 2017-06-07 13:20:15 +00:00
deploy-guide/source [deploy-guide] Moving the quick start to the deploy folder 2017-03-28 15:25:16 +00:00
doc vagrant env not working due to libpng-dev and zlib-dev package deprecation 2017-06-07 13:09:44 +05:30
etc/kolla Support OSprofile usage 2017-06-02 22:41:33 +02:00
kolla_ansible Support OSprofile usage 2017-06-02 22:41:33 +02:00
releasenotes Merge "Add release note to deprecate some config files" 2017-06-06 08:17:46 +00:00
specs fix typo 2017-04-11 12:08:19 +00:00
tests Enable multinode gate 2017-06-05 11:35:20 -07:00
tools Merge "Fix unrecognized --limit option" 2017-06-07 13:30:57 +00:00
.gitignore Remove unnecessary file in .gitignore 2017-02-10 11:45:24 +08:00
.gitreview Set up .gitreview 2016-11-15 20:02:38 +01:00
.testr.conf Merge "Revert "Capture the log in default"" 2016-01-19 15:36:52 +00:00
bindep.txt Make Ubuntu gate work 2016-11-03 16:07:47 +00:00
LICENSE Add ASL license 2014-09-20 17:29:35 -07:00
README.rst Stop using old gnocchi reference 2017-06-02 09:41:55 +00:00
requirements.txt Updated from global requirements 2017-06-06 01:49:08 +00:00
setup.cfg Merge "Remove support for py34" 2017-02-16 03:29:00 +00:00
setup.py Updated from global requirements 2017-03-02 17:44:00 +00:00
test-requirements.txt Updated from global requirements 2017-06-06 01:49:08 +00:00
tox.ini Remove support for py34 2017-02-08 10:06:08 +07:00

Team and repository tags

image

Kolla-Ansible Overview

The Kolla-Ansible is a deliverable project separated from Kolla project.

Kolla-Ansible deploys OpenStack services and infrastructure components in Docker containers.

Kolla's mission statement is:

To provide production-ready containers and deployment tools for operating
OpenStack clouds.

Kolla is highly opinionated out of the box, but allows for complete customization. This permits operators with little experience to deploy OpenStack quickly and as experience grows modify the OpenStack configuration to suit the operator's exact requirements.

Getting Started

Learn about Kolla-Ansible by reading the documentation online docs.openstack.org.

Get started by reading the Developer Quickstart.

OpenStack services

Kolla-Ansible deploys containers for the following OpenStack projects:

Infrastructure components

Kolla-Ansible deploys containers for the following infrastructure components:

Directories

  • ansible - Contains Ansible playbooks to deploy OpenStack services and infrastructure components in Docker containers.
  • contrib - Contains demos scenarios for Heat and Murano and a development environment for Vagrant
  • doc - Contains documentation.
  • etc - Contains a reference etc directory structure which requires configuration of a small number of configuration variables to achieve a working All-in-One (AIO) deployment.
  • specs - Contains the Kolla-Ansible communities key arguments about architectural shifts in the code base.
  • tests - Contains functional testing tools.
  • tools - Contains tools for interacting with Kolla-Ansible.

Getting Involved

Need a feature? Find a bug? Let us know! Contributions are much appreciated and should follow the standard Gerrit workflow.

  • We communicate using the #openstack-kolla irc channel.
  • File bugs, blueprints, track releases, etc on Launchpad.
  • Attend weekly meetings.
  • Contribute code.

Contributors

Check out who's contributing code and contributing reviews.

Notices

Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.