aboutsummaryrefslogtreecommitdiff
path: root/ansible
diff options
context:
space:
mode:
authorPaul Bourke <paul.bourke@oracle.com>2015-11-16 17:53:46 +0000
committerPaul Bourke <paul.bourke@oracle.com>2015-11-17 09:42:39 +0000
commit988c4f23f10b8c844c8a8123187391ab992d1fa7 (patch)
tree79d7b390710f3414f0c355f466f714a202ef8b3d /ansible
parentac0442a880bb440f7955b548740215617ea23f22 (diff)
downloadkolla-988c4f23f10b8c844c8a8123187391ab992d1fa7.tar.gz
kolla-988c4f23f10b8c844c8a8123187391ab992d1fa7.zip
Fix issues in Glance filesystem backend
The drop root change for Glance highlighted the fact that we were binding volumes from glance_data into the wrong container - it was glance_registry whereas it should be glance_api. This would result in all images being lost if the glance_api container happens to restart. Also, we need a sudoers file to chown the file backend dir to the glance user. Change-Id: If04337045bb94b3126e48d1f5bf0ea29e20373ae Closes-Bug: #1516729
Diffstat (limited to 'ansible')
-rw-r--r--ansible/roles/glance/tasks/start.yml4
1 files changed, 2 insertions, 2 deletions
diff --git a/ansible/roles/glance/tasks/start.yml b/ansible/roles/glance/tasks/start.yml
index a28e3f3b1..80be58c2b 100644
--- a/ansible/roles/glance/tasks/start.yml
+++ b/ansible/roles/glance/tasks/start.yml
@@ -16,8 +16,6 @@
volumes:
- "{{ node_config_directory }}/glance-registry/:{{ container_config_directory }}/:ro"
- "/var/lib/kolla/dev/log:/dev/log"
- volumes_from:
- - glance_data
env:
KOLLA_CONFIG_STRATEGY: "{{ config_strategy }}"
when: inventory_hostname in groups['glance-registry']
@@ -39,6 +37,8 @@
volumes:
- "{{ node_config_directory }}/glance-api/:{{ container_config_directory }}/:ro"
- "/var/lib/kolla/dev/log:/dev/log"
+ volumes_from:
+ - glance_data
env:
KOLLA_CONFIG_STRATEGY: "{{ config_strategy }}"
when: inventory_hostname in groups['glance-api']