e: 03/25/2016 10:15 AM
> Subject: Re: [ovs-dev] [PATCH RFC] OVN: Openstack floating ip support
>
> "dev" wrote on 03/22/2016 04:19:07 PM:
>
> > From: Chandra Sekhar Vejendla/San Jose/IBM@IBMUS
> > To: dev@openvswitch.org
> > Date: 03/22/2016 04:19 PM
> &g
rther
processing, the packet will be sent out of port PVM2 to VM2.
[OUT PVM2]: m_net1, 198.44.1.3 -> m_vm2, 10.1.1.4
VM 10.1.1.4 responds to 198.44.1.3
[IN PVM2]: m_vm2, 10.1.1.4 -> m_net1, 198.44.1.3
The return path from 10.1.1.4 --> 198.44.1.3 will follow the exact same
path a
It would really help if you give packet walkthrough when following 2
simultaneous connections happen at the same time.
1. east-west without NAT between the private IP addresses
2 east-west with floating IP.
You also mentioned in the meeting (if I remember correctly) on how you have
to keep a part
"dev" wrote on 03/22/2016 04:19:07 PM:
> From: Chandra Sekhar Vejendla/San Jose/IBM@IBMUS
> To: dev@openvswitch.org
> Date: 03/22/2016 04:19 PM
> Subject: [ovs-dev] [PATCH RFC] OVN: Openstack floating ip support
> Sent by: "dev"
>
> This patch adds dis
This patch adds distributed floating ip support for ovn. The assumption made
here is that the external network is a single L2 broadcast domain and all the
chassis have connectivity to the external network.
2 new tables are added in the LROUTER pipeline IN_IP_DNAT & IP_IN_SNAT.
IN_IP_DNAT will modi
