gizmoguy_ has quit [Remote host closed the connection]
gizmoguy_ has joined #openvswitch
jlibosva has quit [Ping timeout: 260 seconds]
egy has joined #openvswitch
jlibosva has joined #openvswitch
ChmEarl has quit [Quit: Leaving]
jlibosva has quit [Ping timeout: 248 seconds]
jlibosva has joined #openvswitch
evplus has joined #openvswitch
felixhuettner has joined #openvswitch
elvira1 has joined #openvswitch
jlibosva has quit [Ping timeout: 252 seconds]
jlibosva has joined #openvswitch
jlibosva has quit [Ping timeout: 272 seconds]
jlibosva has joined #openvswitch
arif-ali has quit [Quit: ZNC 1.9.0+deb2build3 - https://znc.in]
arif-ali has joined #openvswitch
arif-ali has quit [Client Quit]
arif-ali has joined #openvswitch
elvira1 has quit [Ping timeout: 265 seconds]
elvira has joined #openvswitch
elvira has quit [Ping timeout: 276 seconds]
elvira has joined #openvswitch
jlibosva has quit [Quit: WeeChat 4.5.1]
elvira has quit [Ping timeout: 276 seconds]
elvira has joined #openvswitch
arif-ali has quit [Quit: ZNC 1.9.0+deb2build3 - https://znc.in]
arif-ali has joined #openvswitch
arif-ali has quit [Changing host]
arif-ali has joined #openvswitch
elvira has quit [Ping timeout: 248 seconds]
elvira has joined #openvswitch
haleyb has quit [Ping timeout: 260 seconds]
imaximets__ has joined #openvswitch
imaximets_ has quit [Ping timeout: 276 seconds]
haleyb has joined #openvswitch
ChmEarl has joined #openvswitch
felixhuettner has quit [Quit: felixhuettner]
zhouhan has joined #openvswitch
elvira has quit [Ping timeout: 244 seconds]
amusil has joined #openvswitch
mkalcok has joined #openvswitch
mmichelson has joined #openvswitch
ihrachyshka has joined #openvswitch
elvira has joined #openvswitch
<mmichelson>
Hi everyone, it's time to begin the weekly OVN developers' meeting.
<fnordahl>
o/
<amusil>
Hi
<mkalcok>
o/
<mmichelson>
I can give the first update.
<mmichelson>
We're in soft freeze, so I've been doing code reviews. Today I'm addressing amusil's feedback on the datapath refactor with I-P series. I also have a few other reviews on patchwork that I intend to give a look.
imaximets__ has quit [Changing host]
imaximets__ has joined #openvswitch
imaximets__ is now known as imaximets
<mmichelson>
That's the extent of my update. However, I do have a topic I'd like to bring up after everyone else has had their turn with regards to branching.
<mmichelson>
So who's next?
<mkalcok>
I could give a quick one
<mmichelson>
go right ahead mkalcok
<mkalcok>
I was mostly on bringing point releases to ubuntu. First time doing this packaging work, so it's a lot to take in.
<fnordahl>
mkalcok++
<mkalcok>
I also have one question but I don't want to derail the meeting too much. Just out of curiosity.
<mkalcok>
In the OVSDB protocol RFC it says that both server and client have to implement response to ECHO requests, but looking briefly at ovsdb-server, it never sends the echos. Does anyone know a reasoning for it? was it not useful (if it was ever in there)?
<mmichelson>
That's interesting, because I know that in OVN, as the client we have code to respond to echo requests.
<imaximets>
It does send them. They are part of jsonrpc.
ihrachyshka has quit [Quit: Client closed]
<mkalcok>
ah, maybe I just missed them. (I saw the parts in client that support responding to requests).
<mkalcok>
thanks. I'll take closer look :)
<imaximets>
np. fnordahl, mkalcok : are you still planning to cleanup upstream debian packaging in ovn?
<imaximets>
just curious, it's been a while.
<fnordahl>
ha, I think we keep getting squashed on the ovn-vif thing, but I guess you have some open comments on the last iteration that we can address
<fnordahl>
imaximets: thanks for the reminder
<fnordahl>
since I'm speaking I can update quickly
<fnordahl>
Quite busy with various downstream issues, and will try to do some reviews despite this.
<fnordahl>
that's about it
<mmichelson>
Thanks fnordahl
<mmichelson>
Who wants to go next?
<imaximets>
May I?
<mmichelson>
imaximets, no
<mmichelson>
just kidding, you may :)
<fnordahl>
lol
<imaximets>
I've been working on ipv6 datapath flow explosion issue in ovn-kubernetes. Turned out to be an issue with a non-contiguous match on ip6.mcast_rsvd.
moloings has joined #openvswitch
<imaximets>
Sent out a patch and it got accepted already. Thanks, zhouhan, for a quick review!
<amusil>
tldr; We can merge the patch from MJ as is and do the follow ups in the EVPN series
<amusil>
Other than that there are somme issues with BGP so I have posted one fix with another one probably following
<amusil>
Also reviews because uf the soft freeze
<fnordahl>
oh, that definitively works for me. We can do another iteration post-merge too if there are things we want to improve. Will respond to the mail
<amusil>
I would also like to encourage community members to help with reviews as there is a lot of features lined up for the next release
<amusil>
That's it, thanks
<mmichelson>
Thanks amusil
<amusil>
fnordahl Thanks!
<mmichelson>
Do we have anyone else that wishes to give an update?
<mmichelson>
OK, I think that's a no. I had one last thing to bring up. We have about 8 days remaining to get reviews done on new features before we branch. Based on the current state, that might be a bit tight. Would anyone be opposed to delaying branching by one week? This would not delay the release.
<amusil>
Also adding to that, should we adjust our schedule? This is 3rd time or so that we need to postpone branching. Should we make it 4 weeks between soft freeze and branching by default?
<mmichelson>
We could do that. The other idea is something imaximets has brought up before, which is to only consider patches that have had at least one round of reviews on them.
<imaximets>
That's what OVS does.
<mmichelson>
That way, last-second patches are not considered for inclusion.
<amusil>
That would exclude a lot of features
<amusil>
Not saying it's bad, just stating the obvious I guess
<imaximets>
It will just force peopel to post earlier and not last-minute.
<mmichelson>
Yeah, and the stuff that's posted late won't be excluded, necessarily. They just get delayed by a release.
<amusil>
4 weeks will give us more time reviews in general, but yeah those are the two options I guess
<mmichelson>
We could even do both.
<imaximets>
It's not like we have a huge number of people posting things all the time. It's mostly a deadline--driven development.
<amusil>
Also the first round of review is a bit double edged sword
<fnordahl>
No issue on our side wrt. move of this branching, for any urgent needs for downstream development release we can always snapshot the main branch
<amusil>
Sometimes we don't have the time to review while we are rushing our own features
<fnordahl>
would extending the freeze period perpetually move the relase date?
<mmichelson>
fnordahl, I think the idea would be to move the soft freeze ahead by two weeks.
<amusil>
+1
<mmichelson>
s/ahead by two weeks/two weeks earlier/
<mmichelson>
Just for clarity ^
<fnordahl>
got it, yeah, that works. I have to have a conversation with my inner procrastinator, but other than that I have no issues
<mkalcok>
I like better the idea of extending the soft freeze window, rather than requiring at least one round of reviews because it's more deterministic.
<mmichelson>
OK, so let's plan on having an extra week before branching for 25.03. After it is branched, I can send a proposed doc update that will change the calendar for 2026 and possibly also change the policy for which patches are considered for inclusion. We can have deeper discussions on the patch itself.
<imaximets>
Note: this will clash with OVs freeze, i.e. some features that may be needed from OVS may not be available in time for OVN freeze.
<amusil>
For those we could have exception, but it's up to debate for individual patches I guess
<mmichelson>
imaximets, ack. There are ways around this, and I think they're better discussed when a concrete plan has been proposed.
<mmichelson>
Does anyone else have anything they wish to discuss right now?
<mmichelson>
Thanks everyone, and have a good day!
<fnordahl>
\o thanks all cheers!
<amusil>
Thanks, bye
<mmichelson>
Bye
<imaximets>
Thanks. Bye!
mmichelson has quit [Quit: Leaving]
<mkalcok>
\o thanks bye
<moloings>
Bye
ihrachyshka has quit [Quit: Client closed]
mkalcok has quit [Quit: leaving]
moloings has quit [Quit: WeeChat 4.6.3]
amusil has quit [Quit: Client closed]
zhouhan has quit [Ping timeout: 272 seconds]
arif-ali has quit [Quit: ZNC 1.9.0+deb2build3 - https://znc.in]
arif-ali has joined #openvswitch
tpires has joined #openvswitch
donhw has joined #openvswitch
elvira has quit [Ping timeout: 248 seconds]
donhw has quit [Read error: Connection reset by peer]