Bug 1430487

Summary:	[RFE] As a deployer, I want to use multiple storage backends for different storage services.
Product:	Red Hat OpenStack	Reporter:	Anandeep Pannu <apannu>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	achernet, apannu, beth.white, jjoyce, jrist, jschluet, mburns, opavlenk, rhel-osp-director-maint, slinaber, tvignaud, ukalifon
Target Milestone:	ga	Keywords:	FutureFeature, Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-7.0.0-0.20170624014919.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 21:11:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1420924, Red Hat1442136, 1469874

Description Anandeep Pannu 2017-03-08 18:18:58 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Jason E. Rist 2017-05-03 14:10:24 UTC

This is dependent on what the storage team provides UI via templates - 

- tripleo-heat-templates
- capabilities map updates

Comment 5 Jiri Tomasek 2017-06-29 09:41:54 UTC

Additional related patches here: https://review.openstack.org/#/q/project:openstack/tripleo-heat-templates+cinder+with+dell

As part of https://bugzilla.redhat.com/show_bug.cgi?id=1386300 and https://bugzilla.redhat.com/show_bug.cgi?id=1422222 work the storage options are added to capabilities-map and then automatically presented via GUI

Comment 14 errata-xmlrpc 2017-12-13 21:11:31 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462