Ansible deployment of the Kolla containers
Go to file
2015-12-31 15:22:25 +00:00
ansible Merge "change libvirt sock group to nova" 2015-12-30 09:02:21 +00:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Update Vagrant's Ubuntu box provisioning script 2015-12-07 10:18:40 -05:00
doc Update to quickstart for CentOS multinode 2015-12-24 16:04:48 -05:00
docker Merge "Neutron ubuntu binary container" 2015-12-31 15:22:25 +00:00
etc/kolla use oslo.config instead of raw argparse.ArgumentParser 2015-12-30 18:53:05 +08:00
kolla Merge "use oslo.config instead of raw argparse.ArgumentParser" 2015-12-31 07:35:05 +00:00
specs Spec: Deploy Kolla images using Mesos 2015-11-16 10:00:13 +10:00
tests Merge "Python 3 deprecated the logger.warn method in favor of warning" 2015-12-31 07:45:06 +00:00
tools Remove ironic containers in the cleanup script 2015-12-14 16:57:04 +01:00
.gitignore Allow to customize vagrant deployment 2015-11-18 22:39:34 +09:00
.gitreview Update .gitreview for project rename 2015-09-11 20:57:54 +00:00
.testr.conf Clean up the image functional test 2015-05-26 15:01:28 -04:00
LICENSE Add ASL license 2014-09-20 17:29:35 -07:00
loc Fix up loc with change to devenv 2015-10-12 09:02:30 -07:00
README.rst Add Aodh and Tempest to the list of provided images 2015-12-03 16:02:49 -05:00
requirements.txt use oslo.config instead of raw argparse.ArgumentParser 2015-12-30 18:53:05 +08:00
setup.cfg Fix version in master 2015-12-27 17:59:31 +00:00
setup.py Updated from global requirements 2015-11-13 17:11:37 +00:00
test-requirements.txt Updated from global requirements 2015-12-18 02:45:53 +00:00
tox.ini make the tox.ini indent uniform 2015-12-31 15:27:26 +08:00

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

Directories

  • 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

Contributors

Check out who's contributing code and contributing reviews.