unixpro1970 has quit [Remote host closed the connection]
Slasheri has quit [Ping timeout: 260 seconds]
unixpro1970 has joined #openvswitch
Slasher has joined #openvswitch
unixpro1970 has quit [Client Quit]
unixpro1970 has joined #openvswitch
unixpro1970 has quit [Remote host closed the connection]
unixpro1970 has joined #openvswitch
unixpro1970 has quit [Client Quit]
unixpro1970 has joined #openvswitch
mestery has quit [Read error: Connection reset by peer]
mestery has joined #openvswitch
tjr has quit [Quit: Ping timeout (120 seconds)]
tjr has joined #openvswitch
tjr has quit [Quit: Ping timeout (120 seconds)]
tjr has joined #openvswitch
kuraudo has joined #openvswitch
kuraudo has quit [Remote host closed the connection]
kuraudo has joined #openvswitch
elvira1 has joined #openvswitch
froyo__ has joined #openvswitch
froyo_ has quit [Ping timeout: 246 seconds]
Guest66 has joined #openvswitch
Guest66 has quit [Client Quit]
tpires_ has joined #openvswitch
Guest76 has joined #openvswitch
Guest76 has quit [Client Quit]
Guest777 has joined #openvswitch
Guest777 has quit [Client Quit]
taichou has joined #openvswitch
dceara has joined #openvswitch
kuraudo has quit [Remote host closed the connection]
kuraudo has joined #openvswitch
<SrRaven>
Maybe a question for #ansible (or the network automation group) instead, but anyone know why the openvswitch package is being discontinued by ansible?
ChmEarl has joined #openvswitch
roriorden has joined #openvswitch
Sragdhara has joined #openvswitch
marym has joined #openvswitch
zhouhan has joined #openvswitch
<imaximets_>
SrRaven, the discussion here says it's unmaintained: https://forum.ansible.com/t/6245 We're not maintaining it, and I don't know who the author is, so it is probably indeed unmaintained.
imaximets_ has quit [Changing host]
imaximets_ has joined #openvswitch
imaximets_ is now known as imaximets
<marym>
Hi everyone
<Sragdhara>
Hi everyone, I had posted RFC on service insertion design couple of weeks back (https://mail.openvswitch.org/pipermail/ovs-dev/2024-October/417711.html) that adds capability to redirect traffic via a network functions (such as L7 firewall) based on ACL match condition, while ensuring statefulness and support for both VLAN and overlay. Can we spend
<Sragdhara>
a few minutes discussing it?
<imaximets>
Hi. It's time for the OVN weekly meeting, if I didn't mess up the time.
<marym>
Hi
<imaximets>
Mark is not here today, so I can host, I guess.
<marym>
Can we go first?
<imaximets>
From my side though I don't really have any updates related to OVN, been mostly busy on OVS side with the ipsec series.
<imaximets>
marym, sure, go ahead!
<Sragdhara>
So far Mark has responded describing the new flexible OVN pipeline architecture he is working on and how he thinks the service insertion can fit in there. Would be great if we can (a) discuss further on this aspect (2) any general feedback on the proposal.
<Sragdhara>
In case my first msg was missed, posting again:
<Sragdhara>
Hi everyone, I had posted RFC on service insertion design couple of weeks back (https://mail.openvswitch.org/pipermail/ovs-dev/2024-October/417711.html) that adds capability to redirect traffic via a network functions (such as L7 firewall) based on ACL match condition, while ensuring statefulness and support for both VLAN and overlay. Can we spend
<marym>
imaximets Sragdhara and I are from Nutanix.
<Sragdhara>
a few minutes discussing it?
<imaximets>
Sragdhara, it feels like not a lot of people are here today... Might be the weird week where time moved in Europe but not yet in US...
<zhouhan>
hi
<Sragdhara>
Any thoughts on the proposal?
<imaximets>
zhouhan, Hi, did you have a chance to look at the proposal linked above?
<zhouhan>
not yet
<Sragdhara>
Also, is there anyone here (since Mark is not present) who is working with Mark on the new architecture ?
<imaximets>
It seems most of the people are either off or can't make it today.
<imaximets>
Maybe Dumitru will join.
<dceara>
I had a look at Mark's design document and Sragdhara's RFC but not in too much detail.
<dceara>
It's probably best to discuss on the mailing list and if needed we could also set up a audio/video meeting to dig deeper into details. How does that sound?
<Sragdhara>
Please let us know if there are any concerns with the design. We are working on the implementation and will send out a patch shortly.
<Sragdhara>
It is rather involved. So an audio/video meeting would be great.
<dceara>
OK, I suggest we take it to the mailing list and we can find a date & time that works for everyone interested
<Sragdhara>
Okay, on the mailing list we would discuss on the time and date then. Thanks.
<zhouhan>
Sragdhara: could you brief what's the relationship between Mark's design and yours?
<Sragdhara>
Mark's design is (if I understand it correctly), making the pipeline processing flexible by creating data paths for various services, such as ACL, NAT.
<Sragdhara>
Our design is for insertion of network functions in the logical switch pipeline, after the ACL processing.
<zhouhan>
Sragdhara: thanks. I was under the impression that Mark's design would include support for network functions. But let's discuss in more detail later.
<Sragdhara>
In his proposal he has an "external" datapath type and he thinks the network function insertion fits in there.
<dceara>
I think part of Mark's proposal speaks of "hook services" too to allow to potentially hook network functions in the middle of the pipeline too.
<Sragdhara>
His response to my email mentions "external" datapath as the fitting way.
<Sragdhara>
His document mentioned hook service as something that is more into the future and not planned for now.
<imaximets>
OK. Thanks for the context! I suppose, let's sync up on a list and find the time slot for the meeting. And we probably need Mark for this discussion anyway.
<zhouhan>
Cool! It is great to see people have similar requirements before implementing and find good opportunity to collaborate :)
<dceara>
+1
<imaximets>
OK. dceara, zhouhan, do you have something to report for today?
<zhouhan>
I am reviewing Ales's patch "Commit all traffic when there is stateful NAT/LB" and trying to test the performance impact of the extra CT recirc.
<zhouhan>
that's it from me
<dceara>
I don't have much, working on a bug fix for use-after-free in ovn-controller when mac binding/fdb aging is configured.
<dceara>
Oh, and I posted a patch to update the documentation wrt how we use the submodule on stable branches.
<dceara>
That's it from me, thanks!
<imaximets>
Ack. Thanks you!
<imaximets>
Anyone else here wants to share? Or maybe Sragdhara, marym you have some other topic to discuss?
<Sragdhara>
We had mainly the service insertion topic to discuss from our end. Nothing else for today.
<imaximets>
OK. Thanks!
<marym>
imaximets Regarding Mark's proposal, he mentioned that the plan is to make it available in OVN-25.03. Are sopme patches out for review already?
<dceara>
No patches out for review as far as I know.
<imaximets>
marym, I think, Mark is working on the code, but he didn't post anything yet.
<marym>
ok thank you.
<imaximets>
OK. I guess, we can call it a meeting.
<imaximets>
Thanks, everyone!
<marym>
bye
<imaximets>
Bye.
<zhouhan>
bye
<dceara>
Thanks, bye!
<Sragdhara>
bye
marym has quit [Quit: Client closed]
Sragdhara has quit [Quit: Client closed]
numans has joined #openvswitch
roriorden has quit [Ping timeout: 252 seconds]
zhouhan has quit [Quit: Client closed]
taichou has quit [Quit: Client closed]
roriorden has joined #openvswitch
roriorden has quit [Remote host closed the connection]
roriorden has joined #openvswitch
roriorden has quit [Client Quit]
dceara has quit [Ping timeout: 252 seconds]
kuraudo has quit [Ping timeout: 265 seconds]
dceara has joined #openvswitch
elvira1 has quit [Ping timeout: 276 seconds]
froyo__ has quit [Ping timeout: 276 seconds]
jistr has quit [Remote host closed the connection]