Skip to content
Snippets Groups Projects
  • Steven Dake's avatar
    ed2f908a
    Remove compose from the repostiory since its dead code · ed2f908a
    Steven Dake authored
    Several people over the liberty cycle committed to maintaining
    compose, but it was never completed.  Rather than carry compose
    in our repoistory until the end of time in a broken state I propose
    removing it.  If someone comes along and wants to resseruct the code
    and make it functional in the future, I'd be 100% open to merge a
    patch in the future which reintroduces this functionality.  In the
    meantime it is confusing to users which ask me on a daily basis if
    compose is supported which I have to go into a 10 minute monologue
    about why its in the repository.
    
    Fortunately git contains full history so we can always revert this
    change at a later time if someone wants to actually fixt his code
    base up and make it useable in some way.  I think the proper answer
    is a seperate repoistory (kolla-compose) which contains any compose
    related bits.
    
    Please consider removing since nobody is using this code and its
    dead.
    
    TrivialFix
    
    backport: liberty
    Change-Id: I8b7c39b00d1967184d363af7db86d1ff8b5e725f
    ed2f908a
    History
    Remove compose from the repostiory since its dead code
    Steven Dake authored
    Several people over the liberty cycle committed to maintaining
    compose, but it was never completed.  Rather than carry compose
    in our repoistory until the end of time in a broken state I propose
    removing it.  If someone comes along and wants to resseruct the code
    and make it functional in the future, I'd be 100% open to merge a
    patch in the future which reintroduces this functionality.  In the
    meantime it is confusing to users which ask me on a daily basis if
    compose is supported which I have to go into a 10 minute monologue
    about why its in the repository.
    
    Fortunately git contains full history so we can always revert this
    change at a later time if someone wants to actually fixt his code
    base up and make it useable in some way.  I think the proper answer
    is a seperate repoistory (kolla-compose) which contains any compose
    related bits.
    
    Please consider removing since nobody is using this code and its
    dead.
    
    TrivialFix
    
    backport: liberty
    Change-Id: I8b7c39b00d1967184d363af7db86d1ff8b5e725f
README.rst 3.28 KiB

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.
  • devenv - Contains an OpenStack-Heat 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.
  • vagrant - Contains a vagrant VirtualBox-based 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 #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.