Kolla provides production-ready containers and deployment tools for operating OpenStack clouds
Go to file
Dave McCowan cc2dde0854 OpenStack Services Should Use keystone_internal_url for auth
Horizon and Neutron mistakenly were using keystone_public_url
for authentication.  This works without error in deployments
when the internal services happen to have access to the
public network, but it is still wrong.  This fails to work
when the internal services can not access the public URLs,
for example when TLS is enabled on the public endppoints.

This patches corrects horizon and neutron to use
keystone_internal_url for auth.

Change-Id: I59b9094364bef375036028ba86a771dabf28c963
Closes-bug: #1625648
2016-10-15 18:50:41 -04:00
ansible OpenStack Services Should Use keystone_internal_url for auth 2016-10-15 18:50:41 -04:00
contrib Move demos and dev directory into a new contrib directory 2016-10-14 12:57:49 +02:00
doc Merge "Update Manila Guide" 2016-10-14 16:43:52 +00:00
docker Merge "ansible: swift: Fix swift-object-expirer restart loop" 2016-10-14 18:08:12 +00:00
etc Add HNAS as Manila backend 2016-10-10 13:23:13 -03:00
kolla Merge "Deprecate Fedora based Docker images" 2016-10-09 08:50:52 +00:00
releasenotes Update reno for stable/newton 2016-10-13 09:28:41 -04:00
specs Fix inconsistencies in git url 2016-08-06 14:21:23 +02:00
tests Changed docker_restart_policy to unless-stopped 2016-09-26 04:32:28 -04:00
tools Merge "Use sudo to create loop device on gate nodes" 2016-10-14 16:14:32 +00:00
.gitignore Fix the prechecks for the ansible version 2016-06-09 07:04:13 +08:00
.gitreview Update .gitreview for project rename 2015-09-11 20:57:54 +00:00
.testr.conf Merge "Revert "Capture the log in default"" 2016-01-19 15:36:52 +00:00
bindep.txt Add more packages in bindep.txt 2016-09-23 07:06:02 +00:00
LICENSE Add ASL license 2014-09-20 17:29:35 -07:00
README.rst Move demos and dev directory into a new contrib directory 2016-10-14 12:57:49 +02:00
requirements.txt Updated from global requirements 2016-10-12 16:26:40 +00:00
setup.cfg Added missing cleanup-images in setup.cfg 2016-10-10 14:11:17 -07:00
setup.py Updated from global requirements 2016-05-03 15:58:36 +00:00
test-requirements.txt Updated from global requirements 2016-10-05 13:30:35 +00:00
tox.ini Merge "Add support to use pdb with tox" 2016-09-22 07:08:58 +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.