Participants: Zoltan, Jan
Patch series
* Generic Encap/Decap (EXT 382) for Ethernet
o v2 series submitted as discussed
o Ben P already merged the PTAP bugfix patch (1/3)
o Jan identified lack of check on VLAN tags in translation of decap() for
Ethernet.
Tagged packets
Hi,
Focus on getting the remaining series reviewed and merged for OVS 2.8:
1. Generic Encap/Decap (EXT 382) for Ethernet (Ericsson)
2. L3/PTAP tunnel config for kernel datapath (RedHat)
3. Basic NSH MD1 including Encap/Decap for NSH (Intel)
Minutes of previous meeting
Participants: Ben P, Zoltan, Jan, Jiri, Thomas Morin
Patch series
* Generic Encap/Decap (EXT 382) for Ethernet
o Reviewed by Ben
o One tunnel config bugfix commit merged
o Zoltan will extract the PTAP bugfix and post separately
o Zoltan to submit v2 series
*
Hi,
Focus on getting the remaining series reviewed and merged for OVS 2.8:
1. Generic Encap/Decap (EXT 382) for Ethernet (Ericsson)
2. Basic NSH MD1 including Encap/Decap for NSH (Intel)
3. L3/PTAP tunnel config for kernel datapath (RedHat)
Thank you,
Jan
Link to the Google design doc:
Participants: Ben P, Zoltan, Jan, Thomas Morin
Patch series
* PTAP v4
o Merged by Ben last night. Thanks!
* Generic Encap/Decap (EXT 382) for Ethernet
o Rebased on PTAP v4 and refactored (refined CLI syntax)
o Can be posted this week
* Support for NSH MD1
Start postponed by 30 minutes due to collision with an internal meeting.
Hi,
Focus on getting PTAP series merged and attack the review of two remaining
series
1. Generic Encap/Decap (EXT 382) for Ethernet and
2. Basic NSH MD1 including Encap/Decap for NSH
Thank you,
Jan
Link to the Google
Hi,
Focus on getting PTAP series merged and attack the review of two remaining
series
1. Generic Encap/Decap (EXT 382) for Ethernet and
2. Basic NSH MD1 including Encap/Decap for NSH
Thank you,
Jan
Link to the Google design doc:
On Fri, Jun 16, 2017 at 03:35:41PM +, Jan Scheurich wrote:
> * Ben will update his patch series with the conclusions so far today
> and repost. The fixups can be folded in.
I did not have enough time for this today, so it will probably happen
Saturday or Sunday. I'm traveling, but
Hi,
Main purpose of this sync meeting is to agree on final technical solution for
PTAP to allow merging of that patch series and to establish a stable base for
Generic Encap/Decap and NSH patch series.
Target is still to upstream these changes in time for OVS 2.8.
Thank you,
Jan
Link to the
Participants
* Zoltan, Jan, Jiri, Ben P, Georg, Ben M
Review/Discussion of current patch sets
* RTNETLINK tunnel configuration (RedHat)
Done: Merged my Joe on May 18th
* L3 Tunneling (Ericsson)
Done: remaining 3 patches merged by Ben on June 2nd
* L3 tunnel config
Hi,
Let's have a look at the progress of the different patch series with respect to
submission, review and merging.
Target is still to upstream these changes in time for OVS 2.8.
Thank you,
Jan
Link to the Google design doc:
Participants
* Ben M, Zoltan, Georg, Jan, Simon
Review/Discussion of current patch packages
1. RTNETLINK tunnel configuration - v3 still under review by Joe S (no
update)
2. L3 Tunneling
a. v4: Ben P has merged 1st patch. Comment on 2nd patch fixed in v5
b. v5: out on
Moved to 2pm CET to accommodate Ben, who is in Boston that week.
Perhaps also Yi can join at that time slot.
Hi,
Let's have a look at the status and work out a plan how to accelerate the
review and merging in order to achieve the agreed target to upstream these
changes in time for OVS 2.8.
Hi,
Let's have a look at the status and work out a plan how to accelerate the
review and merging in order to achieve the agreed target to upstream these
changes in time for OVS 2.8.
Thank you,
Jan
Link to the Google design doc:
Participants
* Ben P, Zoltan, Georg, Jan, Jiri
Review/Discussion of current patch packages
1. RTNETLINK tunnel configuration - v3 still under review by Joe S
2. L3 Tunneling - v4 out fixing sparse errors. Ben to continue review
3. PTAP - v1 out for review. Will need rebase to
Hi,
The team is making good progress in preparing the various patch packages. We
have a lot of things working in our gitlab repo
(https://gitlab.com/JScheurich/ovs). v3 of the L3 tunneling patches are out on
the mailing list since a week
Hi Jan,
I do not understand the concept of masked packet type. The note below from
the call is:
- For masked packet_types use “/mask” or “*” notation ,
e.g. packet_type=(1,*) to match any packet with name space ethertype.
Is this intended to relate to the canonical packet type ID or to
On Mon, Mar 13, 2017 at 05:23:26PM +, Jan Scheurich wrote:
> 2. Kernel datapath tunnel configuration (RedHat, Eric Garver)
> * Still no comment yet
> * Resend as non-RFC patch to trigger new comments. Please review!
> * Jan to include the new patch in Gitlab repo (see
Hi,
Please be invited to our next sync meeting: Mon 13 March, 5pm CET.
Agenda:
* Review/Discussion of current patch packages, e.g.
o Display format for packet_type field in match and flow keys
o packet_type in struct dp_packet or struct pkt_metadata
* Status/Planning of
Thanks for the invite. In general I’d prefer if the email title or body would
also contain the proposed meeting date & time.
I started review of the L3 userspace patches 3 weeks ago, but unfortunately
have been swamped by urgent release tasks ever since. This should ease a bit
next week.
I also missed the meeting, did not have it my calendar, sorry.
Jarno
> On Jan 24, 2017, at 5:52 AM, Jiri Benc wrote:
>
> On Wed, 18 Jan 2017 09:53:18 +, Jan Scheurich wrote:
>> Please be invited to the next sync meeting.
>
> Sorry, won't make the meeting today. Too
On Wed, 18 Jan 2017 09:53:18 +, Jan Scheurich wrote:
> Please be invited to the next sync meeting.
Sorry, won't make the meeting today. Too busy with DevConf.cz
preparations.
> Actions Points:
> AP-1 (Jarno): Coordinate review of Yi's backported net-next patches
> AP-2 (Jiri) Check the
Hi,
Please be invited to the next sync meeting.
Minutes of the previous meeting:
https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327738.html
Actions Points:
AP-1 (Jarno): Coordinate review of Yi's backported net-next patches
AP-2 (Jiri) Check the ability of the kernel datapath to
Hi,
Please be invited to the first sync meeting in the new year.
Agenda:
* Status/progress/coordination of work packages:
1 - L3 packets in kernel datapath (net-next)
2 - Layer 3 tunnel configuration
3 - L3 ports in non-PTAP bridge
6 - VXLAN-GPE tunnel
4 -
pet...@ovn.org' <jpet...@ovn.org>;
> 'ja...@ovn.org' <ja...@ovn.org>; 'Ben Pfaff' <bpf...@vmware.com>;
> 'ben.mackcr...@corsa.com' <ben.mackcr...@corsa.com>; d...@openvswitch.org;
> Zhou, Danny <danny.z...@intel.com>
> Subject: Re: [ovs-dev] Sync on PTAP, EXT-3
On Mon, 9 Jan 2017 11:15:22 +, Yang, Yi Y wrote:
> We need to let users have one NSH version available before your
> proposal is implemented. I support your proposal, but I have no way
> to do anything helpful before your implementation for generic
> encap/decap and packet_type are available.
om'
<ben.mackcr...@corsa.com>; d...@openvswitch.org; Zhou, Danny
<danny.z...@intel.com>
Subject: Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH
Hi Yi,
I fully agree that support for NSH has been dragging along for to long. The
prime reason for this (in addition to the depend
..@netronome.com>;
'jpet...@ovn.org' <jpet...@ovn.org>; 'ja...@ovn.org' <ja...@ovn.org>;
'Ben Pfaff' <bpf...@vmware.com>; 'ben.mackcr...@corsa.com'
<ben.mackcr...@corsa.com>; d...@openvswitch.org; Zhou, Danny
<danny.z...@intel.com>
*Subject:* Re: [ovs-dev] Sync on
m>; Pravin Shelar <pshe...@ovn.org>;
Simon Horman (simon.hor...@netronome.com) <simon.hor...@netronome.com>;
'jpet...@ovn.org' <jpet...@ovn.org>; 'ja...@ovn.org' <ja...@ovn.org>; 'Ben
Pfaff' <bpf...@vmware.com>; 'ben.mackcr...@corsa.com'
<ben.mackcr...@corsa.com>; d.
Hi Yi,
Thanks for the confirmation and for rebasing the existing L3 tunneling
patches to include VXLAN-GPE.
Unfortunately, Simon's original user-space implementation in patches
9/17 through 11/17 using base_layer and offset fields in dp_packet is
not compatible to our ongoing implementation
Re: Discussed introduction of a new OXM class for the proposed GEN_TLV
fields
- No problem to reserve an OXM class even before those fields are
standardized
We have allocated OXM class 0x8005 for TLV value mapping (experimental for
now) in the ONF Registry
Thanks for the good meeting. Here are my notes:
Date: 2016-12-21, 17-18:30 CET
Participants: Jarno R, Ben P, Ben M-C, Jiri B, Simon H, Zoltan B, Jan S
Summary:
* Discussed making PTAP, EXT-382 and NSH available as extensions to OF
1.3.
o No big deal for the match fields and the
Hi Jan,
On Sun, 18 Dec 2016 14:44:03 +, Jan Scheurich wrote:
> I would like to call for a final sync meeting before the Christmas break.
you managed to hit almost the only slot in this week when I have a
conflict with another meeting. I'm not available on Tuesday starting at
the time you
Hello all,
I would like to call for a final sync meeting before the Christmas break.
Now that we have gone through the main aspects of the design, I would like to
focus on how to divide the entire function into manageable pieces, discuss the
potential work split, an integration anatomy and a
Hi,
Thank you for the constructive meeting. Here are my notes:
Date: 2016-12-15, 8-9:30 am CET
Participants: Yi Yang, Danny Zhou, Zoltan Balogh, Jan Scheurich
Summary:
* Went through the proposed solution for NSH based on PTAP and generic
encap/decap in the doc:
35 matches
Mail list logo