Ansible deployment of the Kolla containers
Go to file
Ravi Shekhar Jethani 9c66123c30 Don't change directory while running init-runonce
Currently init-runonce script changes directory to the
script's base directory (/usr/...) before doing anything else.
This unnecessarily _forces_ a non-root user to use sudo for
running this script thereby raising privileges for code which
doesn't want it. Also downloading temporary stuff in places like
/usr... seems not a good choice.

Hence deleting the said code part and letting the deployer work
comfortably from any directory.

Made documentation changes accordingly.

Change-Id: Ib3c7ed97aa5f53c115b6337aaf572b5fdc7a71f3
Closes-Bug: #1732963
2017-11-23 16:35:45 +05:30
ansible Merge "HyperV should not disable tunneling" 2017-11-22 16:24:41 +00:00
contrib Merge "Disable firewall while setup of dev env" 2017-09-19 08:24:40 +00:00
deploy-guide/source fix kolla giturl. 2017-11-02 11:34:53 +08:00
doc/source Don't change directory while running init-runonce 2017-11-23 16:35:45 +05:30
etc/kolla Merge "Move nova-fake config into globals.yml" 2017-10-11 10:51:53 +00:00
kolla_ansible Add missing dot to help string in genpwd.py script 2017-09-14 00:16:19 +02:00
releasenotes Merge "Remove setting of version/release from releasenotes" 2017-11-20 05:51:49 +00:00
specs fix typo 2017-04-11 12:08:19 +00:00
tests Pull image from dockerhub rather than tarballs.o.o site 2017-11-16 15:44:24 +08:00
tools Don't change directory while running init-runonce 2017-11-23 16:35:45 +05:30
.gitignore Remove unnecessary file in .gitignore 2017-02-10 11:45:24 +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
.zuul.yaml Zuul: add file extension to playbook path 2017-10-28 20:01:50 -07: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 Fix quickstart links 2017-09-08 18:28:48 +02:00
requirements.txt Updated from global requirements 2017-11-16 11:07:43 +00:00
setup.cfg Rearrange existing documentation to fit the new standard layout 2017-09-06 17:43:56 +02:00
setup.py Updated from global requirements 2017-03-02 17:44:00 +00:00
test-requirements.txt Updated from global requirements 2017-11-16 11:07:43 +00:00
tox.ini Merge "Remove doc build errors" 2017-07-19 03:24:45 +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 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.