Keep existing data for containerized RabbitMQ
authorJiri Stransky <jistr@redhat.com>
Tue, 7 Mar 2017 15:19:19 +0000 (16:19 +0100)
committerJiri Stransky <jistr@redhat.com>
Tue, 14 Mar 2017 13:53:17 +0000 (13:53 +0000)
Use mounts instead of docker volumes to preserve existing data when
moving from baremetal to containerized RabbitMQ.

Change-Id: I8de6610d13d2d878ffba12eb742880eed694eb3e

docker/services/rabbitmq.yaml

index 573ec17..341ec3d 100644 (file)
@@ -90,7 +90,7 @@ outputs:
               - /var/lib/config-data/rabbitmq/:/var/lib/kolla/config_files/src:ro
               - /etc/hosts:/etc/hosts:ro
               - /etc/localtime:/etc/localtime:ro
-              - rabbitmq:/var/lib/rabbitmq/
+              - /var/lib/rabbitmq:/var/lib/rabbitmq
             environment:
               - KOLLA_CONFIG_STRATEGY=COPY_ALWAYS
               - KOLLA_BOOTSTRAP=True
@@ -116,9 +116,14 @@ outputs:
               - /var/lib/config-data/rabbitmq/:/var/lib/kolla/config_files/src:ro
               - /etc/hosts:/etc/hosts:ro
               - /etc/localtime:/etc/localtime:ro
-              - rabbitmq:/var/lib/rabbitmq/
+              - /var/lib/rabbitmq:/var/lib/rabbitmq
             environment:
               - KOLLA_CONFIG_STRATEGY=COPY_ALWAYS
+      host_prep_tasks:
+        - name: create /var/lib/rabbitmq
+          file:
+            path: /var/lib/rabbitmq
+            state: directory
       upgrade_tasks:
         - name: Stop and disable rabbitmq service
           tags: step2