openstack/kolla-ansible
Code Issues Proposed changes
Ansible deployment of the Kolla containers
2,096 Commits 5 Branches 106 Tags 175 MiB
Jinja 48.2%
Python 39%
Shell 12.6%
Ruby 0.2%
2492362dd7
Go to file
Steven Dake 2492362dd7 Shorten up title in docs 
Change "kolla's Philosophy on Deployment" to "Kolla's Deplooyment
Philosophy" so it takes up less bytes.

Change-Id: I35d7b91f6b5260878e3a5a45d89b97c74d88cddc
2015-11-02 11:06:14 -07:00
ansible Merge "heat containers depends on 'common' (rsyslog, log_data, kolla-ansible)" 2015-11-02 12:46:54 +00:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Pin Docker version to 1.8.2 2015-10-15 07:51:14 +02:00
doc Shorten up title in docs 2015-11-02 11:06:14 -07:00
docker Use EL7 repostitory instead of EL6 for percona 2015-10-23 02:55:44 -07:00
etc/kolla Add mariadb to the gate 2015-10-23 20:23:24 +00:00
kolla Add build profiles to build.py 2015-10-19 13:31:30 +01:00
specs Update ha guide kolla repo reference 2015-09-14 07:19:55 +00:00
tests Update the super function name 2015-10-23 20:24:02 +00:00
tools Remove memcached container in cleanup-containers tool 2015-10-22 06:47:32 +02: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 Merge "Move around the development environments" 2015-10-08 08:02:04 +00: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 Removed unneeded tox things 2015-10-23 20:24:02 +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

Please get started by reading the Developer Quickstart followed by the Ansible Deployment Guide.

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.