Bug 1636179

Summary:	[RFE] Add TripleO support for configuring cinder backend availability zones
Product:	Red Hat OpenStack	Reporter:	Alan Bishop <abishop>
Component:	openstack-tripleo-heat-templates	Assignee:	Alan Bishop <abishop>
Status:	CLOSED ERRATA	QA Contact:	Tzach Shefi <tshefi>
Severity:	medium	Docs Contact:
Priority:	high
Version:	15.0 (Stein)	CC:	abishop, gcharot, gfidente, gregraka, johfulto, lmarsh, mabrams, mburns, pgrist, scohen, tshefi, yrabl
Target Milestone:	Upstream M2	Keywords:	FutureFeature, TechPreview, Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-10.5.1-0.20190509160423.4dac4dc.el8ost	Doc Type:	Technology Preview
Doc Text:	With Red Hat OpenStack Platform director you can now configure different availability zones for Block Storage service (cinder) volume back ends. Director has a new parameter, CinderXXXAvailabilityZone, where XXX is associated with a specific back end.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:19:11 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:
Embargoed:
Bug Depends On:	1688475
Bug Blocks:	1700396

Description Alan Bishop 2018-10-04 16:19:23 UTC

The DCN/Edge architecture requires the ability to configure the cinder-volume service at each Edge site to be in its own availability zone. Cinder already supports this capability, and this RFE is to add TripleO support for configuring it.

Upstream blueprint: https://blueprints.launchpad.net/tripleo/+spec/split-controlplane-cinder-volume-az

Comment 4 Alan Bishop 2018-12-06 13:59:54 UTC

Upstream patches are all merged on stein.

Comment 18 Tzach Shefi 2019-07-17 16:44:15 UTC

Verified on:
openstack-tripleo-heat-templates-10.6.1-0.20190713150434.2871ce0.el8ost.noarch

Passed manual testing no bugs hit during verification.

Comment 24 errata-xmlrpc 2019-09-21 11:19:11 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-2019:2811