Bug 1003951

Summary:	impl_qpid changes to allow use of qpid federation
Product:	Red Hat OpenStack	Reporter:	Russell Bryant <rbryant>
Component:	openstack-heat	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:	Ami Jeain <ajeain>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.0	CC:	hateya, ndipanov, sbaker, sdake, shardy, yeylon
Target Milestone:	ga	Keywords:	MoveUpstream
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1003937	Environment:
Last Closed:	2013-11-11 22:39:26 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:	1003937
Bug Blocks:	1003938, 1003942, 1003946

Description Russell Bryant 2013-09-03 14:47:09 UTC

+++ This bug was initially created as a clone of Bug #1003937 +++

A patch was recently merged upstream to the impl_qpid rpc driver to allow the use of qpid federation.  It also completes the fix for leaking qpid exchanges.  Lastly, it includes a couple of additional options to allow durable and auto-delete for queues to be configurable.  Pulling in these options make for a cleaner backport.

The commits from oslo-incubator are:

76972e2 Support a new qpid topology
5ff534d Add config for amqp durable/auto_delete queues


These changes should be backported for RHOS 3.0.z.

Comment 1 Steve Baker 2013-11-11 22:17:49 UTC

In heat the oslo-incubator sync commit is:
7f1c6e9 Sync rpc from oslo-incubator

According to the attached Launchpad bug this fix was released in heat 2013.2.

It has not yet been backported to RHOS 3.0.z

Comment 2 Steven Dake 2013-11-11 22:25:25 UTC

heat 2013.1.3 was rebased in Bug #993092
heat 2013.1.4 was rebased in Bug #1021638

Are you not seeing in the zstream?

Comment 3 Steven Dake 2013-11-11 22:33:23 UTC

NM, 2013.1.4 was Grizzly - 2013.2 (Havana) shouldn't be rebased in a zstream.

The correct course of action is to backport those changes to stable/grizzly and release a 2013.1.5 rebase in RHOS3.0.z.

Comment 4 Steven Dake 2013-11-11 22:36:12 UTC

Ignore Comment #3.  After looking at the activity of the other bugs in Blocks, looks like we are moving this to RHOS4.0.