Ansible deployment of the Kolla containers
Go to file
confi-surya dbf754655f Following the new PTI for document build
For compliance with the Project Testing Interface [1]
as described in [2]

[1]
https://governance.openstack.org/tc/reference/project-testing-interface.html
[2]
http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html

doc8 command is dropped from docs tox envs.
So this affect nothing and run in PEP8.

Related-Bug: #1765348

Depends-On: Icc7fe3a8f9716281de88825e9d5b2fd84de3d00a
Change-Id: Idf9a16111479ccc64004eac9508da575822a3df5
2018-05-21 10:51:59 +01:00
ansible Fix missed kolla_action for murano 2018-05-17 06:17:14 +00:00
contrib Merge "Fix the profile missing when run bootstrap.sh" 2018-04-24 07:30:33 +00:00
deploy-guide/source Remove the deprecated "giturl" option 2018-01-15 03:41:21 +00:00
doc Following the new PTI for document build 2018-05-21 10:51:59 +01:00
etc/kolla Apply Glance database migration 2018-05-09 16:29:27 +00:00
kolla_ansible Add missing dot to help string in genpwd.py script 2017-09-14 00:16:19 +02:00
releasenotes Merge "Fix ansible warning" 2018-05-11 04:13:44 +00:00
specs Update the database connection for keystone 2018-04-22 23:22:15 +08:00
tests Apply Glance database migration 2018-05-09 16:29:27 +00:00
tools Fix ansible warning 2018-05-11 02:54:02 +00: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
.zuul.yaml Reinstate testing of changes to requirements.txt 2018-05-09 09:21:58 +01: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 Update lower-constraints to match local requirements 2018-04-12 16:21:57 +05:30
README.rst Update the Blazar link 2018-05-03 13:44:49 +00:00
requirements.txt Updated from global requirements 2018-03-17 08:35:39 +00:00
setup.cfg Following the new PTI for document build 2018-05-21 10:51:59 +01:00
setup.py Updated from global requirements 2017-03-02 17:44:00 +00:00
test-requirements.txt Following the new PTI for document build 2018-05-21 10:51:59 +01:00
tox.ini Following the new PTI for document build 2018-05-21 10:51:59 +01: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 docs.openstack.org.

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.