Kolla provides production-ready containers and deployment tools for operating OpenStack clouds
Go to file
Michal (inc0) Jastrzebski 03d86d5f24 Fix mariadb build issue
Change-Id: I12cb9a000f2d90007c1ea55d1ca12ede28c35d6f
Closes-Bug: #1634680
2016-10-18 22:59:28 +00:00
ansible Fix wrong log permission for services collected through syslog 2016-10-18 21:20:46 +00:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev/vagrant Update "which" command to "type" 2016-09-16 11:12:28 +00:00
doc Merge "Clean up TODOs from live documentation" 2016-10-10 03:55:05 +00:00
docker Fix mariadb build issue 2016-10-18 22:59:28 +00:00
etc integrate gnocchi with ceilometer 2016-10-09 03:04:07 +00:00
kolla Merge "Deprecate Fedora based Docker images" 2016-10-09 08:50:52 +00:00
releasenotes Congress doesn't deploy release note 2016-10-18 22:11:51 +00:00
specs Fix inconsistencies in git url 2016-08-06 14:21:23 +02:00
tests Changed docker_restart_policy to unless-stopped 2016-09-26 04:32:28 -04:00
tools Choose node with largest seqno number for mariadb recovery 2016-10-09 12:08:58 +00:00
.gitignore Fix the prechecks for the ansible version 2016-06-09 07:04:13 +08:00
.gitreview Update .gitreview for stable/newton 2016-10-13 09:28:37 -04: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
README.rst Added Barbican in the list of services deployed by kolla 2016-09-19 16:18:44 +05:30
bindep.txt Add more packages in bindep.txt 2016-09-23 07:06:02 +00:00
loc loc fails with recent removal of heat dev env 2016-09-08 08:22:28 -04:00
requirements.txt Add netaddr to requirements file 2016-10-10 13:25:45 +02:00
setup.cfg Added missing cleanup-images in setup.cfg 2016-10-10 14:11:17 -07:00
setup.py Updated from global requirements 2016-05-03 15:58:36 +00:00
test-requirements.txt Updated from global requirements 2016-10-05 13:30:35 +00:00
tox.ini Merge "Add support to use pdb with tox" 2016-09-22 07:08:58 +00:00

README.rst

Kolla Overview

The Kolla project is a member of the OpenStack Big Tent Governance.

Kolla's mission statement is:

To provide 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.

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

OpenStack services

Kolla provides images to deploy the following OpenStack projects:

Infrastructure components

Kolla provides images to deploy the following infrastructure components:

Directories

  • ansible - Contains Ansible playbooks to deploy Kolla in Docker containers.
  • demos - Contains a few demos to use with Kolla.
  • dev/vagrant - Contains a vagrant VirtualBox/Libvirt based development environment.
  • doc - Contains documentation.
  • docker - Contains jinja2 templates for the docker build system.
  • 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.
  • tests - Contains functional testing tools.
  • tools - Contains tools for interacting with Kolla.
  • specs - Contains the Kolla communities key arguments about architectural shifts in the code base.

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.