Friday, 2023-04-07

*** ministry is now known as __ministry07:18
opendevreviewSlawek Kaplonski proposed openstack/neutron master: WIP [S-RBAC] Switch to new policies by default  https://review.opendev.org/c/openstack/neutron/+/87982708:12
opendevreviewSlawek Kaplonski proposed openstack/neutron-tempest-plugin master: [S-RBAC] Switch to new policies by default  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/87982808:15
sahido/ quick question, should we keep bug that as indicated as NEW 6 years old?09:27
sahidbugs that are09:27
*** elodilles is now known as elodilles_pto10:11
opendevreviewSlawek Kaplonski proposed openstack/neutron master: WIP [S-RBAC] Switch to new policies by default  https://review.opendev.org/c/openstack/neutron/+/87982711:25
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [S-RBAC] Allow network owners to get ports from that network  https://review.opendev.org/c/openstack/neutron/+/87989111:25
opendevreviewSlawek Kaplonski proposed openstack/neutron master: WIP [S-RBAC] Switch to new policies by default  https://review.opendev.org/c/openstack/neutron/+/87982711:32
haleybsahid: it just means noone has triaged it, otherwise it should be Confirmed. But we've been closing things that old if we don't think they'll ever be fixed12:44
sahidhaleyb: ack thank you, I may start to clean some of those very old reports, i will take care to be sure that they will ever be fixed before doing it13:00
sahidthanks a lot for your back13:00
opendevreviewBrian Haley proposed openstack/neutron master: DNM: Test neutron gate failure  https://review.opendev.org/c/openstack/neutron/+/87989413:00
haleybsahid: yes, it was mentioned at the vPTG, we closed about 400 last cycle in various states, so we should continue. if need be they can re-open with more data13:02
sahidhaleyb: ack i may have missed some details during vPTG :-)13:05
haleybsahid: yeah, we might have just talked about it during the good/bad discussion. actually if you look at the previous meeting notes, there is a good query for this, https://etherpad.opendev.org/p/neutron-antelope-ptg L12713:08
haleybthat's what I've been using, then filter by priority perhaps? it's a start13:08
sahidoh yes interesting query I was using one to see old bugs that are new and still undecided without the priority criteria13:19
dvo-plv#startmeeting neutron_drivers14:03
opendevmeetMeeting started Fri Apr  7 14:03:56 2023 UTC and is due to finish in 60 minutes.  The chair is dvo-plv. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
opendevmeetThe meeting name has been set to 'neutron_drivers'14:03
haleybmeeting was cancelled, odd14:04
haleybdvo-plv: ?14:05
haleyb#endmeeting14:05
dvo-plvHello, haleyb14:06
dvo-plvwill threre be a driver meeting ? 14:06
haleybdvo-plv: no, it was canceled, and only the chair should start meetings14:06
haleybplease type #endmeeting or it will be stuck open14:07
dvo-plvI see, sorry, I thought that it required to be joined14:07
dvo-plv#endmeeting14:07
opendevmeetMeeting ended Fri Apr  7 14:07:31 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:07
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_drivers/2023/neutron_drivers.2023-04-07-14.03.html14:07
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2023/neutron_drivers.2023-04-07-14.03.txt14:07
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_drivers/2023/neutron_drivers.2023-04-07-14.03.log.html14:07
haleybno, meetings are in this channel, so if you're here don't need to join14:07
haleybit is a holiday for most today14:08
dvo-plvI see, I was guided by this schedule https://meetings.opendev.org/#Neutron_drivers_Meeting14:08
dvo-plvThank you, sorry for troubling14:09
haleybdvo-plv: the agenda is sent to openstack-discuss mail list usually the day before by the ptl, who chairs the meeting14:10
mlavalle2dvo-plv: the drivers meeting takes place normally in this channel at this time and day. Today is an exception, because it is a holiday in a lot of countries, so we wouldn't reach quorum today14:25
mlavalle2dvo-plv: drivers meetings require a minimum quorum to make decisions14:26
dvo-plvokay, thank you, sorry for mess14:28
mlavalle2dvo-plv: I think you are here because of https://bugs.launchpad.net/neutron/+bug/2013540. It will be discussed next week14:28
dvo-plvyes, exactly14:28
mlavalle2dvo-plv: last week during the session with you in the PTG, we didn't realize that today was a holiday in most countries. so, it is a mess of our creation because we inadvertintly misled you :-)14:30
opendevreviewSlawek Kaplonski proposed openstack/neutron master: WIP [S-RBAC] Switch to new policies by default  https://review.opendev.org/c/openstack/neutron/+/87982715:10
opendevreviewBrian Haley proposed openstack/neutron master: Fix NoSuchOptError error in Ipam unit tests  https://review.opendev.org/c/openstack/neutron/+/87990818:16
ihrachyshaleyb the reason why ovn allows RA/NA traffic for stateful SGs is because it skips ACLs for the protocols: https://github.com/ovn-org/ovn/blob/c85835fc84befb700f3f224e9153160b4ff613fc/northd/northd.c#L6480-L648620:56
ihrachysbut... only if LS "has_stateful" ACLs...20:56
ihrachyswhich also makes for weird behavior when - in neutron - we combine ports with stateless and stateful SGs... when only stateless SG ports are present in a network, they can't receive RA/NA... but once I create a VM attached to stateful SG in the same network, suddenly the stateless ports can also receive RA/NAs.20:57
haleybihrachys: interesting. so it did that to not do conntrack on them? and that's an interesting side-effect ^^21:01
ihrachysyeah. default behavior in ovn is allow not drop, so it's to skip ct only; they assume no functional difference either way (because it will be allowed anyway)... except that we drop all21:02
haleybhopefully it didn't make your work that much harder21:03
ihrachysI'm still thinking what to do with this knowledge21:03
ihrachysI also wonder if this behavior described above - where a random port created in a network affects other ports from other SG - should be explored further as a violation of security guarantees / isolation21:04
haleybsounds like a bug at first thought21:06
ihrachysif it only affects RA/NA etc. it can be considered part of the bug I care about (the protocols not enabled by default). just thinking if these are all the protocols that get affected by the "has_stateful" magic, or there's something else lurking.21:08
ihrachysI wouldn't want some other protocols enabled in the same manner21:08
opendevreviewBrian Haley proposed openstack/neutron master: OVN: Always try and create a metadata port on subnets  https://review.opendev.org/c/openstack/neutron/+/87991321:15
ihrachyshaleyb I'm thinking that maybe this skip-ct block for the protocols should be moved from under the has_stateful if-clause in OVN. the blocks does two things 1) skip-ct for the protocols and 2) skips all ACLs for the protocols. Yes, (1) indeed makes sense only when stateful ACLs are present; but (2) doesn't seem to have a relation to statefulness. If OVN skips ACLs for them for stateful, it should21:16
ihrachys do it for stateless too. Now, maybe (2) is a side-effect / was never intended. Gotta talk to OVN folks to understand what their intent was.21:16
haleyback. i watch the ovn ML too will keep an eye out21:18

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!