Re: hwvtep high level control flow
toggle quoted message Show quoted text
It's good to add md-sal data store in between, because in beryllium release neutron-northbound project won't be talking to net-virt directly. Neutron northbound will be pushing all the data to data store and net-virt will be listening to those data changes.
As of now Net-Virt relies that use will connect the compute nodes to the controller using tcp:ip:port, rather then putting switch in passive mode (ptcp:port) and expected controller to connect to it. Although OVSDB southbound plugin allows user to proactively connect to the switch if switch is listening for the connection by putting hyper-visor data in config data store. If OpenStack l2gateway rest APIs provide hardware vtep device information (ip,port this device is listening for connection on) then i think you can support controller initiated connection as well.
On Fri, Aug 28, 2015 at 8:36 AM, <Ravi_Sabapathy@...> wrote: