Hi Greg
few comments inline.
On Fri, Jun 14, 2019 at 1:44 PM Greg Rose wrote:
> The current documentation states that "all packets entering OVS for
> the first time are "untracked"". However there is a minor exception
> to this in the case where a packet (re)enters the same datapath and
> the
The current documentation states that "all packets entering OVS for
the first time are "untracked"". However there is a minor exception
to this in the case where a packet (re)enters the same datapath and
the namespace has not changed. In that case there is no need to
scrub the packet and in this
Bleep bloop. Greetings Numan Siddique, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 236 characters long (recommended limit is 79)
#497 FILE:
From: Numan Siddique
This new type is added for the following reasons:
- When a load balancer is created in an OpenStack deployment with Octavia
service, it creates a logical port 'VIP' for the virtual ip.
- This logical port is not bound to any VIF.
- Octavia service creates a
On 6/14/2019 5:40 PM, Louis Peens wrote:
On Wed, Jun 12, 2019 at 11:53 AM Eli Britstein
mailto:el...@mellanox.com>> wrote:
On 6/11/2019 2:21 PM, Ilya Maximets wrote:
>> On Mon, Jun 3, 2019 at 4:42 PM Simon Horman >
Add northd logical flows in order to reports that the controller
received an IP packet for LB rule witn no backends.
This configuration is used by OpenShift to spin up a idle POD
Signed-off-by: Mark Michelson
Co-authored-by: Mark Michelson
Signed-off-by: Lorenzo Bianconi
---
Add send_event() ovn action in order to allow ovs-vswitchd to report
CMS related events.
This commit introduces a new event, empty_lb_backends. This event is
raised if a received packet is destined for a load balancer VIP that has
no configured backend destinations. For this event, the event info
Add Controller_Event table to OVN SBDB in order to
report CMS related event.
Introduce event_table hashmap array and controller_event related
structures to ovn-controller in order to track pending events
forwarded by ovs-vswitchd. Moreover integrate event_table hashmap
array with event_table
There are situations where arrival of certain types of traffic into OVS
does not warrant a "typical" action, such as output to a specific port
or dropping. Rather, the decision about what to do needs to be left to a
CMS.
The series here introduces a new table, Controller_Event, for this
purpose.
Next meeting: 27th June
12th June minutes
Attendees: Frikkie, Ian, Scott, Roni, Pieter, David, Johann, Kevin.
===
GENERAL
===
- DPDK 18.11.2 (Kevin)
-- Released
-- https://mails.dpdk.org/archives/announce/2019-June/000267.html
- OVS 2.12 (Ian)
-- Dates
--- Assuming it follows previous
On Wed, Jun 12, 2019 at 11:53 AM Eli Britstein wrote:
>
> On 6/11/2019 2:21 PM, Ilya Maximets wrote:
> >> On Mon, Jun 3, 2019 at 4:42 PM Simon Horman netronome.com>
> >> wrote:
> >>
> >>> On Fri, May 31, 2019 at 02:45:25PM +0200, Simon Horman wrote:
> Sorry Eli,
>
> I had missed
On Thu, Jun 13, 2019 at 11:18 PM Lorenzo Bianconi <
lorenzo.bianc...@redhat.com> wrote:
> Do not send traffic for local FIP through the overlay tunnels but
> manage it in the local hypervisor
>
> Signed-off-by: Lorenzo Bianconi
>
Acked-by: Numan Siddique
> ---
> Changes since v1:
> - update
OVS may be unable to transmit packets for multiple reasons and
today there is a single counter to track packets dropped due to
any of those reasons. The most common reason is that a VM is
unable to read packets fast enough causing the vhostuser port
transmit queue on the OVS side to become full.
On Thu, Jun 13, 2019 at 3:51 AM Ankur Sharma
wrote:
> Hi,
>
> Just adding a minor clarification inline.
>
> Regards,
> Ankur
>
>
>
> *From:* Numan Siddique
> *Sent:* Wednesday, June 12, 2019 12:29 AM
> *To:* Han Zhou
> *Cc:* ovs dev ; Ankur Sharma <
> ankur.sha...@nutanix.com>
> *Subject:* Re:
From: Numan Siddique
This patch handles sending GARPs for
- router port IPs of a distributed router port
- router port IPs of a router port which belongs to gateway router
(with the option - redirect-chassis set in Logical_Router.options)
Signed-off-by: Numan Siddique
---
From: Numan Siddique
With the commit [1], the routing for the provider logical switches
connected to a router is centralized on the master gateway chassis
(if the option - reside-on-redirect-chassis) is set. When the
failover happens and a standby gateway chassis becomes master,
it should send
From: Numan Siddique
The present code which sets the Port_Binding.nat_addresses
can be simplied. This patch does this. This would help in
upcoming commits to set the nat_addresses column with the
mac and IPs of distributed logical router ports and logical
router ports with
From: Numan Siddique
The v1 of the patch series had just one patch which handled sending
GARPs for the logical router ports with the option -
reside-on-redirect-chassis set.
The v2 has totall 3 patches.
Patch 1 is a simple refactor in ovn-northd code which sets the
Port_Binding.nat_addresses
On Thu, Jun 13, 2019 at 10:23 PM Ben Pfaff wrote:
> On Wed, Jun 12, 2019 at 12:49:32PM +0530, nusid...@redhat.com wrote:
> > From: Numan Siddique
> >
> > The patch renames the make target - 'rpm-fedora-ovn' to 'rpm-fedora'
> >
> > Signed-off-by: Numan Siddique
>
> I didn't read all of this
19 matches
Mail list logo
