Ansible deployment of the Kolla containers
Go to file
Travis McPeak cc33c103d4 Adding a few #nosec tags to prepare for Bandit usage
This commit adds a few #nosec tags for non-issues.  I've examined
the code and determined that these don't represent security issues
so we should add a #nosec tag that tells Bandit not to find these
issues in the future.

Closes-Bug: #1577498
Change-Id: Ic37216c08442c700c64118c78cfb46e6cedd237c
2016-05-02 20:58:57 -07:00
ansible Update murano service name 2016-04-28 12:35:16 +01:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Update remaining files for formatting 2016-04-21 12:03:42 +00:00
doc Document custom-repos 2016-04-27 10:48:37 -04:00
docker Merge "Update base dockerfile for formatting" 2016-04-26 22:45:01 +00:00
etc Implement nova-ssh container 2016-04-03 07:21:17 +00:00
kolla Adding a few #nosec tags to prepare for Bandit usage 2016-05-02 20:58:57 -07:00
releasenotes Add reno support 2016-03-23 11:59:35 -07:00
specs Revert "Spec: Deploy Kolla images using Kubernetes" 2016-04-11 10:17:05 +00:00
tests Add Mistral Binary Containers 2016-04-13 17:51:12 +00:00
tools Merge "Add a role to cleanup containers after deployment" 2016-04-27 17:21:46 +00: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
README.rst Update README for heka image 2016-03-17 13:33:25 +00:00
loc Fix up loc with change to devenv 2015-10-12 09:02:30 -07:00
requirements.txt Updated from global requirements 2016-04-14 02:33:41 +00:00
setup.cfg Add a role to cleanup containers after deployment 2016-04-19 10:00:59 -04:00
setup.py Adding a few #nosec tags to prepare for Bandit usage 2016-05-02 20:58:57 -07:00
test-requirements.txt Updated from global requirements 2016-04-14 02:33:41 +00:00
tox.ini Add Ubuntu binary build and deploy gate 2016-04-02 16:02:58 +00:00

README.rst

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.