LVM in cinder-volume container without udev
authorJiri Stransky <jistr@redhat.com>
Tue, 27 Jun 2017 13:48:40 +0000 (15:48 +0200)
committerJiri Stransky <jistr@redhat.com>
Tue, 11 Jul 2017 13:05:42 +0000 (15:05 +0200)
Disabling udev usage from LVM seems to be the only observed working
way of running containerized cinder-volume with local LVM backend.

I didn't come across reports that not using udev would have negative
impact on the functionality.

Additional info at
https://groups.google.com/forum/#!topic/docker-user/n4Xtvsb4RAw

Change-Id: I491795deab0c37d1bad3b50524481e0b76529667
Depends-On: I1bf395a6228dba66fa6bf9b8bcc9f3ac3d922a49
Closes-Bug: #1700982

docker/services/cinder-volume.yaml

index 0ce098a..0254e25 100644 (file)
@@ -67,9 +67,15 @@ outputs:
     description: Role data for the Cinder Volume role.
     value:
       service_name: {get_attr: [CinderBase, role_data, service_name]}
-      config_settings: {get_attr: [CinderBase, role_data, config_settings]}
+      config_settings:
+        map_merge:
+          - get_attr: [CinderBase, role_data, config_settings]
+          - tripleo::profile::base::lvm::enable_udev: false
       step_config: &step_config
-        get_attr: [CinderBase, role_data, step_config]
+        list_join:
+          - "\n"
+          - - "include ::tripleo::profile::base::lvm"
+            - get_attr: [CinderBase, role_data, step_config]
       service_config_settings: {get_attr: [CinderBase, role_data, service_config_settings]}
       # BEGIN DOCKER SETTINGS
       puppet_config: