aboutsummaryrefslogtreecommitdiff
path: root/docker/rabbitmq/extend_start.sh
AgeCommit message (Collapse)AuthorFilesLines
2026-07-06Migrate to pyproject.tomlMichal Nasiadka1-26/+0
[tool.setuptools.data-files] does not support recursive directory installation. The old setup.cfg [files] worked because PBR's FilesConfig.expand_globs() used os.walk() to expand docker/*, but this hook is not triggered by the pbr.build PEP-517 backend. Move docker/ into kolla/ and use [tool.setuptools.package-data] instead. Update kolla_worker._get_images_dir() to check the kolla package directory first so both editable and regular installs work. Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2024-08-28Revert "Add support for checking incoming RabbitMQ version"Matt Crees1-5/+0
This reverts commit 36a7cd053d5b13ecc9fad1866f244a733fdd58e5. Reason for revert: feature not needed anymore, see here: https://review.opendev.org/c/openstack/kolla-ansible/+/926146/comment/e593d721_7c48143b/ Change-Id: Ic0f9521c66240f13ff5b7fc94480dbbb76498339
2024-08-12Add support for checking incoming RabbitMQ versionMatt Crees1-0/+5
Will be used to check if the current RabbitMQ version is high enough before upgrading to the new one. Change-Id: Ie133d6efc2e4c00002b8f0724e0183eaab35d1c5
2017-06-15Merge "Make rabbitmq log dir configurable"Jenkins1-4/+7
2017-06-14Make rabbitmq log dir configurablePaul Bourke1-4/+7
Change-Id: I020eb6219f89a310451becde41f6f1c7f54baadd Partial-Bug: #1620374
2017-05-26Remove sudo operations that are no longer necessarySteven Dake1-1/+0
set_configs.py has logic to handle chown of directories. Simplify the codebase by removing these unnessary chowns. Further the chowns cause some forms of NFS backed storage to not work properly. Change-Id: I8df95d06b1010778deb3e2a3065aaab26ed2eb6a Closes-Bug: #1693973
2016-07-14Removing .erlang.cookie before rabbitmq bootstrap recreates itSerguei Bezverkhi1-0/+7
In kolla-kubernetes environment rabbitmq bootstrap process fails when .erlang.cookie already exists, the issue is consistently reproduced when using persistent storage PV/PVC. This PS prevents this type of failure. TrivialFix Change-Id: I3509650b1c11aa45cd5ae2d8eea6523201bfb1de
2016-02-19Make Heka collect RabbitMQ logsÉric Lemoine1-0/+7
Partially implements: blueprint heka Change-Id: I8fd3324daf15e52712591c2b3cbec613d82b73b3
2015-11-12Drop root privileges for rabbitmqRyan Hallisey1-1/+1
Drop root privileges for rabbitmq. Only the rabbitmq user will be able to execute chown of /var/lib/rabbitmq. Change-Id: I546e6b475a8462bfbc75972854e1fee64f96d9cb Partially-Implements: blueprint drop-root
2015-10-06Common start.shSam Yaple1-0/+10
The majority of the start.sh code is identical. This removes that duplicate code while still maintaining the ability to call code in a specific container. The start.sh is moved into /usr/local/bin/kolla_start in the container The extend_start.sh script is called by the kolla_start script at the location /usr/local/bin/kolla_extend_start . It always exists because we create a noop kolla_extend_start in the base directory. We override it with extend_start.sh in a specific image should we need to. Of note, the neutron-agents container is exempt from this new structure due to it being a fat container. Additionally, we fix the inconsistent permissions throughout. 644 for repo files and the scripts are set to 755 via a Docker RUN command to ensure someones local perm change won't break upstream containers. Change-Id: I7da8d19965463ad30ee522a71183e3f092e0d6ad Closes-Bug: #1501295