Kolla provides production-ready containers and deployment tools for operating OpenStack clouds
Go to file
Mauricio Lima a2707ecf00 Move manila-share service to network node
After a research regarding manila-share node,
is required that for the generic driver the
manila-share service should be run on the network node.

As the generic driver is our default driver, so this change is needed.

Closes-Bug: #1639028
Change-Id: I4b73fec4f96e3e2f9c442c8716941bede5dfbc8e
2016-11-07 10:25:17 -03:00
ansible Move manila-share service to network node 2016-11-07 10:25:17 -03:00
contrib Update "=" to "==" in "if" condition 2016-10-22 17:04:13 +08:00
doc Merge "Add guide for Hitachi NAS Platform Driver for Manila" 2016-11-03 14:19:14 +00:00
docker Merge "Remove kuryr-lib in upper-constraints.txt file when install master kuryr" 2016-11-03 13:27:16 +00:00
etc Merge "Support searchlight ansible role" 2016-10-19 18:25:45 +00:00
kolla Merge "Revert "Build source from Newton rather then Master"" 2016-11-02 18:38:44 +00:00
releasenotes Move manila-share service to network node 2016-11-07 10:25:17 -03:00
specs Delete the unnecessary space 2016-10-15 04:07:29 +00:00
tests Support Searchlight Docker container 2016-10-19 00:49:46 +00:00
tools Move precheck into its own role 2016-11-03 14:48:58 +08: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 Support searchlight ansible role 2016-10-19 05:57:53 +00:00
requirements.txt Updated from global requirements 2016-10-27 12:15:09 +00:00
setup.cfg Set the license field in pip 2016-11-02 04:51:13 -07:00
setup.py Updated from global requirements 2016-05-03 15:58:36 +00:00
test-requirements.txt Updated from global requirements 2016-11-02 21:54:15 +00:00
tox.ini Move bandit to pep8 as generic linting target 2016-10-19 20:40:33 +02: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.