toggle quoted messageShow quoted text
when you say ovsdb suite, does that include the southbound and the netvirt pieces?
Also, have both pieces already been tested with 6634 as the controller ovsdb port? Reason I ask, is there might some hardcoded values in the ovsdb code depending on the use case.
----- Original Message -----
From: "Luis Gomez" <ecelgp@...>
To: "Andrew Grimberg" <agrimberg@...>
Cc: "'integration-dev@...' (integration-dev@...)
<integration-dev@...>, "ovsdb-dev" <ovsdb-dev@...>
Sent: Monday, June 22, 2015 6:36:10 PM
Subject: Re: [ovsdb-dev] [integration-dev] ovsdb server port
So if we want the OVSDB suite to run smooth in a test consolidated
environment (controller + OVS in same VM) we will have to open a different
port (not 6640) for the mininet VM. So I am thinking we can still use the
old port 6634 for the mininet VM.
On Jun 22, 2015, at 3:05 PM, Andrew Grimberg < agrimberg@...
wrote:On Mon, 2015-06-22 at 15:30 -0600, Edward Warnicke wrote:
From the RFC: https://tools.ietf.org/html/rfc7047
"IANA has assigned TCP port 6640 for this protocol. Earlier
implementations of OVSDB used another port number, but compliant
implementations should use the IANA-assigned number.
IANA has updated the reference for port 6640 to point to this
My guess is that it might have been 6634 at some point in the past...
but its 6640 now.
How old is our RHEL?
This is a fallout from the recently built Fedora 21. Yes, we're aware
that F22 is already available but it came out just after we built out
the F21 image. We can modify the port that SELinux allows (it's not
hard), just not what the default SELinux policies allow openvswitch to
If IANA says it should be 6640, I would suggest we use that and just
modify the Jenkins script to add it as an allowed port.
Andrew J Grimberg
The Linux Foundation
ovsdb-dev mailing list