Ansible deployment of the Kolla containers
Go to file
Javier Castillo Alcíbar b13c40f586 Make sure ceilometer/service_credentials wotks with internalURL
When configuring kolla with

 - kolla_enable_tls_external: "yes"

ceilometer service credential defaults to publicURL.

Ceilometer should work with the internal interface (v3 API Identity syntax):

.....
[service_credentials]
interface = internal
.....

Change-Id: I898ffb2b901f08b810756d80dbb988d8c9298219
Closes-Bug: #1643860
2016-11-22 16:21:48 +01:00
ansible Make sure ceilometer/service_credentials wotks with internalURL 2016-11-22 16:21:48 +01:00
contrib Merge "Fix broken test in vagrant boostrap script" 2016-11-06 06:00:37 +00:00
doc Merge "change docker.server to docker.service in kuryr-guide.rst" 2016-11-11 07:11:16 +00:00
docker Merge "Wait the wsrep_ready to be ON in mariadb" 2016-11-11 17:09:34 +00:00
etc Remove Fedora support 2016-11-03 10:50:22 +01:00
kolla Merge "Show the rendered docker file" 2016-11-11 17:03:42 +00:00
releasenotes Remove non-existent branches in releasenote 2016-11-18 00:00:58 +08:00
specs Delete the unnecessary space 2016-10-15 04:07:29 +00:00
tests Merge "Corrects typo "requried" in kolla_docker.py" 2016-11-10 06:21:51 +00:00
tools Use tox to build gate images 2016-11-21 11:27:07 +00:00
.gitignore Fix the prechecks for the ansible version 2016-06-09 07:04:13 +08:00
.gitreview Set up .gitreview 2016-11-15 20:02:38 +01:00
.testr.conf Merge "Revert "Capture the log in default"" 2016-01-19 15:36:52 +00:00
bindep.txt Make Ubuntu gate work 2016-11-03 16:07:47 +00:00
LICENSE Add ASL license 2014-09-20 17:29:35 -07:00
README.rst Merge "Add support freezer on README.rst" 2016-11-10 08:31:05 +00:00
requirements.txt Updated from global requirements 2016-11-10 10:15:50 +00:00
setup.cfg Set the license field in pip 2016-11-02 04:51:13 -07:00
setup.py Updated from global requirements 2016-05-03 15:58:36 +00:00
test-requirements.txt Updated from global requirements 2016-11-02 21:54:15 +00:00
tox.ini Merge "fix ci gate" 2016-11-22 11:43:36 +00:00

Kolla Overview

The Kolla project is a member of the OpenStack Big Tent Governance.

Kolla's mission statement is:

To provide 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

Learn about Kolla by reading the documentation online docs.openstack.org.

Get started by reading the Developer Quickstart.

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.

The Kolla developers build images in the kolla namespace for every tagged release and implement an Ansible roles for many but not all of them.

You can view the available images on Docker Hub or with the Docker CLI:

$ sudo docker search kolla

OpenStack services

Kolla provides images to deploy the following OpenStack projects:

Infrastructure components

Kolla provides images to deploy the following infrastructure components:

Directories

  • ansible - Contains Ansible playbooks to deploy Kolla in Docker containers.
  • contrib - Contains demos scenarios for Heat and Murano and a development environment for Vagrant
  • doc - Contains documentation.
  • docker - Contains jinja2 templates for the docker build system.
  • 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.
  • tests - Contains functional testing tools.
  • tools - Contains tools for interacting with Kolla.
  • specs - Contains the Kolla communities key arguments about architectural shifts in the code base.

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 #openstack-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.