On Tue, Jul 14, 2015 at 7:19 AM, Liran Schour <lir...@il.ibm.com> wrote:
> "dev" <dev-boun...@openvswitch.org> wrote on 14/07/2015 06:22:43 AM: > > > This commit adds the pipeline module to ovn-controller-vtep. The > > module will scan through the Binding table, and create the > > Ucast_Macs_Remote in vtep database for each logical port's MACs in > > the same logical datapath (same as logical switch for vtep). Also > > the module will create the physical locators to each HV chassis in > > the same logical datapath. > > > > TODO: > > > > - vtep gateway will create entries in the "Ucast_Macs_Local" for > > each MAC learned. ovn-controller-vtep should take advantage of > > this and notify the ovn-sb database in some way so that all HVs > > (in the same logical datapath) are aware of these MACs and will > > send all related packets to the vtep gateway. We should achieve > > this in the near future. > > > > Signed-off-by: Alex Wang <al...@nicira.com> > > > > For clarification. Do you expect someone to add logical port with unknown > MAC to the NB DB? > Yes, I expect that, since we want to assume there is only one VTEP gateway for now. If so why not to do the learning through the NB DB and add the learned MACs > there. It will be projected to the SB DB by northd. > > We discussed that. The learned MACs could change very frequently, it is too expensive to update it to northbond database. So for now, we go for the simplest solution first. > Thanks, > - Liran _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
