76c5d9a6c8
This is a complete DNS solution, with hidden master and bind9 slave. It lacks the designate-sink service, because there is no true specification to implement that. It listens for Nova/Neutron events and creates records though adding those to just 1 domain isn't helping much in an environment with multiple tenants. Change-Id: I500fb6058b118d25a4ccfd1d3479830c36af7e2a Blueprint: designate-container |
||
---|---|---|
ansible | ||
compose | ||
demos | ||
devenv | ||
docker | ||
docs | ||
specs | ||
tests | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
LICENSE | ||
README.md | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
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.