Ansible deployment of the Kolla containers
Go to file
Eduardo Gonzalez 9b05c94266 Split zuul.yaml into multiple files
With the current increase of zuul jobs and
service testing, is easier to maintain and
control what changes are done in different files.

Ideally jobs.yaml would be split into multiple files,
in example per distro, install type, aio or multinode,
etc

Change-Id: I78d3f1f00f96ef3042e94bba6b19e61d7fff4203
2018-08-07 23:06:52 +02:00
ansible Merge "Stabilise Bifrost CI job" 2018-08-07 11:29:03 +00:00
contrib Update tacker CLI to openstack CLI in tacker demo 2018-07-24 07:02:48 +00:00
deploy-guide/source Remove the deprecated "giturl" option 2018-01-15 03:41:21 +00:00
doc Merge "Added kolla_inspector_extra_kernel_options" 2018-08-04 10:40:29 +00:00
etc/kolla Added kolla_inspector_extra_kernel_options 2018-08-03 10:14:09 +01:00
kolla_ansible Use fernet for barbican crypto key 2018-07-26 22:01:30 +02:00
releasenotes Added kolla_inspector_extra_kernel_options 2018-08-03 10:14:09 +01:00
specs Update the database connection for keystone 2018-04-22 23:22:15 +08:00
tests Merge "Apply Resource Constraints to Openstack Services" 2018-07-26 14:18:34 +00:00
tools Fix the name of the CI log for reconfigure 2018-08-02 15:59:39 +01:00
zuul.d Split zuul.yaml into multiple files 2018-08-07 23:06:52 +02:00
.gitignore gitignore: Update path to vagrant environment dir 2017-12-19 13:26:55 +01: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
.yamllint Verify YAML syntax in gates 2018-03-26 17:56:22 +02: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
lower-constraints.txt Drop python-cinderclient usage 2018-06-25 16:19:47 +00:00
README.rst Fix the MongoDB description 2018-06-10 03:38:20 -04:00
requirements.txt Updated from global requirements 2018-03-17 08:35:39 +00:00
setup.cfg Delete the unused openrc-example 2018-06-09 02:27:17 -04:00
setup.py Updated from global requirements 2017-03-02 17:44:00 +00:00
test-requirements.txt Remove openstackdocstheme from test-requirements.txt file 2018-06-08 18:29:44 +08:00
tox.ini Merge "fix tox python3 overrides" 2018-07-15 12:07:12 +00:00

Team and repository tags

image

Kolla-Ansible Overview

The Kolla-Ansible is a deliverable project separated from Kolla project.

Kolla-Ansible deploys OpenStack services and infrastructure components in Docker containers.

Kolla's mission statement is:

To provide production-ready containers and deployment tools for operating
OpenStack clouds.

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-Ansible by reading the documentation online Kolla-Ansible.

Get started by reading the Developer Quickstart.

OpenStack services

Kolla-Ansible deploys containers for the following OpenStack projects:

Infrastructure components

Kolla-Ansible deploys containers for the following infrastructure components:

Directories

  • ansible - Contains Ansible playbooks to deploy OpenStack services and infrastructure components in Docker containers.
  • contrib - Contains demos scenarios for Heat, Magnum and Tacker and a development environment for Vagrant
  • doc - Contains documentation.
  • 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.
  • specs - Contains the Kolla-Ansible communities key arguments about architectural shifts in the code base.
  • tests - Contains functional testing tools.
  • tools - Contains tools for interacting with Kolla-Ansible.

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.