Ansible deployment of the Kolla containers
Go to file
Paul Bourke 8006ecdacf Update keystone sanity check to use built in shade
The current module 'kolla_sanity' was written as a shim before full
shade support was added to Ansible. This should now no longer be needed,
we can implement the checks using Ansible provided modules.

Begin by updating the Keystone check to use 'os_auth' to fetch a token,
I think this is a good basic smoke test to verify Keystone is working.

Change-Id: I16049d9201fd8138c781ef2e1e0c1827ea817259
Partially-implements: blueprint sanity-check-container
2017-04-06 11:50:38 +00:00
ansible Update keystone sanity check to use built in shade 2017-04-06 11:50:38 +00:00
contrib Fix Magnum Kolla demo in contrib 2017-03-07 10:51:02 +01:00
deploy-guide/source [deploy-guide] Moving the quick start to the deploy folder 2017-03-28 15:25:16 +00:00
doc Fix the "tox -e docs" failed 2017-04-03 15:53:28 +08:00
etc/kolla Merge "Remove useless variable glance_backend_file" 2017-03-30 15:11:22 +00:00
kolla_ansible Use yaml.safe_dump() instead of yaml.dump() 2017-03-30 16:54:05 +08:00
releasenotes Add zun ansible role 2017-03-30 04:15:17 -04:00
specs change amoung to among 2017-03-01 00:19:31 +07:00
tests Change python interpreter 2017-02-16 13:39:36 -08:00
tools Update the cirros version to "0.3.5" 2017-04-03 16:04:12 +08: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 Merge "Update infra components list in README.rst" 2017-03-27 13:16:34 +00:00
requirements.txt Cleanup requirements.txt file 2017-03-22 16:17:38 +01: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-03-29 18:43:05 +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.