Bug 618636 – PRD33 - [RFE] Add multiple network gateways to the Host

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 618636 - PRD33 - [RFE] Add multiple network gateways to the Host

Summary:	PRD33 - [RFE] Add multiple network gateways to the Host

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	RFEs (Show other bugs)
Sub Component:
Version:	2.2.2
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.3.0
Assigned To:	Assaf Muller
QA Contact:	Martin Pavlik
Docs Contact:

URL:	http://www.ovirt.org/Features/Multipl...
Whiteboard:	network
Keywords:	FutureFeature

Duplicates:	675760 786052 786053 (view as bug list)
Depends On:	975759 977856 984028 994523
Blocks:	786053 977207 1019470
	Show dependency tree / graph

Reported:	2010-07-27 08:42 EDT by Avi Tal
Modified:	2018-10-27 09:17 EDT (History)
CC List:	19 users (show)

See Also:
Fixed In Version:	3.3.0, IS6
Doc Type:	Release Note
Doc Text:	Users can now define a gateway for each logical network on a host. This feature is beneficial for deployments in which a host has more than one network device. Any traffic that has to be returned to a network outside the host's subnets will be routed back via the device through which the traffic came, instead of the host's default gateway.
Story Points:	---
Clone Of:
Clones:	977207 (view as bug list)
Environment:
Last Closed:	2014-01-21 12:05:46 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	danken: Triaged+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	118583	None	None	None	Never
oVirt gerrit	15207	None	None	None	Never
oVirt gerrit	15335	None	None	None	Never
oVirt gerrit	15528	None	None	None	Never
oVirt gerrit	16461	None	None	None	Never
oVirt gerrit	16552	None	None	None	Never
oVirt gerrit	16629	None	None	None	Never
oVirt gerrit	16692	None	None	None	Never
Red Hat Product Errata	RHSA-2014:0038	normal	SHIPPED_LIVE	Important: Red Hat Enterprise Virtualization Manager 3.3.0 update	2014-01-21 17:03:06 EST

Groups: None (edit)

Description Avi Tal 2010-07-27 08:42:52 EDT

The only GW in the host is used by rhevm network.
We should support adding more GW's according to our network configurations.

Comment 1 Yaniv Kaul 2010-07-27 08:58:09 EDT

(In reply to comment #0)
> The only GW in the host is used by rhevm network.
> We should support adding more GW's according to our network configurations. 

That is - per interface. Each interface will have its own gateway.

Comment 2 Itamar Heim 2010-07-27 09:41:53 EDT

(In reply to comment #1)
> (In reply to comment #0)
> > The only GW in the host is used by rhevm network.
> > We should support adding more GW's according to our network configurations. 
> 
> That is - per interface. Each interface will have its own gateway.    

actually, should the gateway be defined at the logical network level, rather than at per host level?

Comment 3 Yaniv Kaul 2010-07-27 11:31:27 EDT

(In reply to comment #2)
> (In reply to comment #1)
> > (In reply to comment #0)
> > > The only GW in the host is used by rhevm network.
> > > We should support adding more GW's according to our network configurations. 
> > 
> > That is - per interface. Each interface will have its own gateway.    
> 
> actually, should the gateway be defined at the logical network level, rather
> than at per host level?    

Really depends what we do with the data at the logical network level. It seems that today - nothing. It would have been nice, that when a user selects the logical network a NIC is connected to, the information would be automatically copied from the logic network settings. The gateway and netmask for sure, the IP can be partially (based on the netmask).

Comment 7 Robert Allton 2010-08-12 08:31:01 EDT

Maybe the real problem is that when adding a new Logical Network in the RHEV-M GUI, one of the boxes you can fill out is Default Gateway.

Putting an entry in is optional but is causing a lot of confusion. If you enter a value it overrides the Default Gateway currently setup.

So maybe we need to simply remove Default Gateway as an option when adding a new Logical Network?

Comment 8 Simon Grinberg 2011-02-07 15:43:05 EST

*** Bug 675760 has been marked as a duplicate of this bug. ***

Comment 10 Itamar Heim 2013-01-14 10:57:46 EST

simon - can you please explain how this bug and bug 786052 co-exist?

Comment 16 lpeer 2013-05-30 08:24:54 EDT

*** Bug 786052 has been marked as a duplicate of this bug. ***

Comment 17 Sadique Puthen 2013-05-30 08:46:41 EDT

*** Bug 786053 has been marked as a duplicate of this bug. ***

Comment 19 errata-xmlrpc 2014-01-21 12:05:46 EST

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.

http://rhn.redhat.com/errata/RHSA-2014-0038.html

Note You need to log in before you can comment on or make changes to this bug.