Ansible deployment of the Kolla containers
Go to file
Christian Berendt be0fcb5b99 Integrate neutron-vpnaas-agent into the neutron Ansible role
Implements: blueprint neutron-vpnaas-agent
Co-Authored-By: zhubingbing <zhubingbing10@gmail.com>
Change-Id: I1fae21f48d5beef47934aef7c23910536955f2b8
2016-09-15 05:07:46 +00:00
ansible Integrate neutron-vpnaas-agent into the neutron Ansible role 2016-09-15 05:07:46 +00:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev/vagrant Fix using filter() to meet python2,3 2016-08-29 18:44:44 +08:00
doc Non-default database port documentation. 2016-09-14 15:33:51 +00:00
docker Merge "Add Networking-SFC role" 2016-09-14 20:03:12 +00:00
etc Integrate neutron-vpnaas-agent into the neutron Ansible role 2016-09-15 05:07:46 +00:00
kolla Merge "Add Networking-SFC role" 2016-09-14 20:03:12 +00:00
releasenotes Integrate neutron-vpnaas-agent into the neutron Ansible role 2016-09-15 05:07:46 +00:00
specs Fix inconsistencies in git url 2016-08-06 14:21:23 +02:00
tests Add Networking-SFC role 2016-09-14 15:41:03 +08:00
tools Merge "move ovs cleanup to tools/cleanup-host" 2016-09-13 14:44:26 +00: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
bindep.txt Turn off bindep 2016-09-06 19:45:52 -07:00
LICENSE Add ASL license 2014-09-20 17:29:35 -07:00
loc loc fails with recent removal of heat dev env 2016-09-08 08:22:28 -04:00
README.rst Merge "Improve README file" 2016-09-12 12:02:52 +00:00
requirements.txt Updated from global requirements 2016-09-09 10:19:39 +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 Add extras and pytz>=2013.6 into test requirements 2016-09-14 17:54:22 +08:00
tox.ini Fix bandit gate jobs 2016-08-28 08:52:44 +00:00

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.