Bug 738277

Summary:	[RFE] disabling qpid on clients should be server driven
Product:	[Retired] Beaker	Reporter:	Marian Csontos <mcsontos>
Component:	qpid	Assignee:	Raymond Mancy <rmancy>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	0.7	CC:	ebaak
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-28 02:19:51 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 Marian Csontos 2011-09-14 12:59:54 UTC

== The problem ==

Currently when disabling qpid on server each client with enabled qpid must be configured manually to match server:

> Also if any beaker clients are using it, they will have to disable it
> by adding the following in their config file
>
>   QPID_BUS=False

== Suggested solution ==

This should be "server driven" and qpid-enable-client connected to non-qpid-server should fall back to XML-RPC. (I do not expect XML-RPC would be disabled.)

== How could it work ==

Client will perform initial XML-RPC to get (version, capabilities) from server and will act accordingly - for example disabling QPID.

Also, for qpid-enabled-server the qpid address could be part of the response from the server, so it is not necessary to configure it separately.

User should be still able to disable qpid in config file by adding the original snippet:

> QPID_BUS=False