Kolla provides production-ready containers and deployment tools for operating OpenStack clouds
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Steven Dake 77a67deeb6 Rename validate-docker-execute with .sh extension

Change-Id: I3ad67fd802f7fe3ed7deb88eddebe520ff410a4f
7 years ago
ansible Merge "Copy the logs out of the container" 7 years ago
demos Extension .md is changed to .rst 8 years ago
dev Simplify logic of vagrantfile 7 years ago
doc Merge "Document how to use loopback devices for Swift" 7 years ago
docker Merge "Fix ubuntu marathon container" 7 years ago
etc Fix default value on globals for config_strategy 7 years ago
kolla Handle kolla-build exception 7 years ago
specs Fixing typo in the documentation 7 years ago
tests Add new gates for oraclelinux 7 years ago
tools Rename validate-docker-execute with .sh extension 7 years ago
.gitignore Added *.DS_Store To .gitignore 7 years ago
.gitreview Update .gitreview for project rename 8 years ago
.testr.conf Merge "Revert "Capture the log in default"" 7 years ago
LICENSE Add ASL license 9 years ago
README.rst Update README for Trove image 7 years ago
loc Fix up loc with change to devenv 8 years ago
requirements.txt Add a new tool to help find the latest versions 7 years ago
setup.cfg Remove unexisting data_files in setup.cfg 7 years ago
setup.py Updated from global requirements 8 years ago
test-requirements.txt Add tox job for the bandit python security linter 7 years ago
tox.ini Add tox job for the bandit python security linter 7 years ago


Kolla Overview

The Kolla project is a member of the OpenStack Big Tent Governance. Kolla's mission statement is:

Kolla provides 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.

Kolla provides images to deploy the following OpenStack projects:

As well as these infrastructure components:

  • Ceph implementation for Cinder, Glance and Nova
  • Openvswitch and Linuxbridge backends for Neutron
  • MongoDB as a database backend for Ceilometer and Gnocchi
  • RabbitMQ as a messaging backend for communication between services.
  • HAProxy and Keepalived for high availability of services and their endpoints.
  • MariaDB and Galera for highly available MySQL databases

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 kollaglue namespace for every tagged release and implement an Ansible deployment for many but not all of them.

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

$ sudo docker search kollaglue


  • ansible - Contains Ansible playbooks to deploy Kolla in Docker containers.
  • demos - Contains a few demos to use with Kolla.
  • dev/heat - Contains an OpenStack-Heat based development environment.
  • dev/vagrant - Contains a vagrant VirtualBox/Libvirt based development environment.
  • 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.
  • docker - Contains jinja2 templates for the docker build system.
  • tools - Contains tools for interacting with Kolla.
  • specs - Contains the Kolla communities key arguments about architectural shifts in the code base.
  • tests - Contains functional testing tools.

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 #kolla irc channel.
  • File bugs, blueprints, track releases, etc on Launchpad.
  • Attend weekly meetings.
  • Contribute code.


Check out who's contributing code and contributing reviews.