+++ This bug was initially created as a clone of Bug #1269990 +++ Description of problem: Manila supports being deployed with multiple back ends. However, there seems to be no support for this in Director/TripleO. This expectation is for manila to be on par with current support for configuring multiple cinder back ends: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/custom_block_storage_back_end_deployment_guide/index We need to test deploying multiple manila back ends with the help of the ControllerExtraConfig; and write up documentation if that works. We might need code fixes in tripleo like that for cinder here: https://review.openstack.org/#/c/269534/ Version-Release number of selected component (if applicable): 16 How reproducible: Steps to Reproduce: 1. Attempt to setup multiple manila backends with ControllerExtraConfig as documented in the cinder custom backend configuration documentation linked above. We can attempt this with homogenous or hetergenous backends. Actual results: Expected results: manila service-list shows a separate manila-share process for each backend used in the deployment.