94f3ce0c78
By default ha-promote-on-shutdown=when-synced. However we are seeing issues with RabbitMQ automatically recovering when nodes are restarted. https://www.rabbitmq.com/ha.html#cluster-shutdown Rather than waiting for operator interventions, it is better we allow recovery to happen, even if that means we may loose some messages. A few failed and timed out operations is better than a totaly broken cloud. This is achieved using ha-promote-on-shutdown=always. Note, when a node failure is detected, this is already the default behaviour from 3.7.5 onwards: https://www.rabbitmq.com/ha.html#promoting-unsynchronised-mirrors This patch adds the option to change the ha-promote-on-shutdown definition, using the flag `rabbitmq_ha_promote_on_shutdown`. This value is unset by default to avoid any unexpected changes to the RabbitMQ definitions.json file, as that would trigger an unexpected restart of RabbitMQ during the next deploy. Related-Bug: #1954925 Change-Id: I2146bda2c72ddac2c9923c6941b0596395fd9ab5 |
||
|---|---|---|
| ansible | ||
| contrib | ||
| deploy-guide/source | ||
| doc | ||
| etc/kolla | ||
| kolla_ansible | ||
| releasenotes | ||
| roles | ||
| specs | ||
| tests | ||
| tools | ||
| zuul.d | ||
| .ansible-lint | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .yamllint | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| lint-requirements.txt | ||
| README.rst | ||
| requirements.txt | ||
| requirements.yml | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Kolla Ansible
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 Kolla Ansible.
Get started by reading the Developer Quickstart.
OpenStack services
Kolla Ansible deploys containers for the following OpenStack projects:
- Aodh
- Barbican
- Bifrost
- Blazar
- Ceilometer
- Cinder
- CloudKitty
- Cyborg
- Designate
- Freezer
- Glance
- Heat
- Horizon
- Ironic
- Keystone
- Kuryr
- Magnum
- Manila
- Masakari
- Mistral
- Murano
- Neutron
- Nova
- Octavia
- Sahara
- Senlin
- Solum
- Swift
- Tacker
- Trove
- Vitrage
- Watcher
- Zun
Infrastructure components
Kolla Ansible deploys containers for the following infrastructure components:
- Collectd, Telegraf, InfluxDB, Prometheus, and Grafana for performance monitoring.
- OpenSearch and OpenSearch Dashboards to search, analyze, and visualize log messages.
- Etcd a distributed reliable key-value store.
- Fluentd as an open source data collector for unified logging layer.
- Gnocchi A time-series storage database.
- HAProxy and Keepalived for high availability of services and their endpoints.
- MariaDB and Galera Cluster for highly available MySQL databases.
- Memcached a distributed memory object caching system.
- Open vSwitch for use with Neutron.
- RabbitMQ as a messaging backend for communication between services.
- Redis an in-memory data structure store.
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 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.kolla_ansible- Contains password generation script.releasenotes- Contains releasenote of all features added in Kolla Ansible.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.zuul.d- Contains project gate job definitions.
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.