> My original thought was a new table of chains. Each chain has a list of
> service endpoints (originally i had this as logical ports, but it'd need
> to be IP or MAC addresses, I guess). A chain would also have a match
> defined in the same syntax used by ACLs. I imagined the implementation
> i
Have you tried using ovs-vsctl --no-wait set open_vswitch .
external-ids:ovn-encap-ip="$HOST_IP" on master controller, "HOST_IP" being ip
of interface where you would like to have tunnel llistener? Controller would
send this IP info to compute nodes for establishing tunnels.
Hi All,
I am currently exploring Service Function Chaining (SFC) implementation using
OVN and would like to hear thoughts from the community.
Has anyone implemented Service Function Chaining using OVN project and would be
willing to share his/her experiences? There are proposals for adding NSH
