openstack/kolla
Code Issues Proposed changes
Kolla provides production-ready containers and deployment tools for operating OpenStack clouds
1,991 Commits 7 Branches 100 Tags 206 MiB
Python 47.6%
Jinja 35.7%
Shell 16.7%
2eb16d2f0a
Go to file
Michal Jastrzebski 2eb16d2f0a Add ceph and ironic to index 
Adding link to missing guides to our docs index page.

TrivialFix

Change-Id: I6704a59ef7e010d5ffec762325bd4442362a093c
2015-10-11 10:38:02 +02:00
ansible Merge "Swift JSON files looking for rings in the wrong place" 2015-10-09 17:59:25 +00:00
demos Extension .md is changed to .rst 2015-08-24 22:14:22 +05:30
dev Fix path of synced_folder in Vagrantfile 2015-10-09 09:50:08 +02:00
doc Add ceph and ironic to index 2015-10-11 10:38:02 +02:00
docker Remove an oslo.message 2.2.0 pin 2015-10-07 22:20:28 -07:00
etc/kolla Fix wrong option name in kolla-build.conf 2015-09-30 21:51:59 +09:00
kolla add "--template-only" flag for tools/build.py 2015-10-05 14:57:29 +08:00
specs Update ha guide kolla repo reference 2015-09-14 07:19:55 +00:00
tests Add Ansible support for Ironic 2015-09-28 16:10:43 -04:00
tools put conatiner name to array in cleanup-containers 2015-10-06 13:55:58 +08:00
.gitignore Add .vagrant dir to .gitignore 2015-09-22 14:24:21 +01: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 Add a LOC counter 2015-10-07 23:02:59 -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 Add venv section in tox.ini 2015-09-03 00:16:01 +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.