On Mon, Jul 23, 2018 at 6:30 PM, Mark Michelson wrote:
> On 07/23/2018 08:03 AM, Anil Venkata wrote:
>
>> Packets destined for VLAN remote logical ports are sent out through
>> physical table 65 rather than physical table 32 (Geneve remote logical
>> ports are sent th
Packets destined for VLAN remote logical ports are sent out through
physical table 65 rather than physical table 32 (Geneve remote logical
ports are sent through table 32). I found below description in ovn
architecture documentation.
vn.org> wrote:
> > > On Fri, Apr 13, 2018 at 5:27 PM, Ben Pfaff <b...@ovn.org> wrote:
> > >> On Wed, Apr 11, 2018 at 07:44:25PM +0530, Anil Venkata wrote:
> > >>> vm created on a vlan tenant network is using geneve tunnel(between
> compute
> > >>> an
In Openstack neutron reference implementation, all agents will be
periodically reporting their status to neutron server. Similarly in
Openstack OVN based deployment, we want ovn-controller to periodically
report its status to neutron server.
We can follow two approaches for this:
1)
This is nice option to have.
On 07-Mar-2018 6:27 PM, "Miguel Angel Ajo Pelayo"
wrote:
>
> As OVN started implementing L3HA with the use of BFD monitoring, after
> discussing with the people who is doing QA and thinking about future
> troubleshooting of the feature, they
On Fri, Mar 2, 2018 at 7:23 AM, Guru Shetty <g...@ovn.org> wrote:
>
>
> On 27 February 2018 at 03:13, Anil Venkata <anilvenk...@redhat.com> wrote:
>
>> For example, I have a 10.1.0.0/24 network and a load balancer is added
>> to it with 10.1.0.10 as VI
For example, I have a 10.1.0.0/24 network and a load balancer is added to
it with 10.1.0.10 as VIP and 10.1.0.2(MAC 50:54:00:00:00:01), 10.1.0.3(MAC
50:54:00:00:00:02) as members.
ovn-nbctl create load_balancer vips:10.1.0.10="10.1.0.2,10.1.0.3"
When I try to send a request from client within