From: venkata anil
ovn-controller recalculates flows for all the members of a PG or AS
when a new member is added or deleted. Instead, this patch identifies
the changed members and only process their related flows.
Also this patch maintains constant sets for only local ports of a port
group
From: venkata anil
We have added new flows for using vlans instead of tunnels for
redirecting VLAN packets to a gateway chassis. This patch documents
these flows in ovn-northd.8.xml and ovn-architecture.7.xml.
Signed-off-by: Venkata Anil
---
v6->v7:
* Rebased
v5->v6:
* Rebased
v4->v5:
*
From: venkata anil
Previous patches in the series doesn't address issue 1 explained in [1]
i.e
1) removal of router gateway port MAC address on external switches
after expiring of aging time.
2) then external switches unable to learn the gateway MAC as
reply packets carry router internal
From: venkata anil
External switches should learn the distributed gateway port MAC address
as they have to forward the packet tagged with tenant vlan network but
with this MAC as destination MAC address. So router has to send ARP
reply and gARP for this MAC address through router internal patch
From: venkata anil
When a vm on a vlan tenant network sends traffic to an external network,
it is tunneled from host chassis to gateway chassis. In the earlier
discussion [1], Russel (also in his doc [2]) suggested if we can figure
out a way for OVN to do this redirect to the gateway host over a
From: venkata anil
This patch avoids tunneling and instead uses source tenant vlan network
across hypervisors for traffic from vlan network on local hypervisor
towards gateway hypervisor hosting redirect chassiss port.
On the local hypervisor, when the packet enters logical router ingress
From: venkata anil
We have added new flows for using vlans instead of tunnels for
redirecting VLAN packets to a gateway chassis. This patch documents
these flows in ovn-northd.8.xml and ovn-architecture.7.xml.
Signed-off-by: Venkata Anil
---
v5->v6:
* Rebased
v4->v5:
* This patch is added to
From: venkata anil
External switches should learn the distributed gateway port MAC address
as they have to forward the packet tagged with tenant vlan network but
with this MAC as destination MAC address. So router has to send ARP
reply and gARP for this MAC address through router internal patch
From: venkata anil
When a vm on a vlan tenant network sends traffic to an external network,
it is tunneled from host chassis to gateway chassis. In the earlier
discussion [1], Russel (also in his doc [2]) suggested if we can figure
out a way for OVN to do this redirect to the gateway host over a
From: venkata anil
This patch avoids tunneling and instead uses source tenant vlan network
across hypervisors for traffic from vlan network on local hypervisor
towards gateway hypervisor hosting redirect chassiss port.
On the local hypervisor, when the packet enters logical router ingress
From: Venkata Anil
We have added new flows for using vlans instead of tunnels for
redirecting VLAN packets to a gateway chassis. This patch documents
these flows in ovn-northd.8.xml and ovn-architecture.7.xml.
Signed-off-by: Venkata Anil
---
v4->v5:
* This patch is added to document the
From: Venkata Anil
External switches should learn the distributed gateway port MAC address
as they have to forward the packet tagged with tenant vlan network but
with this MAC as destination MAC address. So router has to send ARP
reply and gARP for this MAC address through router internal patch
From: Venkata Anil
When a vm on a vlan tenant network sends traffic to an external network,
it is tunneled from host chassis to gateway chassis. In the earlier
discussion [1], Russel (also in his doc [2]) suggested if we can figure
out a way for OVN to do this redirect to the gateway host over a
From: Venkata Anil
This patch avoids tunneling and instead uses source tenant vlan network
across hypervisors for traffic from vlan network on local hypervisor
towards gateway hypervisor hosting redirect chassiss port.
On the local hypervisor, when the packet enters logical router ingress
From: Venkata Anil
External switches should learn the distributed gateway port MAC address
as they have to forward the packet tagged with tenant vlan network but
with this MAC as destination MAC address. So router has to send ARP
reply and gARP for this MAC address through router internal patch
From: Venkata Anil
This patch avoids tunneling and instead uses source tenant vlan network
across hypervisors for traffic from vlan network on local hypervisor
towards gateway hypervisor hosting redirect chassiss port.
On the local hypervisor, when the packet enters logical router ingress
From: Venkata Anil
When a vm on a vlan tenant network sends traffic to an external network,
it is tunneled from host chassis to gateway chassis. In the earlier
discussion [1], Russel (also in his doc [2]) suggested if we can figure
out a way for OVN to do this redirect to the gateway host over a
From: venkata anil
When a vm on a vlan tenant network sends traffic to an external network,
it is tunneled from host chassis to gateway chassis. In the earlier
discussion [1], Russel (also in his doc [2]) suggested if we can figure
out a way for OVN to do this redirect to
From: venkata anil
When a vm on a vlan tenant network sends traffic to an external network,
it is tunneled from host chassis to gateway chassis. In the earlier
discussion [1], Russel (also in his doc [2]) suggested if we can figure
out a way for OVN to do this redirect to
From: Venkata Anil
When a vm on a vlan tenant network sends traffic to an external network,
it is tunneled from host chassis to gateway chassis. In the earlier
discussion [1], Russel (also in his doc [2]) suggested if we can figure
out a way for OVN to do this redirect to
From: Venkata Anil
Signed-off-by: Venkata Anil
---
lib/automake.mk | 3 ++-
lib/unixctl.xml | 26 ++
ovn/northd/ovn-northd.8.xml | 7 +--
ovn/northd/ovn-northd.c | 9 -
21 matches
Mail list logo