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
Éric Lemoine d2aa9aa6a3 Logging with Heka spec
This adds a spec for using Heka as Kolla's log processing tool.

Change-Id: Ia786601f3f0b298c120950e2abdd6d1b71e32ba5
7 years ago
ansible Merge "Add missing ceph-rgw group for sample multinode inventory" 7 years ago
demos Extension .md is changed to .rst 8 years ago
dev Adapt openrc file to use keystone v3 7 years ago
doc Update the document to use kolla-ansible post-deploy 8 years ago
docker Merge "Fix permissions to /var/lib/nova/" 7 years ago
etc Fix typos in docstrings: 8 years ago
kolla Merge "Import modules rather than objects" 7 years ago
specs Logging with Heka spec 7 years ago
tests Merge "add unittest code base" 7 years ago
tools refactor the cleanup containers 7 years ago
.gitignore Standardize bashate and add linters 8 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 Added Mistral doc link in README.rst 8 years ago
loc Fix up loc with change to devenv 8 years ago
requirements.txt Updated from global requirements 8 years ago
setup.cfg Generate the kolla-build.conf file using oslo_config 8 years ago
setup.py Updated from global requirements 8 years ago
test-requirements.txt Updated from global requirements 7 years ago
tox.ini Merge "Add validate scrits to linters" 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

The learn about Kolla, you can find the documentation online on docs.openstack.org.

You can 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 Ansible deployment for 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.