openstack/kolla-ansible
Code Issues Proposed changes
c3114b9610
kolla-ansible/README.md
Daneyon Hansen e0de6af3ec Implements: blueprint heat-template 
Previously, the kolla heat template was maintained outside of
the project in the larsks/heat-kubernetes repo. This patch adds
the templates to the project's devenv directory. Additionally,
the patch updates the templates and documentation to reflect
the design changes outlined in the following spec:

https://github.com/stackforge/kolla/blob/master/specs/containerize-openstack.rst

Change-Id: I11305f87cceb2495478d458a7e381d20838e664a
2015-02-16 23:41:22 +00:00

2.6 KiB
Raw Blame History

Kolla Overview

The Kolla project is part of the OpenStack TripleO effort, focused on deploying OpenStack services using Docker containers. The initial system spec provides additional details of Kolla and the use cases it addresses.

Getting Started

Deployment on bare metal is a complex topic which is beyond the scope of the project at this time. An environment to simplify the deployment of a single or multi-node Kolla cluster is required for development purposes. As a result, a Heat template has been created for deploying a Kolla cluster to an existing OpenStack cloud.

Docker Images

The Docker images are built by the Kolla project maintainers. A detailed process for contributing to the images can be found here. Images reside in the Docker Hub Kollaglue repo.

The Kolla developers build images in the kollaglue namespace for the following services:

  • Glance
  • Heat
  • Keystone
  • Mariadb
  • Nova
  • Rabbitmq
  • Neutron
  • Mongodb
  • Ceilometer
  • Zaqar
  • Horizon
$ sudo docker search kollaglue

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

Directories

  • docker - contains artifacts for use with docker build to build appropriate images
  • k8s - contains service and pod configuration information for Kubernetes
  • tools - contains different tools for interacting with Kolla
  • devenv - A collection of tools and resources for managing a Kolla development environment.

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 #tripleo irc channel.
  • File bugs, blueprints, track releases, etc on Launchpad.
  • Attend weekly meetings.
  • Contribute code

Contributors

Check out who's contributing.