Ansible deployment of the Kolla containers
Go to file
Graeme Seaton 7f3cab65f0 Set fluentd output to elasticsearch to use elasticsearch_address
Haproxy binds the elasticsearch service to kolla_internal_vip_address but
the output templates for fluentd (td-agent) point to a non-existent
kolla_external_vip_address.

Output should also be able to be sent to an external elasticsearch
instance (as per the documentation regarding overriding
elasticsearch_address)

Change these settings so that fluentd outputs to either
the default elasticsearch_address (i.e. kolla_internal_vip_address) or to
the external elasticsearch instance.

Closes-Bug: #1673990
Change-Id: I081533ae8ea9aad186e9c44e1dee069729931453
2017-03-20 19:31:41 +00:00
ansible Set fluentd output to elasticsearch to use elasticsearch_address 2017-03-20 19:31:41 +00:00
contrib Merge "Fix broken test in vagrant boostrap script" 2016-11-06 06:00:37 +00:00
deploy-guide/source Deployment Guide 2017-03-02 21:44:07 +00:00
doc Merge "Multi-regions Support" 2017-03-16 17:42:07 +00:00
etc/kolla Add neutron-bgp-dragent playbooks and sensible defaults. 2017-03-16 10:03:17 +00:00
kolla_ansible Fix booting from volume failure 2017-03-08 21:16:06 +08:00
releasenotes Merge "Add neutron-bgp-dragent playbooks and sensible defaults." 2017-03-20 10:47:01 +00:00
specs change amoung to among 2017-03-01 00:19:31 +07:00
tests Change python interpreter 2017-02-16 13:39:36 -08:00
tools init-runonce - set image distro to "linux" 2017-03-14 01:20:49 +00:00
.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
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 Merge "Update the README.rst file" 2017-03-18 12:54:06 +00:00
requirements.txt Updated from global requirements 2017-03-14 11:20:00 +00:00
setup.cfg Merge "Remove support for py34" 2017-02-16 03:29:00 +00:00
setup.py Updated from global requirements 2017-03-02 17:44:00 +00:00
test-requirements.txt Updated from global requirements 2017-02-15 20:46:37 +00:00
tox.ini Remove support for py34 2017-02-08 10:06:08 +07: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 and Murano 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.