Bug 1117303

Summary:	[RFE] Don't count on vdsm to report the management interface
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Dan Kenigsberg <danken>
Component:	RFEs	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED ERRATA	QA Contact:	Meni Yakove <myakove>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	3.6.0	CC:	bazulay, danken, gklein, iheim, lpeer, masayag, mburman, myakove, nyechiel, rbalakri, yeylon, ykaul
Target Milestone:	ovirt-3.6.0-rc	Keywords:	FutureFeature
Target Release:	3.6.0	Flags:	nyechiel: Triaged+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-09 20:48:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Kenigsberg 2014-07-08 13:15:08 UTC

Description of problem:

During deployment of a new host, Engine needs to know which of the host's interfaces is used to connect to Engine. Currently, this is exposed by the lastClientIface element of getVdsCaps verb. However, this approach is problematic, as we plant to remove the requirement of direct Engine-Vdsm TCP connection, without which, Vdsm cannot compute this element.

Instead, it is suggested that Vdsm would expose the output of `ip get route addr`, so that Engine would be able to guess which on top of which host should it configure the management network. Note that this would only be a guess, as Vdsm may sit behind NAT with no route to Engine. In that case, automatic deployment of the management network would be skipped.

Comment 2 Lior Vernia 2014-10-29 09:56:23 UTC

Moving back to POST as Eliraz also needs to get patches merged for this to work :) Please move to MODIFIED when the entire feature is functioning.

Comment 3 Petr Horáček 2014-10-29 10:15:56 UTC

Ok, thanks for the notice :)

Comment 6 Lior Vernia 2014-12-03 15:59:06 UTC

Due to possible issues with deployments where the engine is behind NAT, we'll try to avoid using the getRoute verb. Dan suggested an interesting solution, in which we'll resolve the hostname (if needed), and look for its IP address among the reported IP addresses of the NICs in getVdsCaps; the one that fits is the "active NIC". This would be quite a small fix, exclusive to the engine side.

Comment 7 Max Kovgan 2015-06-28 14:13:39 UTC

ovirt-3.6.0-3 release

Comment 10 errata-xmlrpc 2016-03-09 20:48:48 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://rhn.redhat.com/errata/RHEA-2016-0376.html