9c5e708fe2
Libvirt requires pid_mode to Host to operate on Fedora Hosts. Further we will need this for libvirt upgrade. I am not entirely sure why libvirt running with pid=host gets things working, but it definately has something to do with CentOS's libvirt's integration with systemd. Nailing down the problem, the interface to the Docker module accepts only None or "host". There is no way to generate a None type except with !!null in yml, but this does not work in the jinja2 parser. As a result, one solution is this conditional. A better long term solution would be for the Docker module to take some other argument to indicate None that can be expressed in a string. Change-Id: I54eb87e8ce8679bbf12f671527280c73e195b2e4 Closes-Bug: #1473270
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.