On 11/10/26 12:59 AM, Alexandra Rukomoinikova via dev wrote:
> Several ovn-controller instances may run with the same chassis name and
> the same encapsulation IP, an anycast address that is reachable over the
> underlay through ECMP. OVN then sees the whole group of nodes as a
> single chassis: a single Chassis record, a single Encap record and a
> single binding for every port placed on it, while the underlay decides
> which node of the group terminates a given tunnel flow.
> 
> There is no coordination and no leader election between the nodes of the
> group while writing to SBDB: every ovn-controller independently does the
> full bookkeeping for that one chassis, and it is the idempotence of those
> writes that keeps them from fighting each other.
> 
> The flip side is that the nodes must be configured identically in
> chassis-related params, and that nothing which relies on conntrack can be
> used, because the group shares no runtime state.
> 
> Document all of this, and add a multinode test that deploys two
> gateway nodes as one replicated gateway, gives a hypervisor and a node that
> does not run OVN an underlay ECMP route to the anycast encapsulation IP,
> checks the north-south connectivity through each of the two nodes and
> checks that the controllers do not fight over the shared records.
> 
> Signed-off-by: Alexandra Rukomoinikova <[email protected]>
> ---

Hi Sasha,

> +
> +AT_SETUP([ovn multinode replicated gateway])
> +
> +check_fake_multinode_setup
> +cleanup_multinode_resources
> +
> +# Two gateway nodes are deployed as one and the same "replicated" gateway: 
> both
> +# ovn-controllers register with the same chassis name and with the same 
> anycast
> +# encap IP. The encap IP is reachable over the underlay via ECMP through the
> +# physical addresses of both gateway nodes, so a geneve tunnel to the 
> replicated
> +# gateway may land on either of them.
> +#
> +#                             underlay (eth1, 170.168.0.0/16)
> +#  ┌───────────────────┐                                   
> ┌──────────────────┐
> +#  │  ovn-chassis-1    │   1.1.1.1/32                      │    ovn-gw-1     
>  │
> +#  │  (compute node)   ├──── nexthop via gw-1 eth1 ────────┤  
> ovn-replicated-gw  │
> +#  │                   │                                   │  encap 1.1.1.1  
>  │
> +#  │  sw0p1 10.0.0.3   ├──── nexthop via gw-2 eth1 ───┐    
> └────────┬─────────┘
> +#  └───────────────────┘                              │             │
> +#                                                     │    
> ┌────────┴─────────┐
> +#  ┌───────────────────┐                              └────┤    ovn-gw-2     
>  │
> +#  │  ovn-chassis-2    │   1.1.1.1/32                      │  
> ovn-replicated-gw  │
> +#  │ (external client) ├──── nexthop via gw-1 eth1 ────────┤  encap 1.1.1.1  
>  │
> +#  │                   ├──── nexthop via gw-2 eth1 ────────┤                 
>  │
> +#  │                   │                                   
> └────────┬─────────┘

Nit: misaligned diagrams.

With that addressed I pushed the patch to main.

Regards,
Dumitru

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to