Bug 1701074

Summary:	[RFE] support for multiple manila heterogeneous back ends for a single deployment
Product:	Red Hat OpenStack	Reporter:	Goutham Pacha Ravi <gouthamr>
Component:	openstack-tripleo-heat-templates	Assignee:	Goutham Pacha Ravi <gouthamr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	vhariria
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.0 (Train)	CC:	astillma, gcharot, gfidente, lmarsh, nlevinki, rdiwakar, scohen, shrjoshi, spower, tbarron, varosim, vhariria, vimartin
Target Milestone:	Alpha	Keywords:	FutureFeature, TestOnly, Triaged
Target Release:	16.2 (Train on RHEL 8.4)	Flags:	rdiwakar: needinfo-
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.3.2-0.20200211065545.d3d6dc3.el8ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1269990	Environment:
Last Closed:	2021-09-22 10:08:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Goutham Pacha Ravi 2019-04-18 00:10:27 UTC

+++ 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.