openstack
/
kolla-ansible
Code Issues Proposed changes
Ansible deployment of the Kolla containers
2,168 Commits 6 Branches 94 Tags 161 MiB
Jinja 46.3%
Python 38.5%
Shell 15%
Ruby 0.2%
Go to file
Steven Dake 6cf5928ff1 Base image changes for drop-root 
The reason we are doing drop root is so that a network exposed
software component (i.e. glance) cannot be used to affect the
immutability of the container which it runs in.  I have tried
several different approaches and this is the only approach which
puts glance in PID=1 while ensuring no files may be written by
the glance process in the container image except for the log files.

Change-Id: Ifd3c8c361b78d0e4791dade3afa6435290407c41
Partially-Implements: blueprint drop-root
 		2015-11-09 11:00:26 -05:00
ansible Merge "Finish implementation of spice" 2015-11-06 21:57:08 +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 Merge "Update Centos7 docker commands" 2015-11-06 11:03:17 +00:00
docker Base image changes for drop-root 2015-11-09 11:00:26 -05:00
etc/kolla Finish implementation of spice 2015-11-06 03:48:07 +00:00
kolla Merge "Make RHEL build properly" 2015-11-06 15:55:43 +00: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 Merge "Few improvements in Kolla tools. Added Ubuntu support." 2015-11-06 12:22:35 +00: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
README.rst fix typo in README.rst 2015-11-05 21:47:33 -08:00
loc Fix up loc with change to devenv 2015-10-12 09:02:30 -07: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 new gate for multinode 2015-11-06 00:46:44 +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 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.