Ansible deployment of the Kolla containers
Go to file
Paul Bourke e2c43b206e Allow operators to customise pip in kolla-toolbox
Closes-Bug: #1635304

Change-Id: I6535e3240695458ed04c8750fe34e772a3b2ede3
2016-10-21 10:01:05 +01:00
ansible Merge "Update 'addUser' to 'createUser'" 2016-10-20 14:08:20 +00:00
contrib Move demos and dev directory into a new contrib directory 2016-10-14 12:57:49 +02:00
doc dependencies added to build code with pip in QSG 2016-10-18 16:13:26 +05:30
docker Allow operators to customise pip in kolla-toolbox 2016-10-21 10:01:05 +01:00
etc Merge "Support searchlight ansible role" 2016-10-19 18:25:45 +00:00
kolla Merge "Remove default=None when set value in config" 2016-10-19 16:55:11 +00:00
releasenotes Allow operators to customise pip in kolla-toolbox 2016-10-21 10:01:05 +01:00
specs Delete the unnecessary space 2016-10-15 04:07:29 +00:00
tests Support Searchlight Docker container 2016-10-19 00:49:46 +00:00
tools Merge "Use xenial repos for Ubuntu in the gate" 2016-10-20 10:58:38 +00:00
.gitignore Fix the prechecks for the ansible version 2016-06-09 07:04:13 +08:00
.gitreview Update .gitreview for project rename 2015-09-11 20:57:54 +00:00
.testr.conf Merge "Revert "Capture the log in default"" 2016-01-19 15:36:52 +00:00
bindep.txt Add more packages in bindep.txt 2016-09-23 07:06:02 +00:00
LICENSE Add ASL license 2014-09-20 17:29:35 -07:00
README.rst Support searchlight ansible role 2016-10-19 05:57:53 +00:00
requirements.txt Merge "Move graphviz dependency to test stage" 2016-10-19 12:20:46 +00:00
setup.cfg Added missing cleanup-images in setup.cfg 2016-10-10 14:11:17 -07:00
setup.py Updated from global requirements 2016-05-03 15:58:36 +00:00
test-requirements.txt Merge "Updated from global requirements" 2016-10-19 13:02:59 +00:00
tox.ini Add validate no new line at end of file 2016-10-19 17:17:06 +00:00

Kolla Overview

The Kolla project is a member of the OpenStack Big Tent Governance.

Kolla's mission statement is:

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

Kolla provides Docker containers and Ansible playbooks to meet Kolla's mission.

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 by reading the documentation online docs.openstack.org.

Get started by reading the Developer Quickstart.

Docker images

The Docker images are built by the Kolla project maintainers. A detailed process for contributing to the images can be found in the image building guide.

The Kolla developers build images in the kolla namespace for every tagged release and implement an Ansible roles for many but not all of them.

You can view the available images on Docker Hub or with the Docker CLI:

$ sudo docker search kolla

OpenStack services

Kolla provides images to deploy the following OpenStack projects:

Infrastructure components

Kolla provides images to deploy the following infrastructure components:

Directories

  • ansible - Contains Ansible playbooks to deploy Kolla in Docker containers.
  • contrib - Contains demos scenarios for Heat and Murano and a development environment for Vagrant
  • doc - Contains documentation.
  • docker - Contains jinja2 templates for the docker build system.
  • 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.
  • tests - Contains functional testing tools.
  • tools - Contains tools for interacting with Kolla.
  • specs - Contains the Kolla communities key arguments about architectural shifts in the code base.

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.