aboutsummaryrefslogtreecommitdiff
path: root/docker/common/rabbitmq/start.sh
AgeCommit message (Collapse)AuthorFilesLines
2015-08-28Move scripts for rabbitmq to docker_templatesSteven Dake1-23/+0
Change-Id: I6f06c067c18e4a3eafbed2b2796aa1cfe6c9b28c Partially-Implements: blueprint remove-docker-dir
2015-08-09Clean up comment in rabbitmqSteven Dake1-1/+1
Change-Id: I87ff9b8319d29cc41ab7a0fb63025b434fab10f8 Partially-Implements: blueprint remove-config-internal
2015-07-03Ansible Rabbitmq supportSam Yaple1-3/+19
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
2015-06-24RabbitMQ container with HA supportMichal Stachowski1-19/+2
This is new RabbitMQ container with support for HA. It's next step for provide HA support in Kolla project. RabbitMQ is supporting now active/active model and It's ready for active/passive model. Change-Id: I2eb6c65f6268ee96d377e72cf880a01c8042559e Implements: blueprint rabbitmq-ha
2015-06-19Symlink all non Dockerfile resources in imagesPaul Bourke1-0/+24
The only files in the docker image directories that differ majorly between distros are the Dockerfiles (e.g. different package manager mechanisms, different repo sources, etc). The supporting files such as the start.sh/check.sh and config files should largely stay the same between base images. This change moves these files up into a "common" directory, and symlinks them in the same way that the build script is managed. This means when adding a new base distro only new Dockerfiles need to be created. Also, if a distro does happen to require a vastly different start.sh script for example, one can choose to simply not symlink to the common and instead drop in a custom one. Implements: blueprint refactor-base-image-layout Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284