Ansible deployment of the Kolla containers
Go to file
Andrew Widdersheim 879b446398 Fix using rhel as a base build image
Using rhel as a base build image is not a supported option. This seems
to have gotten lost during some code rearchitecture. Also, rename from
redhat to rhel to match the references in the documentation.

Closes-bug: #1625229

Change-Id: If950b20717205dd0e336e6171971e25a9d07df13
2016-09-19 11:18:16 -04:00
ansible Merge "fix config file permission to ironic instead of root" 2016-09-19 14:36:14 +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 corrected error in multinode.rst 2016-09-17 17:02:33 +00:00
docker Merge "Fix ironic Dockerfile" 2016-09-19 14:24:21 +00:00
etc Add Kuryr ansible role 2016-09-15 23:47:22 +00:00
kolla Fix using rhel as a base build image 2016-09-19 11:18:16 -04:00
releasenotes Merge "Enable CADF events in Keystone and introduce enable_cadf_notifications" 2016-09-19 14:23:14 +00:00
specs Fix inconsistencies in git url 2016-08-06 14:21:23 +02:00
tests Revert 'Add neutron-lbaas-agent to exlude image for Ubuntu binary' 2016-09-16 07:43:31 +08:00
tools Merge "Add ara to collect ansible playbook running statics" 2016-09-16 11:56:47 +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 Added Barbican in the list of services deployed by kolla 2016-09-19 16:18:44 +05:30
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 "python-openstackclient" to test-requirements.txt 2016-09-16 11:12:06 +00: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.