Ansible deployment of the Kolla containers
Go to file
Jeffrey Zhang 6710bbeb7c Use dumb-init to manage the pid 1 process
Normally, when you launch a Docker container, the process you're
executing becomes PID 1, giving it the quirks and responsibilities that
come with being the init system for the container.

There are two common issues this presents:

* In most cases, signals won't be handled properly.
* Orphaned zombie processes aren't properly reaped.

the dumb-init acting like a simple init system. It launches a single
process and then proxies all received signals to a session rooted at
that child process.

Closes-Bug: #1614509
Change-Id: I9d3d04648e151ddc7c6732b92ffd3b6c9fe467ec
2016-08-20 17:27:17 +00:00
ansible Merge "Optimize horizon cache and compress for http response" 2016-08-19 15:54:02 +00:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev/vagrant Remove heat dev environment 2016-08-09 15:25:35 +02:00
doc Make tox -e docs work 2016-08-20 09:31:07 -07:00
docker Use dumb-init to manage the pid 1 process 2016-08-20 17:27:17 +00:00
etc Merge "Simplify the Cinder LVM backend" 2016-08-06 18:18:19 +00:00
kolla Pin to Ubuntu 16.04 2016-08-20 22:30:28 +08:00
releasenotes Use dumb-init to manage the pid 1 process 2016-08-20 17:27:17 +00:00
specs Fix inconsistencies in git url 2016-08-06 14:21:23 +02:00
tests Add Dockerfile for congress 2016-08-19 09:29:24 +05:30
tools Fix Ubuntu source gate deployment 2016-08-20 22:28:13 +08: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
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 Fix inconsistencies in git url 2016-08-06 14:21:23 +02:00
requirements.txt Updated from global requirements 2016-08-04 02:36:01 +00:00
setup.cfg Fix Kolla home-page URL 2016-08-18 10:56:50 +08:00
setup.py Updated from global requirements 2016-05-03 15:58:36 +00:00
test-requirements.txt Updated from global requirements 2016-08-19 09:04:45 +00:00
tox.ini Add doc8 test and improve rst syntax 2016-08-04 15:09:10 +02: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

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
  • Heka A distributed and scalable logging system for openstack services.

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 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 kolla

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 #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.