- Oct 31, 2024
-
-
Matt Crees authored
As version-check.yml is added to deploy.yml, we must make sure the tasks are only run when the rabbitmq container exists. Change-Id: Iaa31bae739110094affb5e402ed9ac40b153ac3d (cherry picked from commit f5ad7829)
-
- Jun 17, 2023
-
-
Mark Goddard authored
Ansible 2.14.3 introduced a change that broke the method used for restarting MariaDB and RabbitMQ serially [1][2]. In I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8 we limited to 2.14.2 to work around this. Ansible upstream claim this behaviour was unintentional, and will not fix it. This change moves to a different approach where we use separate plays with a 'serial' keyword to execute the restart. This change also removes the restriction on the maximum supported version of 2.14.2 on ansible-core - any 2.14 release is now supported. [1] https://github.com/ansible/ansible/commit/65366f663de7d044f42ae6dd53368fd4c1f88b35 [2] https://github.com/ansible/ansible/issues/80848 Depends-On: https://review.opendev.org/c/openstack/kolla/+/884208 Change-Id: I5a12670d07077d24047aaff57ce8d33ccf7156ff
-
- Apr 13, 2023
-
-
Matt Crees authored
With the addition of the variable `om_enable_rabbitmq_high_availability`, this feature in the upgrade task should be brought back. It is also now used in the deploy task. The `ha-all` policy is cleared only when `om_enable_rabbitmq_high_availability` is set to `false`. Change-Id: Ia056aa40e996b1f0fed43c0f672466c7e4a2f547
-
- Apr 12, 2023
-
-
Michal Nasiadka authored
Since RMQ 3.8 we can use rolling upgrade [1]. Depends-On: https://review.opendev.org/c/openstack/kolla/+/872393 [1]: https://www.rabbitmq.com/upgrade.html#rolling-upgrades Change-Id: If6a7c6c12d9226a2406728108b3c87b3485ac55f
-
- Oct 12, 2020
-
-
Radosław Piliszek authored
Config plays do not need to check containers. This avoids skipping tasks during the genconfig action. Ironic and Glance rolling upgrades are handled specially. Swift and Bifrost do not use the handlers at all. Partially-Implements: blueprint performance-improvements Change-Id: I140bf71d62e8f0932c96270d1f08940a5ba4542a
-
- Aug 28, 2020
-
-
Mark Goddard authored
Including tasks has a performance penalty when compared with importing tasks. If the include has a condition associated with it, then the overhead of the include may be lower than the overhead of skipping all imported tasks. For unconditionally included tasks, switching to import_tasks provides a clear benefit. Benchmarking of include vs. import is available at [1]. This change switches from include_tasks to import_tasks where there is no condition applied to the include. [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/include-and-import.md#task-include-and-import Partially-Implements: blueprint performance-improvements Change-Id: Ia45af4a198e422773d9f009c7f7b2e32ce9e3b97
-
- Jul 25, 2018
-
-
Jeffrey Zhang authored
include is marked as deprecated since ansible 2.4[0] [0] https://docs.ansible.com/ansible/2.4/include_module.html#deprecated Co-Authored-By:
confi-surya <singh.surya64mnnit@gmail.com> Change-Id: Ic9d71e1865d1c728890625aeddf424a5734c0a8a
-
- Feb 17, 2017
-
-
caoyuan authored
Change-Id: I14e1619f8fd33be5b0652982131c2a4a4b3e1292 Partially-implements: blueprint better-reconfigure
-
- Jan 06, 2016
-
-
SamYaple authored
Change-Id: I184aabfbbd9fcd0b87080d044b0d286f0deac14c Partially-Implements: blueprint pre-pull-images
-
- Nov 03, 2015
-
-
Sam Yaple authored
Change-Id: I2a9c6fa16444a2142ab77f58d188eda84a2e59fd Partially-Implements: blueprint rabbitmq-clusterer
-
- Sep 09, 2015
-
-
Steven Dake authored
Stagger the start times of the rabbitmq daemon so rabbitmq neither crashes and also properly forms a cluster. This problem exists in the latest rabbitmq 3.5.4 available on rabbitmq.com for download. Change-Id: Iac4186b3c3b586de38467294399c7ed9415244de Closes-Bug: #1490780
-
- Sep 02, 2015
-
-
Sam Yaple authored
Change-Id: I69a5ace61dd621a7fc0354d4deb5e8937505e13e Partial-Bug: #1480496
-
- Jul 30, 2015
-
-
Sam Yaple authored
The original purpose for having an abstract like 'database' rather than the service name of 'mariadb' has been change. Our direction is different and this patch reflects consistent naming throughout Change-Id: I704896191cc5243f9dab2a4cca9120e9dc2ceb2c Closes-Bug: #1478328
-
- Jul 03, 2015
-
-
Sam Yaple authored
Adds initial support for Rabbitmq in Ansible using the CONFIG_EXTERNAL methods. Additionally, this refactors some of the Rabbitmq config script to allow for reuse by CONFIG_EXTERNAL. Partially Implements: blueprint ansible-service Change-Id: I1765548f7e4f1258eb8a49e2a23242955f52655d
-
- Apr 03, 2015
-
-
Sam Yaple authored
Implements the initial structure for variable substitution in ansible. Change-Id: I26d82189273be6ebf941b0ab82efc6bf1eebc53d
-
- Apr 02, 2015
-
-
Sam Yaple authored
This ansible module for docker-compose allows for idempotency. I have submitted a pull request upstream to ansible-modules-extra to include this new module. When/if the module is accepted upstream if can be removed from the local module library. The two playbooks have been updated to use this module. The database data container does not support idempotency due to the fact that it exists instead of sleeps. Therefore each time `docker-compose up` is called, it will start the container and register a change. The message-broker does not have this issue and will remain unchanged even repeatedly running these playbooks. Due to the use of a special branch of docker-compose provided by sdake, this module requires at least docker-compose==1.2.0rc1 Change-Id: If1644eaa3bff0c2a007fa2d479a95bea941945f6
-
- Mar 28, 2015
-
-
Sam Yaple authored
This adds a very basic structure to begin supporting ansible in Kolla. Ansible can support complete idempotency, but wrapping docker-compose does not allow idempotency at this time. These playbooks will be extended to compensate for that in future patches. Change-Id: I1c9e8d32321e2733f5a9b752edf74b4fe90317ed
-