962e48970a
The previous version of crus 6-1 installed pbr hooks. This is incompatible with CentOS RDO. Remove the requirements.txt file from the RPM that is installed. This required placing the files in a new COPRS repository. Since Lars no longer contributes to Kolla, I imported his src rpm, made the necessary adjustments, and created a new COPRS repo for it. The result of the PBR hooks is that any container that ran crux would fail with a distribution error about argparse not being present when it was present. Change-Id: Ibdbccd9e0dd5aeb6d6292bd633b9d2dde8c7b4ce Closes-bug: #1460886
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
- Horizon
- Zaqar
- Magnum
$ 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 #kolla irc channel.
- File bugs, blueprints, track releases, etc on Launchpad.
- Attend weekly meetings.
- Contribute code
Contributors
Check out who's contributing.