Bug 1364484 - [RFE] Allow default route to be set from RHEV-M
Summary: [RFE] Allow default route to be set from RHEV-M
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-05 13:24 UTC by Robert McSwain
Modified: 2020-04-15 14:35 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-07 00:10:35 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1200963 0 medium CLOSED [RFE] - Set non-mgmt network as Default Route 2021-09-09 11:42:29 UTC

Internal Links: 1200963

Description Robert McSwain 2016-08-05 13:24:53 UTC
1. Title
       Allow default route to be set from RHEV-M

2. Account information
      [See next comment] 

3. What is the nature and description of the request?  
      Add an option in rhev to change default route from the RHEV-M

4. Why does the customer need this? (List the business requirements here)  
      so that nfs does not mount on 1gb ovirtmgtmt connection

5. How would the customer like to achieve this? (List the functional requirements here)  
      Have an option to set default route in the rhevm interface

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
      Confirm once the option has been added that the proper networking configurations are set in the RHEV-H and can be verified from the Admin Portal of the RHEV-M

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
      No

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
      rhev 4.0

9. Is the sales team involved in this request and do they have any additional input?  
      No

10. List any affected packages or components.  
      RHEV-M

11. Would the customer be able to assist in testing this functionality if implemented?
      Yes

Comment 2 Yaniv Kaul 2016-08-07 05:57:35 UTC
I can only assume it's not just default route (this could be easily done) but routing rules (per interface?).

Comment 3 Dan Kenigsberg 2016-09-13 05:50:49 UTC
Robert, isn't this a dup of Bug 1200963?

Comment 4 Edward Haas 2016-09-26 09:41:38 UTC
VDSM uses a routing table per network, the main table is only relevant for host IP addresses that are not managed by VDSM.
Any IP address that have been set through a network setup, will not pass the main routing table and therefore not affected by the host level default route.

Based on the above, seems to me like it is enough to setup the gateway on the storage network (or create one).

Will this solve the issue?

Comment 6 Edward Haas 2016-11-23 08:20:03 UTC
Please review https://bugzilla.redhat.com/show_bug.cgi?id=1200963 , it treated similar needs when the gateways are not enough.


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