Hi Venkata, On Thu, Oct 8, 2015 at 1:32 AM, Venkata Anil <vkomm...@redhat.com> wrote: > > > On 10/08/2015 01:06 PM, Han Zhou wrote: >> >> Sorry, correct a typo: >> >> On Wed, Oct 7, 2015 at 11:55 PM, Han Zhou <zhou...@gmail.com> wrote: >> >>> This would be a very interesting feature. But would it become scaling >>> bottleneck if each HV need to be programmed to hold all the logical >>> router flows (because it doesn't know whom could it be talking to)? > > I think already openstack neutron is following above approach.
Do you mean neutron DVR or any l3 service plugin? DVR uses linux namespaces rather than openflow calculated by a controller. That is completely different approach and yet no proof of large scale deployment. If you mean some other service plugins please point out. For example dragonflow is trying to implement it the reactive way I mentioned: first crossing subnets packets are sent to controller. Best regards, Han _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
