Ansible deployment of the Kolla containers
Go to file
Ryan Hallisey 67333e4dd1 Set db connection retry to infinity
Make sure that all the sevices will attempt to
connect to the database an infinite about of times.
If the database ever disappears for some reason we
want the services to try and reconnect more than just
10 times.

Closes-bug: #1505636
Change-Id: I77abbf72ce5bfd68faa451bb9a72bd2544963f4b
2016-04-11 07:22:09 -04:00
ansible Set db connection retry to infinity 2016-04-11 07:22:09 -04:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Merge "Use packaged pip instead of easy_install" 2016-03-28 05:00:24 +00:00
doc Update vagrant-dev-env.rst 2016-04-08 10:46:21 +05:30
docker Fix the qemu has nova permission in nova instances folder 2016-04-08 15:53:28 -04:00
etc Implement nova-ssh container 2016-04-03 07:21:17 +00:00
kolla Log the SHA of the Git ref for source builds 2016-04-05 13:31:03 +00:00
releasenotes Add reno support 2016-03-23 11:59:35 -07:00
specs Spec: Deploy Kolla images using Kubernetes 2016-04-08 00:20:00 +00:00
tests Add Ubuntu binary build and deploy gate 2016-04-02 16:02:58 +00:00
tools Add default flavors during init-runonce 2016-04-08 10:32:57 -04:00
.gitignore Add reno support 2016-03-23 11:59:35 -07: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 Update README for heka image 2016-03-17 13:33:25 +00:00
requirements.txt Updated from global requirements 2016-04-08 00:10:41 +00:00
setup.cfg Add reno support 2016-03-23 11:59:35 -07:00
setup.py Updated from global requirements 2015-11-13 17:11:37 +00:00
test-requirements.txt Updated from global requirements 2016-04-08 00:10:41 +00:00
tox.ini Add Ubuntu binary build and deploy gate 2016-04-02 16:02:58 +00: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 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

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.