Bug 1389718

Summary:	[networking_public_157] oadm router command should support VxLAN related options
Product:	OpenShift Container Platform	Reporter:	Hongan Li <hongli>
Component:	Networking	Assignee:	Rajat Chopra <rchopra>
Networking sub component:	router	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	low
Priority:	low	CC:	aos-bugs, bbennett, bmeng
Version:	3.4.0	Keywords:	Reopened
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 18:41:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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