Ansible deployment of the Kolla containers
Go to file
Paul Bourke fecf719e59 Allow operators to use 'fallback mode' for Ceph disks
This change adds a variable to the Ceph role "kolla_ceph_use_udev",
which is True by default meaning no change to the current behaviour. If
set to False, it will fallback to tools such as sgdisk/blkid to parse
the disk info it needs, instead of using udev.

Change-Id: I88d7b73efe27f04bb1ba16d61e101fa14a9f0d81
Depends-On: I6ad7825cdb164498f3d02f2ae064c7c1c38e10d5
Closes-Bug: #1631949
2016-12-20 13:38:33 +00:00
ansible Allow operators to use 'fallback mode' for Ceph disks 2016-12-20 13:38:33 +00:00
contrib Merge "Fix broken test in vagrant boostrap script" 2016-11-06 06:00:37 +00:00
doc Change 'docker' to 'Docker' in docs 2016-12-08 08:07:12 -06:00
etc Merge "Integrate ceph-rgw with keystone" 2016-12-15 14:02:31 +00:00
kolla Fix kolla-genpwd and kolla-mergepwd 2016-12-12 15:10:13 -05:00
releasenotes Allow operators to use 'fallback mode' for Ceph disks 2016-12-20 13:38:33 +00:00
specs Delete the unnecessary space 2016-10-15 04:07:29 +00:00
tests clean up kolla related files 2016-11-30 11:17:35 +08:00
tools Read EXTRA_OPTS from env in kolla-ansible script 2016-12-05 10:25:42 +08:00
.gitignore Add *.egg-info into .gitignore file 2016-12-06 12:30:52 +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 Change 'docker' to 'Docker' in docs 2016-12-08 08:07:12 -06:00
requirements.txt Add PyYAML to requirements.txt, dependency of genpwd 2016-12-15 17:22:31 -05:00
setup.cfg Merge "clean up kolla related files" 2016-12-01 20:52:42 +00:00
setup.py Updated from global requirements 2016-05-03 15:58:36 +00:00
test-requirements.txt Updated from global requirements 2016-12-05 09:39:33 +00:00
tox.ini clean up kolla related files 2016-11-30 11:17:35 +08:00

Team and repository tags

image

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.

Notices

Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.