Martin André 34872c1c2f Allow check_for_* functions to be consumed by wait_for
In order for the `check_for_*` functions to be consumed by `wait_for`,
they should notify of their success but not exit.

As a consequence, the previous behavior is restored by the fail_unless_*
companion functions.

With this change, it is now possible to do:

    wait_for 30 1 check_for_os_service_running keystone

Change-Id: I16ddf8913027030c3ccb5487713d172904508fd6
2015-04-01 16:39:44 +09:00
2014-09-20 17:29:35 -07:00
2014-10-31 10:10:27 -04:00

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
  • compose - contains the docker-compose files defining the container sets
  • 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.

Description
Ansible deployment of the Kolla containers
Readme 181 MiB
Languages
Jinja 46.1%
Python 41.4%
Shell 12.3%
Ruby 0.2%