With 795d7f24ce0e2ed5454e193a059451d237289542 we have added
support for E-W routing on vlan backed networks by replacing
router port macs with chassis macs.
This replacement of router port mac need NOT be done on
gateway chassis for following reasons:
a. For N-S traffic, gateway chassis will
Background:
With c0974331b7a19a87ab8f1f2cec8fbe366af92fa2, we have added
support for E-W workflow for vlan backed DVRs.
This series enables N-S workflow for vlan backed DVRs.
Key difference between E-W and N-S traffic flow is that
N-S flow requires a gateway chassis. A gateway chassis
will be
Hi Numan,
My bad, I missed the sleep related comments.
Fixed the same in v6, please take a look.
Appreciate your help.
Regards,
Ankur
From: Numan Siddique
Sent: Friday, August 16, 2019 5:46 AM
To: Ankur Sharma
Cc: ovs-dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH v5 1/4 ovn] OVN: Do not
Background:
With c0974331b7a19a87ab8f1f2cec8fbe366af92fa2, we have added
support for E-W workflow for vlan backed DVRs.
This series enables N-S workflow for vlan backed DVRs.
Key difference between E-W and N-S traffic flow is that
N-S flow requires a gateway chassis. A gateway chassis
will be
Problem Description:
Redirection to chassisredirect ports happens only via tunnel
encapsulation. As a result, same cannot be leveraged upon for vlan backed
environments.
This series addresses the issue by allowing redirection to happen without
encapsulation.
Design:
===
a. High level design
Background:
With c0974331b7a19a87ab8f1f2cec8fbe366af92fa2, we have added
support for E-W workflow for vlan backed DVRs.
This series enables N-S workflow for vlan backed DVRs.
Key difference between E-W and N-S traffic flow is that
N-S flow requires a gateway chassis. A gateway chassis
will be
Thanks for the patch
Pls let me know if the following incremental works for you.
diff --git a/ofproto/ofproto-dpif.c b/ofproto/ofproto-dpif.c
index 244155a..cb8b51e 100644
--- a/ofproto/ofproto-dpif.c
+++ b/ofproto/ofproto-dpif.c
@@ -168,6 +168,12 @@ struct ct_timeout_policy {
Thanks for the patch
Pls let me know if this incremental works for you.
Main change is logging fix for timeout policy deletion.
Darrell
diff --git a/lib/dpif-netlink.c b/lib/dpif-netlink.c
index 1d4ee60..00d957b 100644
--- a/lib/dpif-netlink.c
+++ b/lib/dpif-netlink.c
@@ -2822,11 +2822,10 @@
Et si l'Auto-Hypnose était votre solution ?TABAC - MINCEUR - STRESS - CONFIANCE
...Fichiers AUDIO MP3 à écouter chez vous, sur votre smartphone ...
CLIQUEZ ICI
Je souhaite me desinscrire, cliquez ici
___
dev mailing
On Thu, Aug 15, 2019 at 11:32 PM Numan Siddique wrote:
> On Thu, Aug 1, 2019 at 3:01 AM Aliasgar Ginwala
> wrote:
>
> > 1. Containerize ovn central components
> > 2. Containerize ovn host
> > 3. Update documentation about building/running ovn in containers.
> >
> >
>
> Hi Aliasgar,
>
> Thanks
On 8/13/19 12:27 PM, nusid...@redhat.com wrote:
From: Numan Siddique
With this patch we have to configure OVN to refer to external OVS source/build
directory instead of the ovs subtree.
The new configuration options added are:
* --with-ovs-source=/path/to/ovs/source/dir
*
On 8/13/19 12:28 PM, nusid...@redhat.com wrote:
From: Numan Siddique
"make rpm-fedora" is broken and this patch fixes it. Previous patch
in this series supported building OVN from external OVS sources.
Before running "make rpm-fedora", it is expected that the developer has run
"make dist" in
On 8/13/19 12:27 PM, nusid...@redhat.com wrote:
From: Numan Siddique
Until now, OVN uses the openvswitch rundirs (rundir, logdir, etcdir).
The commit [1] changed the package name from openvswitch to ovn, but
it didn't take into the account the effects of it. When "make install"
is run ovn-ctl
On Fri, Aug 16, 2019 at 4:32 PM Dumitru Ceara wrote:
>
> From: Dumitru Ceara
>
> Due to the use of a uint8_t to index inside the DNS payload we could end
> up in an infinite loop when specific (invalid) DNS packets were
> processed by ovn-controller. In the infinite loop we keep increasing the
>
From: Dumitru Ceara
Due to the use of a uint8_t to index inside the DNS payload we could end
up in an infinite loop when specific (invalid) DNS packets were
processed by ovn-controller. In the infinite loop we keep increasing the
query_name dynamic string until running out of memory.
One way to
Add the following new configuration options to the
Logical_Switch_Port:options column in the OVN Northbound database:
- mcast_flood: if set to 'true' all incoming IP multicast traffic
(except IP multicast reports) entering the switch will also be
flooded on the logical switch port.
-
On Fri, Aug 16, 2019 at 2:31 PM Numan Siddique wrote:
>
>
>
> On Fri, Aug 16, 2019 at 4:15 PM Dumitru Ceara wrote:
>>
>> Due to the use of a uint8_t to index inside the DNS payload we could end
>> up in an infinite loop when specific (invalid) DNS packets were
>> processed by ovn-controller. In
On Fri, Aug 16, 2019 at 3:04 PM Numan Siddique wrote:
>
>
>
> On Fri, Aug 16, 2019 at 6:23 PM Numan Siddique wrote:
>>
>>
>>
>> On Fri, Aug 16, 2019 at 5:51 PM Dumitru Ceara wrote:
>>>
>>> Add a new configuration option 'mcast_relay' to the Logical_Router:options
>>> in the OVN Northbound
On Fri, Aug 16, 2019 at 6:23 PM Numan Siddique wrote:
>
>
> On Fri, Aug 16, 2019 at 5:51 PM Dumitru Ceara wrote:
>
>> Add a new configuration option 'mcast_relay' to the Logical_Router:options
>> in the OVN Northbound database.
>>
>> If a router is configured with 'mcast_relay' enabled then
On Fri, Aug 16, 2019 at 5:51 PM Dumitru Ceara wrote:
> Add a new configuration option 'mcast_relay' to the Logical_Router:options
> in the OVN Northbound database.
>
> If a router is configured with 'mcast_relay' enabled then ovn-northd
> will install Logical_Flows to allow IP multicast traffic
On Fri, Aug 16, 2019 at 1:11 AM Ankur Sharma
wrote:
> With 795d7f24ce0e2ed5454e193a059451d237289542 we have added
> support for E-W routing on vlan backed networks by replacing
> router port macs with chassis macs.
>
> This replacement of router port mac need NOT be done on
> gateway chassis for
On Fri, Aug 16, 2019 at 4:15 PM Dumitru Ceara wrote:
> Due to the use of a uint8_t to index inside the DNS payload we could end
> up in an infinite loop when specific (invalid) DNS packets were
> processed by ovn-controller. In the infinite loop we keep increasing the
> query_name dynamic string
Add a new configuration option 'mcast_relay' to the Logical_Router:options
in the OVN Northbound database.
If a router is configured with 'mcast_relay' enabled then ovn-northd
will install Logical_Flows to allow IP multicast traffic to be routed
between Logical_Switches. The logical router will
On Fri, Aug 16, 2019 at 2:09 PM Numan Siddique wrote:
>
>
>
> On Fri, Aug 16, 2019 at 5:26 PM Dumitru Ceara wrote:
>>
>> On Fri, Aug 16, 2019 at 12:23 PM Numan Siddique wrote:
>> >
>> >
>> >
>> > On Mon, Aug 12, 2019 at 5:32 PM Dumitru Ceara wrote:
>> >>
>> >> Add a new configuration option
On Fri, Aug 16, 2019 at 5:26 PM Dumitru Ceara wrote:
> On Fri, Aug 16, 2019 at 12:23 PM Numan Siddique
> wrote:
> >
> >
> >
> > On Mon, Aug 12, 2019 at 5:32 PM Dumitru Ceara wrote:
> >>
> >> Add a new configuration option 'mcast_relay' to the
> Logical_Router:options
> >> in the OVN Northbound
On Fri, Aug 16, 2019 at 12:23 PM Numan Siddique wrote:
>
>
>
> On Mon, Aug 12, 2019 at 5:32 PM Dumitru Ceara wrote:
>>
>> Add a new configuration option 'mcast_relay' to the Logical_Router:options
>> in the OVN Northbound database.
>>
>> If a router is configured with 'mcast_relay' enabled then
When a packet is received, the RSS hash is calculated if it is not
already available. The Exact Match Cache (EMC) entry is then looked up
using this RSS hash.
When a MPLS encapsulated packet is received, the MPLS header is popped
and the packet is recirculated. Since the RSS hash has not been
Due to the use of a uint8_t to index inside the DNS payload we could end
up in an infinite loop when specific (invalid) DNS packets were
processed by ovn-controller. In the infinite loop we keep increasing the
query_name dynamic string until running out of memory.
One way to replicate the issue
On Mon, Aug 12, 2019 at 5:32 PM Dumitru Ceara wrote:
> Add a new configuration option 'mcast_relay' to the Logical_Router:options
> in the OVN Northbound database.
>
> If a router is configured with 'mcast_relay' enabled then ovn-northd
> will install Logical_Flows to allow IP multicast traffic
Hi Ilya,
Please see my response inline. I will be sending new patch after incorporating
some of your comments.
Regards,
Nitin
> -Original Message-
> From: Ilya Maximets [mailto:i.maxim...@samsung.com]
> Sent: Wednesday, August 14, 2019 5:45 PM
> To: Nitin Katiyar ;
On Thu, Aug 1, 2019 at 3:01 AM Aliasgar Ginwala wrote:
> 1. Containerize ovn central components
> 2. Containerize ovn host
> 3. Update documentation about building/running ovn in containers.
>
>
Hi Aliasgar,
Thanks for the patch. This is interesting. I tried out both the OVS patch
and this
31 matches
Mail list logo
