Yes. From: Colin Dixon <colin@...> Date: Friday, June 26, 2015 at 9:39 AM To: Thanh Ha <thanh.ha@...> Cc: "sfc-dev@..." <sfc-dev@...>, "<ovsdb-dev@...>" <ovsdb-dev@...>, "release@..."

In that case, can we remove the ovs-sfc directory from the ovsdb project if it's really dead code? --Colin

Ok maybe false alarm. I did a recheck on ovsdb and it was successful despite the the dependencies.log reporting that ovsdb needed sfc. I guess I'm not blocked on this as I had thought. Thanh

SFC definitely uses OVSDB, but I cant imagine why OVSDB would need anything from SFC. OVSDB used to have some implementation code for SFC, but that should have been removed long ago.

Hi Everyone, Just trying to figure out how to solve this build cycle. It seems sfc needs ovsdb and vice-versa causing a build cycle between the 2 projects (see below). How do we resolve this? and is

Thanks Sam. Actually, this what I thought I need to do (only include odl-ovsdb-southbound-impl in my features.xml), but I am not sure what part I am missing. I believe the devstack & ODL connection

Khal, the OVSDB southbound plugin [1] will populate the topology with the ovsdb node information, including the bridges and ports. With devstack as part of the local.conf config the ODL address is

Hi, I can’t figure out how OVSDB populate ODL Inventory based on openstack (i.e. specifically after ./stack.sh is complete). Also, is there a feature I can include in my project to do that.

Thank you for confirming :) Ed

all, we are starting an ongoing sync up call at 7 am PST tuesdays, to implement hardware_vtep schema to the ovsdb project. please find meeting details attached. here's the agenda set from initial

i tried different ovs port to connect to from controller and it worked fine for me. -- Thanks Anil

If memory serves, we *should* be able to use any port we desire in connection_info when starting a connection from the controller to ovsdb. That said, to be completely honest, I've never tried any

Hi Sam, controller is always tested with 6640, I am just talking on the OVS side.

Luis, 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

Ah, ok, then yes, 6634 would be acceptable as that's what the system is currently configured for. -Andy- -- Andrew J Grimberg Systems Administrator The Linux Foundation

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

Ed, 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

Luis, 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

Hi ovsdb experts, Anyone knows if there is any agreement on standard OVSDB server port. Our controller uses 6640 while SELinux assumes 6634 for example. BR/Luis

This event has been changed. more details » OVSDB VTEP meeting Changed: OVSDB VTEP Mtg Every Tuesday, from Tue, Jun 23, 2015 to no end date, 8:00 am | 1 hr Denver (Mountain Daylight Time,