Bug 1389718 - [networking_public_157] oadm router command should support VxLAN related options
Summary: [networking_public_157] oadm router command should support VxLAN related options
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Rajat Chopra
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-28 10:07 UTC by Hongan Li
Modified: 2022-08-04 22:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: "oadm router" command should add two options for them: external-host-internal-adress and external-host-vxlan-gw-cidr Reason: To support the vxlan on F5 Result: Implemented
Clone Of:
Environment:
Last Closed: 2017-03-08 18:41:02 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Origin (Github) 11677 0 None None None 2016-11-01 12:50:45 UTC

Description Hongan Li 2016-10-28 10:07:16 UTC
Description of problem:
since f5 router support vxlan in 3.4, so "oadm router" command should add two options for them: external-host-internal-adress and external-host-vxlan-gw-cidr.


Version-Release number of selected component (if applicable):
openshift v3.4.0.16+cc70b72
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0
F5 BIG-IP: 12.1.1.0.0.184


How reproducible:
always

Steps to Reproduce:
1. run "oadm router -h"


Actual results:
cannot find the options: external-host-internal-adress and external-host-vxlan-gw-cidr

Expected results:
"oadm router" should support the new options

Additional info:
currently, we need to create f5 router firstly, then add the options as ENV to enable VxLAN.

Comment 1 Ben Bennett 2016-10-28 13:38:26 UTC
Rajat: is this a reasonable request for the future?

Comment 2 Rajat Chopra 2016-10-31 21:08:17 UTC
Fixed with https://github.com/openshift/origin/pull/11677

Comment 4 Meng Bo 2016-11-07 08:07:41 UTC
The PR has been merged into latest OCP build. Move to ON_QA

Comment 5 Hongan Li 2016-11-07 08:17:04 UTC
Verified in OCP 3.4.0.22 and issue has been fixed.

the added two options works well:
--external-host-internal-ip=x.x.x.x
--external-host-vxlan-gw=x.x.x.x/x


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