7f3cab65f0
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 |
||
---|---|---|
ansible | ||
contrib | ||
deploy-guide/source | ||
doc | ||
etc/kolla | ||
kolla_ansible | ||
releasenotes | ||
specs | ||
tests | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
bindep.txt | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
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:
- Aodh
- Barbican
- Bifrost
- Ceilometer
- Cinder
- CloudKitty
- Congress
- Designate
- Freezer
- Glance
- Gnocchi
- Heat
- Horizon
- Ironic
- Karbor
- Keystone
- Kuryr
- Magnum
- Manila
- Mistral
- Murano
- Neutron
- Nova
- Octavia
- Panko
- Rally
- Sahara
- Searchlight
- Senlin
- Solum
- Swift
- Tacker
- Tempest
- Trove
- Vmtp
- Watcher
- Zaqar
- Zun
Infrastructure components
Kolla-Ansible deploys containers for the following infrastructure components:
- Ceph implementation for Cinder, Glance and Nova
- collectd, InfluxDB, and Grafana for performance monitoring.
- Elasticsearch and
-
Kibana to search, analyze, and visualize log messages.
- Fluentd as an open source data collector for unified logging layer.
- HAProxy and Keepalived for high availability of services and their endpoints.
- Kafka A distributed streaming platform.
- MariaDB and Galera Cluster for highly available MySQL databases
- MongoDB as a database backend for Ceilometer and Gnocchi
- Open vSwitch and Linuxbridge backends for Neutron
- RabbitMQ as a messaging backend for communication between services.
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 Vagrantdoc
- 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.