Ansible deployment of the Kolla containers
Go to file
Wanlong Gao e25c12fee6 ironic-conductor: install ipmitool for source deploy in centos
Change-Id: Ib6b095341c8d63b365d3575478b4dafa69720b63
Closes-Bug: #1534900
2016-01-16 16:19:39 +08:00
ansible Fix wrong integration bridge configuration name in ml2 conf 2016-01-15 12:08:18 -05:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Remove the kolla-build.conf 2016-01-07 21:06:22 +08:00
doc Limit the Ansible version up to <2.0.0 2016-01-15 06:55:52 +08:00
docker ironic-conductor: install ipmitool for source deploy in centos 2016-01-16 16:19:39 +08:00
etc Merge "Remove the kolla-build.conf" 2016-01-08 03:22:18 +00:00
kolla Add trove source url and location 2016-01-09 18:25:03 +08:00
specs Spec: Deploy Kolla images using Mesos 2015-11-16 10:00:13 +10:00
tests Merge "Add some additional debug to gate" 2016-01-13 20:20:34 +00:00
tools Merge "Standardize bashate and add linters" 2016-01-13 22:03:39 +00:00
.gitignore Standardize bashate and add linters 2016-01-13 17:33:28 +00: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 Added Mistral doc link in README.rst 2016-01-12 11:26:39 +09:00
requirements.txt Updated from global requirements 2016-01-07 06:53:10 +00:00
setup.cfg Generate the kolla-build.conf file using oslo_config 2016-01-06 08:11:06 +08:00
setup.py Updated from global requirements 2015-11-13 17:11:37 +00:00
test-requirements.txt Standardize bashate and add linters 2016-01-13 17:33:28 +00:00
tox.ini Put py34 first in the env order of tox 2016-01-14 10:11:24 +05:30

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.