Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1515394 - Allow for the Global VNID 0 for OpenShift Open vSwitch to be modified
Summary: Allow for the Global VNID 0 for OpenShift Open vSwitch to be modified
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Xiaoli Tian
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-20 18:02 UTC by Alfredo Quiroga
Modified: 2019-02-12 19:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Alfredo Quiroga 2017-11-20 18:02:48 UTC
Description of problem:

It seems that the default VNID for Open vSwitch under multi-tenant mode is not something we can change. Currently that value is set to 0. In some cases, it might be necessary to change that. For example, see email I received from a customer:

Kent Munson
10:46 AM (2 hours ago)

to me 
Hey Alfredo,
Hope things are well and you are getting ready for a good Thanksgiving.  I have a quick question is it possible to change the VNID that OCP uses after install?  We have a customer that has a production as well as a test OCP environment and would like to connect them to the same BIG-IP.  The issue is that we can only have one tunnel with VNID 0, I thought if we could change the VNID in their test environment that would solve the problem.
Kent Munson | Solution Architect   
Mobile +1 408-316-5586 |

I looked around and found this:

It seems that the VNID of 0 is hard coded at the moment.

This RFE calls for that value to be configurable, preferably during the installation via Ansible.

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