openstack/kolla-ansible
Code Issues Proposed changes
Ansible deployment of the Kolla containers
2,146 Commits 5 Branches 106 Tags 175 MiB
Jinja 48.2%
Python 39%
Shell 12.6%
Ruby 0.2%
2405110f3d
Go to file
Martin André 2405110f3d Remove mysql-devel cruft 
This was conflicting with Percona-Server-devel-55 and broke centos
source build for openstack-base image.

Backport: Liberty
Change-Id: Ia2bb2106038e8e2eadb6668f4ae1ad1d95710c09
Closes-Bug: #1513711
2015-11-06 15:07:55 +09:00
ansible Remove vip for rabbitmq 2015-11-05 15:43:20 +00:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Use default disk image size for centos/7 2015-11-02 01:46:19 +00:00
doc Tidy up quickstart.rst 2015-11-05 01:32:33 -07:00
docker Remove mysql-devel cruft 2015-11-06 15:07:55 +09:00
etc/kolla Add Docker in Docker container 2015-11-05 10:58:29 +00:00
kolla Fix RHEL builds 2015-11-04 09:32:08 -05:00
specs Add a template spec to make it a bit easier to write a new spec 2015-11-03 10:30:01 +10:00
tests Restrucutre gate scripts 2015-11-05 10:58:29 +00:00
tools Use kolla_internal_address in the example rc file 2015-10-28 12:50:02 -04:00
.gitignore Update Vagrant directories in .gitignore 2015-10-12 07:46:15 +02:00
.gitreview Update .gitreview for project rename 2015-09-11 20:57:54 +00:00
.testr.conf Clean up the image functional test 2015-05-26 15:01:28 -04: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 Fix documentation links in the README 2015-11-05 13:46:49 -05:00
requirements.txt Add developer docs automatic produce support 2015-08-28 06:11:08 +00:00
setup.cfg Release version 1.0.0 2015-10-06 21:47:48 -07:00
setup.py Make Kolla installable via PIP 2015-08-24 16:08:49 -07:00
test-requirements.txt Add developer docs automatic produce support 2015-08-28 06:11:08 +00:00
tox.ini Restrucutre gate scripts 2015-11-05 10:58:29 +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

The learn about Kolla, you can find the documentation online on docs.openstack.org.

You can 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. Images reside in the Docker Hub Kollaglue repo.

The Kolla developers build images in the kollaglue namespace for the following services for every tagged release and implement Ansible deployment for them:

  • Ceilometer
  • Cinder
  • Glance
  • Haproxy
  • Heat
  • Horizon
  • Keepalived
  • Keystone
  • Mariadb + galera
  • Mongodb
  • Neutron (linuxbridge or neutron)
  • Nova
  • Openvswitch
  • Rabbitmq
$ sudo docker search kollaglue

A list of the upstream built docker images will be shown.

Directories

  • ansible - Contains Anible 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.