Bug 534206 (RHQ-1024)

Summary:	partitioning algorithm should pair agent/server if on same machine
Product:	[Other] RHQ Project	Reporter:	John Mazzitelli <mazz>
Component:	High Availability	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	Keywords:	FutureFeature, Improvement
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
URL:	http://jira.rhq-project.org/browse/RHQ-1024
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 John Mazzitelli 2008-10-24 13:53:00 UTC

If an agent is running on the same box as a server, the  partitioning algorithm should make that server the agent's primary, for the simple fact that the agent won't need to route its traffic outside of that machine's network adapter since both are co-located.

Comment 1 Red Hat Bugzilla 2009-11-10 20:22:06 UTC

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1024

Comment 2 wes hayutin 2010-02-16 17:09:17 UTC

mass add of key word FutureFeature to help track

Comment 3 Corey Welton 2010-08-18 15:02:49 UTC

Per triage, this has been moved to ON_QA with the expectation that is is fixed.  If not, please reopen, otherwise close.

Comment 4 John Mazzitelli 2010-08-31 14:22:34 UTC

This was never fixed.

Comment 5 John Mazzitelli 2010-08-31 14:27:20 UTC

this can easily be "worked around" by using affinity - such that the agent has affinity with the server that is running on the same box.