Friday, 2022-03-18

zhouhenglcslaweq: a small patch https://review.opendev.org/c/openstack/neutron-fwaas/+/831478, when you have time, please check it :)02:20
opendevreviewliuyulong proposed openstack/neutron master: Config option for link down/up ext gw port HA router in backup node  https://review.opendev.org/c/openstack/neutron/+/83426005:54
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron-specs master: OVS: multiple routed provider segments per host  https://review.opendev.org/c/openstack/neutron-specs/+/82382306:21
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron-specs master: OVS: multiple routed provider segments per host  https://review.opendev.org/c/openstack/neutron-specs/+/82382306:35
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron-specs master: OVS: multiple routed provider segments per host  https://review.opendev.org/c/openstack/neutron-specs/+/82382306:36
opendevreviewyangjianfeng proposed openstack/neutron master: [docs] L3 router support ndp proxy  https://review.opendev.org/c/openstack/neutron/+/82225306:54
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/victoria: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83388408:00
opendevreviewSlawek Kaplonski proposed openstack/neutron stable/wallaby: Add FIPS enabled scenario jobs  https://review.opendev.org/c/openstack/neutron/+/82814308:45
opendevreviewLiangyi Ma proposed openstack/neutron-fwaas master: replace tearDown with addCleanup  https://review.opendev.org/c/openstack/neutron-fwaas/+/83426408:49
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider master: Fix zuul templates for functional and tempest tests  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83379808:53
opendevreviewSlawek Kaplonski proposed openstack/neutron stable/wallaby: DNM Just testing functional and fullstack fips jobs  https://review.opendev.org/c/openstack/neutron/+/83426508:57
opendevreviewZhouHeng proposed openstack/neutron-fwaas master: replace tearDown with addCleanup  https://review.opendev.org/c/openstack/neutron-fwaas/+/83426409:57
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider master: Fix zuul templates for functional and tempest tests  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83379810:21
opendevreviewLajos Katona proposed openstack/neutron master: Decrease OS_TEST_TIMEOUT to 240 for dsvm-fullstack  https://review.opendev.org/c/openstack/neutron/+/82748810:25
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/xena: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83388510:35
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/wallaby: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83388210:36
opendevreviewyangjianfeng proposed openstack/neutron-tempest-plugin master: [WIP] Add ndp proxy API tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/82779111:08
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/yoga: [Stable only] Fix CI jobs  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83428212:41
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/yoga: [Stable only] Fix CI jobs  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83428212:44
*** TheJulia is now known as needsleep12:57
*** needsleep is now known as TheJulia12:57
*** obondarev_ is now known as obondarev13:18
*** dasm|off is now known as dasm13:22
lajoskatonadamiandabrowski[m]: Hi, is today's drivers meeting ok for you for the GARP vs HA routers issue?13:25
lajoskatonatrident: ---^13:31
damiandabrowski[m]hey! I'm available if You need me but I didn't have enough time to prepare due to the internal incident in my company :/ 13:31
damiandabrowski[m]so we can either discuss it today or postpone to next Friday 13:32
tridentHey, yeah, I think it would probably make sense to actually postpone to next week. Same company and same incident has taken most of my time this week as well. Next week looks much more promising timewise for me.13:34
*** arne_wiebalck is now known as a2ew6k13:36
lajoskatonatrident: ok, thanks, I keep it in the agenda then (https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda )13:36
damiandabrowski[m]thank You!13:37
*** TheJulia is now known as needssleep13:38
slaweqlajoskatona: I have urgent issue at work today and will probably not be able to participate actively in drivers meeting13:47
slaweqbut I will be lurking here :)13:47
slaweqsorry13:47
tridentThanks very much lajoskatona!13:47
lajoskatonaslaweq: thanks13:50
lajoskatona#startmeeting neutron_drivers14:00
opendevmeetMeeting started Fri Mar 18 14:00:25 2022 UTC and is due to finish in 60 minutes.  The chair is lajoskatona. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'neutron_drivers'14:00
lajoskatonao/14:00
mlavalleo/14:00
obondarevhi14:00
yamamotohi14:01
noonedeadpunko/14:01
amotokihi14:01
haleybhi14:02
lajoskatonaI think we can start14:03
lajoskatonaThe first topic from the list regarding GARP are not sent during ha router master state transition we can postpone14:03
lajoskatonaSo the first one fortoday:14:04
lajoskatona[QoS][OvS] implement QoS bandwidth limitation by leveraging ovs meter (#link https://bugs.launchpad.net/neutron/+bug/1964342 )14:04
noonedeadpunkAre we?14:04
mlavalleyeah, I think that's trident's topic14:04
noonedeadpunkBecause that's quite critical14:04
slaweqo/14:04
noonedeadpunkBasic functionality is quite broken and this topic has not been taken for meeting for 3 weeks now14:04
lajoskatonanoonedeadpunk:  I jsut asked trident if we can discuss it today, but they had no time for testing the possible solutions this week14:04
mlavalleyeap14:05
slaweqis it about ingress or egress traffic (from vm point of view)?14:05
slaweqor both?14:05
tridentnoonedeadpunk: Yeah, me and damiandabrowski[m] discussed a bit and there is more testing on our side that needs to be done before we really have anything new to report on it.14:06
noonedeadpunkI'm not sure about egress14:06
noonedeadpunkIngress for sure is broken14:06
slaweqhttps://review.opendev.org/c/openstack/neutron/+/832662 that should fix current implementation of the ingress bw limit in ml2/ovs14:07
noonedeadpunkI'm not neutron code expert, but can try to help out. But eventuaalyy any solutions I saw has own flaws...14:07
lajoskatonanoonedeadpunk: could you sync with trident and than next week we can check the topic14:08
noonedeadpunkI don't think it will as VIP is not functional and mentioned patch not touching that part?14:08
lajoskatonanoonedeadpunk: is that work for you?14:08
noonedeadpunklajoskatona: yes, thanks!14:08
lajoskatonanoonedeadpunk: cool14:08
mlavalleso talking now about QoS?14:09
noonedeadpunksorry for interrupting:) I just joined to check out on the bug that was skipped without mentioning reason again :)14:09
lajoskatonayes I think we can jump on it14:09
lajoskatonanoonedeadpunk: true, I forgot to mention that I asked about it trident14:09
lajoskatonaSo the coming rfe:  [QoS][OvS] implement QoS bandwidth limitation by leveraging ovs meter (#link https://bugs.launchpad.net/neutron/+bug/1964342 )14:10
lajoskatonathis is from liuyulong14:10
lajoskatonaIf I understand correctly it is to have another QoS Bandwidth limit driver with os-ken and and ovs meter rules14:11
slaweqsorry, I though we are talking about this one all the time :)14:12
mlavalleLOL14:12
mlavalleyeah I figured14:12
* slaweq is focused mostly on other meeting now14:12
slaweqregarding this qos bw limit rfe - what's the point of having 2 different ways to configure it in ovs agent? I would just go with one which works better14:13
mlavalleagree14:13
slaweqso if using meters will be more accurate/efficient/better in other way - lets go with it and replace current implementation14:13
slaweqif it's not better, what's the point of adding it to the code?14:14
lajoskatonaslaweq: valid point14:14
slaweqthat's my opinion at least14:14
mlavalleI agree14:14
slaweqbut tbh I would like to see ralonsoh's thoughts on that one before approving/rejecting it14:14
mlavalleit seems he is trying to justify this from the off loading perspective14:14
mlavalleto smart-nic14:15
mlavallebut then he states that tc can also be off-loaded14:15
mlavalleI bit confusing14:15
lajoskatonathe current driver uses ovsdb 14:15
lajoskatonasorry half finished sentence....14:15
lajoskatonaso that one was confusing for me also, as I don't see why offloading is better with the proposed solution14:16
obondarevagree, need to clarify what are the benefits14:17
lajoskatonaok, I add the questions to the bug, and ask liuyulong to present the asked details, is that ok?14:18
obondarev14:19
obondarev+114:19
mlavalleperfect14:20
mlavalle+114:20
amotoki+114:20
lajoskatonaok, thanks14:20
lajoskatonaNext topic is:14:20
lajoskatonaDHCP agent scheduler filtering ignored when agent service restarted (#link https://bugs.launchpad.net/neutron/+bug/1964765 )14:21
lajoskatonait's from BBC as I see14:21
amotokihonestly I am not sure this is a bug or not....14:22
lajoskatonasummary is to have possiblity to schedule network on a group of dhcp agents specified by some regex filtering or similar14:23
obondarevI think it’s a fair expectation to have consistent filtering of dhcp agents when network (auto)scheduling14:23
lajoskatonaamotoki: your decision to mark it a srfe was really good, thanks14:23
lajoskatonaobondarev: true, I can imagine usecases to be useful like the one in the bug report14:24
obondarevfrom the other hand changing this behaviour (skip filtering on net auto schedule) might break things for someone14:26
obondarevfor this I think a new parameter in the Filter itself might be added - whether filter should be applied on net auto-schedule (agent restart)14:27
amotokiis it the right thing to skip filtering? I think it is better to apply consistent filtering if there is some inconsistency.14:27
obondarevthis will let us avoid new config option14:28
lajoskatonaand what about a new scheduler and if somebody needs this with possible traps, they select it in config?14:29
obondarevnew scheduler or new filter?14:29
lajoskatonaI thought new scheduler, as that is configurable14:30
amotokiI think two topics are mixed. the one is about a new filtering/scheduler and the other point is that filtering is skipped when agent restart.14:31
amotokii am not sure the second point only affects the new filtering mentioned in the bug.14:31
obondarevafaiu only segment related filtering is currently done on agent restart14:34
obondarevall others are skipped, both old and new ones14:34
lajoskatonaok so the LP can be split to an RFE and an actual bug?14:35
obondarevI think the bug is just to decide if we should enable filters on agent restart14:37
amotokiobondarev: agree14:38
obondarevand my point is - let's enable filtering on agent restart for those filters that explicitly say "apply me on restart" - then we can decide if existing filters should add this flag or not14:38
lajoskatona+114:39
amotoki+114:40
amotokiit looks like that the bug author does not request to add a new filter in neutron. the author just uses their new filter as an example to explain what happens.14:40
amotokiso I  totally agree with obondarev's point14:40
lajoskatonaamotoki: possible, I concerned more on the filter they created14:41
obondarevnot sure this new filter is even going to be upstreamed14:42
*** a2ew6k is now known as arne_wiebalck14:43
obondarevI mean if author has such plans14:43
lajoskatonaok, than the summary of this LP is: allow new flag for filters to execute them on agent restart, and set this to False for already existing filters14:43
lajoskatonaobondarev: possible14:44
obondarevor to accept it as False if filter doesn't have this parameter14:44
fnordahllajoskatona: (re question about smartnic_dpu docs, screnshot and possible marketing page reference) apologies for the tardy response, that is an excellent idea. Are you asking for expansion of the existing doc page or some oob screenshot of stuff in action?14:44
lajoskatonaobondarev: +114:45
lajoskatonafnordahl: just a sec we are at the end of the meeting14:46
lajoskatonaok regarding DHCP scheduling/filtering: is it ok this way for everybody?14:46
obondarev+114:46
amotokiI am still unclear a bit. I think AZ schduler does the similar thing so it might be affected, while network AZ and network segments are used together.14:47
amotokis/are not used together/14:48
obondarevso do you suggest to enable it for all filters on agent restart?14:51
amotokiwhat is "this way"? is it to accept filtering in dhcp RPC as False?14:51
amotokiif so, I am okay with it.14:52
amotokiIf the current behavior affects the existing scheduler, we can fix it separately.14:52
lajoskatonaamotoki: for this way I meant this : "allow new flag for filters to execute them on agent restart, and set this to False for already existing filters"14:53
obondarevIOW nothing changes for current filters, new filters can specify if they should filter on agent restart14:53
lajoskatonayes that's my understanding also14:53
amotokilajoskatona: obondarev: thanks for the clarification. I got it.14:53
lajoskatonaamotoki: :-) this is a tricky LP bug, but really good discussion14:54
lajoskatonaok, could you vote on in please if it is ok for you?14:55
mlavalle+114:55
amotoki+114:55
lajoskatona+114:55
obondarev+114:55
yamamoto+114:55
lajoskatonaok, thanks14:56
lajoskatonaif there is nothing more to discuss, we can close the meeting14:56
*** arne_wiebalck is now known as a2ew6k14:57
lajoskatona#endmeeting14:57
opendevmeetMeeting ended Fri Mar 18 14:57:29 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-18-14.00.html14:57
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-18-14.00.txt14:57
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-18-14.00.log.html14:57
lajoskatonao/14:57
mlavalleo/14:57
obondarevo/14:57
amotokihave a good weekend o/14:57
yamamotogood night14:57
lajoskatonathanks, have a good weekend :-)14:58
fnordahllajoskatona: sorry about that, I just jumped on the highlight not realizing a meeting was in session, my bad :)14:58
lajoskatonafnordahl: no problem14:58
*** a2ew6k is now known as arne_wiebalck14:59
lajoskatonafnordahl: the question was coming from diabl_rojo for Yoga marketing page, and they need more screenshots and such things14:59
lajoskatonafnordahl:  I think the doc pages are ok for them, at least yesterday when I asked there was no complaints :-)15:00
fnordahllajoskatona: we'd be happy to provide them, we have a talk on the schedule for the Berlin summit which will include a demo and we can take screenshots from that preparation. What are the timelines and where should we send them?15:01
lajoskatona fnordahl: cool, that sounds really good, and something that is more digestable for marketing people :-)15:02
lajoskatonaI think today15:02
lajoskatonalet me check the mail15:02
*** arne_wiebalck is now known as a2ew6k15:02
lajoskatonafnordahl: it's today, but no info which timezone today is closing 15:03
*** a2ew6k is now known as arne_wiebalck15:05
fnordahllajoskatona: right, I'll see what I can do, is this e-mail on the list i.e. do you have a link to it, or would it be possible for you to forward it to me?15:06
*** arne_wiebalck is now known as a2ew6k15:07
*** a2ew6k is now known as arne_wiebalck15:08
lajoskatonafnordahl: I forwarded it to frode.nordahl@canonical.com15:29
fnordahllajoskatona: excellent, thanks!15:29
opendevreviewBalazs Gibizer proposed openstack/neutron-lib master: Add port-mac-address-override shim extension  https://review.opendev.org/c/openstack/neutron-lib/+/83193515:43
opendevreviewBalazs Gibizer proposed openstack/neutron master: Update port MAC from binding profile for PFs  https://review.opendev.org/c/openstack/neutron/+/82924715:45
gibi_ptolajoskatona, rubasov, ralonsoh: ^^ update the bugfix to overwrite the data in the DB and proposed a shim API extension for it15:46
lajoskatonagibi_pto:  thanks15:55
opendevreviewBalazs Gibizer proposed openstack/neutron-lib master: Add port-mac-address-override shim extension  https://review.opendev.org/c/openstack/neutron-lib/+/83193516:05
opendevreviewBalazs Gibizer proposed openstack/neutron master: Update port MAC from binding profile for PFs  https://review.opendev.org/c/openstack/neutron/+/82924716:06
opendevreviewLajos Katona proposed openstack/tap-as-a-service master: Code cleaning: make RPC method signatures more meaningful  https://review.opendev.org/c/openstack/tap-as-a-service/+/83343216:15
opendevreviewBalazs Gibizer proposed openstack/neutron-lib master: Add port-mac-address-override shim extension  https://review.opendev.org/c/openstack/neutron-lib/+/83193516:24
opendevreviewBalazs Gibizer proposed openstack/neutron master: Update port MAC from binding profile for PFs  https://review.opendev.org/c/openstack/neutron/+/82924716:26
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider master: Avoid loadbalancer stuck in PENDING_X if delete_vip_port fails  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83433517:05
opendevreviewMiguel Lavalle proposed openstack/ovn-octavia-provider master: Remove incorrect character in f-string  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83434518:09
*** jlibosva is now known as Guest250218:23
hjensasI have a question regarding black magic retrying in neutron ML2 drivers. If the driver knows it failed in a non-recoverable way, how can the driver raise an exception that won't be retried?20:40
hjensasp20:42

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