Tuesday, 2021-11-23

opendevreviewYi Yang proposed openstack/neutron master: Set network namespace and tap interface type in case of OVS DPDK  https://review.opendev.org/c/openstack/neutron/+/81833801:34
opendevreviewYi Yang proposed openstack/neutron master: Set network namespace and tap interface type in case of OVS DPDK  https://review.opendev.org/c/openstack/neutron/+/81833801:35
opendevreviewGhanshyam proposed openstack/neutron master: DNM: test tempest train-last tag  https://review.opendev.org/c/openstack/neutron/+/81884401:41
opendevreviewTerry Wilson proposed openstack/neutron master: WIP Use neutron db for ovn agents  https://review.opendev.org/c/openstack/neutron/+/81885003:58
opendevreviewBernard Cafarelli proposed openstack/networking-ovn stable/train: Fix race condition retrieving logical router rows  https://review.opendev.org/c/openstack/networking-ovn/+/81082008:14
opendevreviewyangjianfeng proposed openstack/neutron master: Improve Router callback system's publish events  https://review.opendev.org/c/openstack/neutron/+/80484608:28
opendevreviewyangjianfeng proposed openstack/neutron master: [Server Side] L3 router support ndp proxy  https://review.opendev.org/c/openstack/neutron/+/74314208:28
opendevreviewOleg Bondarev proposed openstack/neutron master: Allow to use static Local IP openflow rules  https://review.opendev.org/c/openstack/neutron/+/81739908:50
opendevreviewOleg Bondarev proposed openstack/neutron master: Allow to use static Local IP openflow rules  https://review.opendev.org/c/openstack/neutron/+/81739908:51
*** ykarel is now known as ykarel|lunch09:21
opendevreviewSlawek Kaplonski proposed openstack/neutron-tempest-plugin master: Remove ussuri jobs from the project's CI queues  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81868810:03
*** blmt is now known as Guest659710:08
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [Fullstack] Don't install OVN in the fullstack job  https://review.opendev.org/c/openstack/neutron/+/81887710:38
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP policy rules  https://review.opendev.org/c/openstack/neutron/+/81643511:36
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP fullstack test case  https://review.opendev.org/c/openstack/neutron/+/81632711:36
opendevreviewPrzemyslaw Szczerbik proposed openstack/neutron master: Update placement allocation of bound ports when network QoS policy is changed  https://review.opendev.org/c/openstack/neutron/+/81888912:02
*** ykarel|lunch is now known as ykarel12:05
opendevreviewMerged openstack/neutron stable/xena: [ovn] Add timeout option to ovsdb-client command  https://review.opendev.org/c/openstack/neutron/+/81879612:15
opendevreviewyatin proposed openstack/neutron master: Fix tunnel_types in ml2 ovs sample config  https://review.opendev.org/c/openstack/neutron/+/81891112:40
*** ykarel is now known as ykarel|afk12:41
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP fullstack test cases  https://review.opendev.org/c/openstack/neutron/+/81632713:14
opendevreviewMerged openstack/neutron stable/victoria: [ovn] Add timeout option to ovsdb-client command  https://review.opendev.org/c/openstack/neutron/+/81880013:14
opendevreviewPrzemyslaw Szczerbik proposed openstack/neutron-tempest-plugin master: QoS min pps API tests  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/80668913:22
opendevreviewPrzemyslaw Szczerbik proposed openstack/neutron-tempest-plugin master: Fix test_port_resource_request_inherited_policy test  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81735613:22
opendevreviewPrzemyslaw Szczerbik proposed openstack/neutron-tempest-plugin master: Update PortTestCasesResourceRequest for new Neutron API ext  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81735713:22
opendevreviewPrzemyslaw Szczerbik proposed openstack/neutron-tempest-plugin master: Test port.resource_request format with min bw and min pps rules  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81735813:22
opendevreviewRodolfo Alonso proposed openstack/neutron stable/wallaby: [OVN] External network ports (SR-IOV) QoS is handled by SR-IOV agent  https://review.opendev.org/c/openstack/neutron/+/81892213:56
lajoskatona#startmeeting networking14:00
opendevmeetMeeting started Tue Nov 23 14:00:17 2021 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 'networking'14:00
mlavalleo/14:00
lajoskatonaHi everybody!14:00
slaweqhi14:00
obondarevhi14:00
rubasovo/14:00
bcafarelo/14:01
lajoskatonaok, let's start14:02
ralonsohhi14:02
lajoskatona#topic Announcements14:02
*** ykarel|afk is now known as ykarel14:02
lajoskatonaFirst the meeting times: it seems that the best would be to keep all meetings untouched so keep the current time slots14:03
lajoskatonaTeam meeting :Tuesday 1400UTC14:03
lajoskatonaCI meeting Tuesday 1500TC14:03
mlavalle+1 Good for me14:03
lajoskatonaDrivers meeting Friday 1400UTC14:03
lajoskatonagood :-)14:04
lajoskatonaIf you have any comments please answer to the mails I sent today.14:04
slaweqso all stays like it was14:06
slaweq:)14:06
slaweqgood for me14:06
lajoskatonaIt would be good to have more people from "the east" India, central asia, east asia, but hard to find good timeslot14:06
bcafarelno need to update my calendar, good for lazy me14:06
obondarev:)14:06
lajoskatonaNova as I know experienced with a special east asian meeting slot or more an "office-hour" but not much success14:06
lajoskatonabcafarel: yeah true :-)14:07
slaweqin neutron we had in the past 2 different time slots for the meetings which were biweekly14:07
liuyulongNothing changed, good to know, p.s. 1400 UTC is 10 p.m. in Beijing. Many times, I had already go to bed. 14:07
slaweqbut we changed that as there was not a lot of people attending one of them14:07
lajoskatonaYeah I remember, was that more visited?14:07
lajoskatonaliuyulong: Hi, I totally understand that14:08
slaweqlajoskatona: I remember that on the meeting which was around midnight my time there was maybe 2 or 3 people14:08
slaweqso I changed that finally to have it always on Tuesday14:08
lajoskatonaslaweq: ok14:08
lajoskatonayeah that was too late for me, and if I had no special topic for it I just skipped as I remember :-)14:09
lajoskatonaok, I think we can jump to the next point14:10
lajoskatonaYoga cycle calendar https://releases.openstack.org/yoga/schedule.html14:10
lajoskatonathe Yoga-1 release patches are out (i.e.: https://review.opendev.org/c/openstack/releases/+/818428 or https://review.opendev.org/c/openstack/releases/+/818417 )14:11
liuyulongToo many running OpenStack clouds need me to take care in daytime. So, I have to go bed earlier to recover. : )14:11
lajoskatonaLast week the ussuri branch was transitioned to em: https://review.opendev.org/c/openstack/releases/+/81760514:12
lajoskatonaand networking-midonet: transition pike, queens and rocky to eol14:13
lajoskatonaThere was a mail for testing runtime: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025881.html14:14
lajoskatonaTC decided to remove py36 from jobs and as py39 voting everywhere14:14
lajoskatonaas I saw we have no problem with py39, do you know something to focus on regarding py39 jobs?14:15
slaweqI think it should be ok14:15
lajoskatonaslaweq: ok14:15
slaweqaccording to https://grafana.opendev.org/d/BmiopeEMz/neutron-failure-rate? viewPanel=22&orgId=1&from=now-30d&to=now it seems that now it's following other ut jobs14:16
slaweqbut about 1-2 weeks ago it was failing much more often than e.g. py36 or 3814:16
slaweqso we will need to keep an eye on it14:16
ralonsoh(dut to timeouts, seems that py39 takes more time)14:16
slaweqralonsoh: can be14:17
lajoskatonaso grfana dashbourd should be updated perhaps to have py39 on it? I see only py3814:18
slaweqlajoskatona: there is openstack-tox-py39 there14:19
slaweqas non-voting job14:19
slaweqso we will only need to update it to be "voting"14:20
slaweqand add to the gate queue graph14:20
lajoskatonaslaweq: ok I see now, the board half loaded for me it seems for first....14:20
lajoskatonaok, if no comments/questions for announcements, we can go to next topic14:21
lajoskatona#topic Bugs14:21
bcafarelyep py39 looks in line with other UT jobs in recent days14:21
lajoskatonahongbin was bug deputy last week: http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025895.html14:21
* frickler has been busy filing bugs with OVN+DNS14:22
lajoskatonaI checked and the found few without owner:14:22
lajoskatona#link https://bugs.launchpad.net/neutron/+bug/1951010  Restarting Neutron floods Nova with segment aggregates calls14:22
lajoskatonafrickler: thanks for filing those14:23
lajoskatonaI think this is one of those: #link https://bugs.launchpad.net/neutron/+bug/1951074  [OVN] default setting leak nameserver config from the host to instances14:24
lajoskatonaDo you have perhaps comments or notes for the bug report?14:25
fricklerI think it's all written there, I open to any questions as always14:26
lajoskatonaok14:26
fricklerthis search has all others, too 14:27
fricklerhttps://bugs.launchpad.net/neutron/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&fi14:27
fricklereld.subscriber=&field.structural_subscriber=&field.tag=ovn+dns&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_bluepr14:27
mlavallelajoskatona: I can take a look at  "Restarting Neutron floods Nova with segment aggregates calls"14:27
fricklerints=on&search=Search14:27
lajoskatonamlavalle thanks14:27
frickleroops, that's a long lp link. essentially look for tags "ovn"+"dns"14:27
frickler#link https://bugs.launchpad.net/neutron/+bugs?field.tag=ovn+dns&field.tags_combinator=ALL14:29
lajoskatonafrickler: thanks, thats much more friendly :-)14:31
fricklerI'm really thinking having a flag to disable all this DNS spoofing and just using dhcp-agent for that would be great14:31
lajoskatonaFor this week haleyb changed with ralonsoh to be deputy I think, at least I have seen something on irc14:32
ralonsohyes14:32
haleybyes, i'm out after today, thanks ralonsoh 14:32
lajoskatonafrickler: I think that was mentioned earlier as workaround, so perhaps it should be documented somewhere14:32
lajoskatonahaleyb, ralonsoh: thanks I will update the table on the meetings wiki page14:33
fricklerlajoskatona: I'm currently testing running with dhcp-agent, but I haven't found out how to disable the OVN spoofing part14:33
lajoskatonaNext week I will be the deputy14:33
lajoskatonaok I think if there's no more comments for bugs we can jump14:35
lajoskatona#topic L3 subteam14:35
lajoskatona#link https://wiki.openstack.org/wiki/Network/Meetings#L3_subteam14:35
lajoskatonaliuyulong: if you are still with us, do you have anything related to L3?14:36
liuyulongone topic14:36
liuyulong#link https://review.opendev.org/c/openstack/neutron-specs/+/77054014:36
liuyulongWhat do you guys think about this spec of "elastic snat"?14:36
liuyulongShould we move forward?14:37
lajoskatonaliuyulong: from my side the idea is really good and as I see the review moved to fix small things in the spec14:37
lajoskatonaI plan to go back and check the last ps14:38
liuyulongIt has been 9 month for this spec. Pretty slow in progress. : )14:39
lajoskatonathat's true14:40
slaweqI will review it again14:40
liuyulongGood, thank you guys.14:41
liuyulongNew features are always weclomed for cloud users. : ) This is also one of the sign of the activity of the community.14:42
mlavalleI will review it also14:42
lajoskatonathanks you very much for the update and headsup14:43
liuyulongSomething in short, port forwarding is the DNAT work, while this is SNAT.14:44
liuyulongThe two features have some similarities.14:44
liuyulongOK, no more from me, please move on.14:46
lajoskatona liuyulong: thanks14:46
lajoskatona#topic ryu and os-ken14:46
ralonsohNo updates in Ryu repo, still following the open bugs in this project.14:46
lajoskatonathere was no new change so we have nothing to do with os-ken14:46
lajoskatonaralonsoh: thanks for following it14:47
lajoskatona#topic On Demand Agenda14:47
ralonsohI have one14:47
ralonsohhttps://review.opendev.org/c/openstack/neutron/+/81839914:47
ralonsohI don't want to hijack this meeting14:47
ralonsohso I would like your comments in the review14:48
ralonsohthose are the current options14:48
ralonsoh1) add a config knob (config driven API)14:48
ralonsoh2) use the upgrade check to emit a warning --> admin will need to change needed policies14:48
ralonsoh3) something else14:48
* mlavalle added the patch to reviews pile14:48
slaweqI already commented there and I'm for option 2 personally14:49
liuyulongI guess you had read my last comment, from my actual cloud operation experience, it's better to let the cloud admins know things explicitly.14:50
slaweqliuyulong: not yet14:50
opendevreviewmitya-eremeev-2 proposed openstack/neutron-tempest-plugin master: Set SG quota for specific project.  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81893314:50
slaweqbut ralonsoh's option 2 gives such possibility, only not with config knob14:50
ralonsohthey'll have this option when executing the upgrade check14:51
slaweqadmin can configure qos policy for ports from external network and then remove policy from the network itself14:51
liuyulongalright, maybe we can continue the disscussion in the gerrit.14:51
ralonsohthey'll have the information about (1) the external networks affected, (2) the FIPs and (3) the fixed ports in those networks14:51
ralonsohsure14:51
slaweqthus nothing will really change and behaviour will be finally consistent with what is now for ports14:51
slaweqI don't think that config option for that will help14:52
slaweqthis would be config driven api behaviour which IMO we shouldn't do14:52
lajoskatonaIt is open for me as well , I will check the discussion under the review14:52
ralonsohthank you all14:53
slaweqand if we will keep it by default as it was until now, nobody will notice that really14:53
slaweqso everyone will still probably use it in old way14:53
mlavallegood point14:53
liuyulongmaybe a add floating_qos_polidy_id to external network for the floating IPs to inherit, to save the tons of API for existing ports.14:55
slaweqIMO that will not be good ux to have yet another qos policy parameter to set14:56
ralonsohthat will fragment the API unnecessarily14:56
liuyulongThen you mixed L2 qos to L3 IPs.14:56
slaweqI think we should keep that API as consistent as possible14:56
ralonsohlajoskatona, as is new14:56
ralonsohas  is now*14:56
slaweqin fact I think that this is kind of bug that it now works differently for FIPS only14:56
lajoskatonayeah I think the good way to have similar behaviour for ports networks and fips, gw port etc...14:58
lajoskatonaok, time is up, so I think we have to move this discussion back to gerrit :-)14:59
mlavalleI have a personal announcement to make. I am leaving my position with Yahoo, to join bcafarel's team at Red Hat, starting this coming Monday. From the community Neutron project point of view, it means I'll continue working with y'all14:59
ralonsohwelcome!14:59
bcafarelyay :)14:59
liuyulongfloating_ip_qos_policy_id to external network can solve the problems with varity cloud settings.14:59
lajoskatonamlavalle: good luck:-)14:59
lajoskatonamlavalle: you move to France? :P15:00
liuyulongcongras!15:00
lajoskatona#endmeeting15:00
opendevmeetMeeting ended Tue Nov 23 15:00:21 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-23-14.00.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-23-14.00.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2021/networking.2021-11-23-14.00.log.html15:00
mlavalleThanks!15:00
lajoskatonaBye15:00
slaweq\o/15:00
slaweqand by :)15:00
slaweq#startmeeting neutron_ci15:01
opendevmeetMeeting started Tue Nov 23 15:01:05 2021 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'neutron_ci'15:01
ralonsohhi15:01
slaweqand welcome again :D15:01
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate15:01
obondarevhi15:02
lajoskatonaHi15:02
slaweqok, lets start15:02
slaweq#topic Actions from previous meetings15:03
slaweqlajoskatona to check why make FIP down took more than 120 seconds in the L3 agent15:03
slaweqit was from two weeks but lajoskatona wasn't there last week15:03
slaweq:)15:03
lajoskatonaI havent worked on it last week, sorry....15:03
bcafarelo/ again15:03
lajoskatonaThe logs are open, but havent diged in them....15:04
ykarelo/15:04
slaweqhi ykarel :)15:04
obondarevdoes it still happen in the gates?15:04
slaweqlajoskatona: ok, so should I assign it to You this week?15:05
slaweqobondarev: yes, I saw it last week once: https://08d14f4ddffb82b199e7-61a732188f1643f755755f84f6310584.ssl.cf1.rackcdn.com/817525/7/check/neutron-tempest-plugin-scenario-linuxbridge/e4b6cfb/testr_results.html15:05
lajoskatonayes, I have to check it to close those tabs in the browser fially ;)15:05
slaweq#action lajoskatona to check why make FIP down took more than 120 seconds in the L3 agent15:05
obondarevslaweq: ack15:05
lajoskatonaslaweq: thanks15:05
slaweqok, next one15:06
slaweqslaweq to remove ussuri jobs from neutron-tempest-plugin queues15:06
slaweq    Patch https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/81868815:06
slaweq    And it requires https://review.opendev.org/c/openstack/releases/+/81868715:06
slaweqplease review them when You will have few minutes15:07
slaweqnext one15:07
slaweqslaweq to open LP for issue with neutron.tests.functional.plugins.ml2.drivers.ovn.mech_driver.ovsdb.test_ovsdb_monitor.TestAgentMonitor.test_network_agent_present15:07
slaweq    Done: https://bugs.launchpad.net/neutron/+bug/195122515:07
ralonsohBTW, we are currently working (again) on a refactor of the OVN agent code15:07
slaweqjlibosva is already taking care of it15:07
ralonsohthat could affect to this test15:07
ralonsohso I'll ping him then15:08
slaweqI saw it couple of times this week again15:08
obondarev+115:08
slaweqnext one15:08
slaweqslaweq to check failed neutron.tests.functional.agent.l3.test_keepalived_state_change.TestMonitorDaemon.test_handle_initial_state_backup15:08
slaweqI didn't had time (still)15:08
slaweqI will try to check it this week15:09
slaweq#action slaweq to check failed neutron.tests.functional.agent.l3.test_keepalived_state_change.TestMonitorDaemon.test_handle_initial_state_backup15:09
slaweqand last one15:09
slaweqslaweq to send email about rechecks numbers to the ML15:09
slaweqI did http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025813.html15:09
slaweqand there is good feedback there15:09
slaweqI will collect all of that for next week's meeting and we can discuss all ideas during the meeting next week15:09
ralonsohslaweq++15:10
slaweq#topic Stable branches15:10
slaweqbcafarel: any updates?15:10
lajoskatonathe release team is now busy with yoga-1 I suppose so perhaps the release patch will be slow to land, I will ping them to be sure15:10
bcafareloverall quite good this week15:11
lajoskatonasorry this is for the tempest-plugin stuff15:11
slaweqlajoskatona: thx15:11
bcafarelwith https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/817933 merged (thanks slaweq) for older branches15:11
slaweqgood to hear that15:11
bcafarelfor rocky we may need to update a bit the filtered out tests https://review.opendev.org/c/openstack/neutron/+/808502 has a lot of rechecks15:11
slaweqyeah, I saw it15:11
bcafarelbut >=stein are quite good, and queens too so only one branch :)15:12
lajoskatonaby the way I have this stein patch for odl: https://review.opendev.org/c/openstack/networking-odl/+/81838415:12
slaweqit's for rocky, not stein :)15:13
slaweqI think stein was merged recently, no?15:13
lajoskatonaoh really the stein one is merged....15:13
slaweqI will review that one tomorrow15:14
lajoskatonathanks15:14
slaweqso if that's all for stable branches, we can move on to the next topic15:14
slaweq#topic Stadium projects15:14
lajoskatonano news from them15:15
slaweqok, lets move on15:16
slaweq#topic Grafana15:16
slaweqfrom good news - scenario jobs are suprisely good recently :)15:17
slaweqbut there is bad news also:15:17
slaweqit seems that functional tests are failing often again15:17
slaweqand UT are also on high failure rate last few days15:18
ralonsohthat could be due to failed patches15:19
obondarevI also didn't see failed UT unrelated to the patch recently15:19
slaweqralonsoh: yes, when I was checking specific patches from last week I noticed that15:19
slaweqthere was a lot of patches with broken UT really because of the patch15:19
slaweqso I think we just need to keep an eye on it for next days15:19
slaweqbut I also noticed few times timeout in the lower-constraints job, like:15:20
slaweq    https://zuul.opendev.org/t/openstack/build/93fa264c3b0e482590369e8b31fa7546/logs15:20
slaweq    https://zuul.opendev.org/t/openstack/build/b73ff16dc4ec4606a3244ee36f699b43/logs15:20
slaweq    https://zuul.opendev.org/t/openstack/build/bba203de96d54d95be30b7309a902a3815:20
lajoskatonathe l-c job timout was not increased last time?15:21
ralonsohI don't think so15:21
lajoskatonaok15:21
slaweqso maybe we should increase it too?15:21
slaweqas for other jobs?15:21
ralonsohyes15:22
lajoskatonayes15:22
lajoskatonaI can push it for review15:22
obondarevit should be connected to UT timeout + some gap for coverage stuff15:22
lajoskatonaobondarev: +115:22
obondarevas far as I understand15:22
ralonsohright15:23
opendevreviewTerry Wilson proposed openstack/neutron master: WIP Use neutron db for ovn agents  https://review.opendev.org/c/openstack/neutron/+/81885015:23
slaweqthx15:24
slaweq#action lajoskatona to increase timeout of the lower-constraints job in neutron15:24
slaweqok, lets move on15:25
slaweq#topic fullstack/functional15:25
slaweqin functional tests I saw mostly issues with those ovn agent tests15:25
slaweqralonsoh: maybe we should mark those tests as unstable temporary until jlibosva will fix it?15:25
slaweqwdyt?15:25
ralonsohok15:26
slaweqok, can You propose patch for that?15:26
ralonsohsuer15:26
ralonsohsure15:26
slaweqthx a lot15:26
jlibosvais it reproducible well in the gate? I ran functional tests several times locally and didn't hit it even single time15:26
slaweqjlibosva: maybe not "well" but it happens pretty often I would say15:26
slaweqlike e.g.: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_db9/816856/6/check/neutron-functional-with-uwsgi/db9ba2c/testr_results.html15:27
slaweqprobably You can find other similar examples15:27
ralonsohI'll do15:27
slaweqthx ralonsoh 15:27
obondarevanother: https://2636029923414340a2c8-da9bd67ce2281bb41bf3df3e007407f6.ssl.cf1.rackcdn.com/818067/2/check/neutron-functional-with-uwsgi/d20e295/testr_results.html15:29
ralonsohin any case, I'll wait to the OVN agent refactor15:29
opendevreviewyatin proposed openstack/neutron master: Fix tunnel_types in ml2 ovs sample config  https://review.opendev.org/c/openstack/neutron/+/81891115:29
slaweqthx obondarev 15:29
slaweqand that's basically only issue which I saw that was repeating last week in the functional job15:30
slaweqregading fullstack, I proposed small improvement today https://review.opendev.org/c/openstack/neutron/+/81887715:30
slaweqplease check when You will have time15:30
jlibosvait looks like the problem there is that OVN event gets processed before mech driver initialization is completed - which the agent refactor will fix only for the agent but will not fix the root cause of it15:30
obondarevnot sure it it's the same: https://7bed286b1abc124aef60-716c2febf7f730d66787c22f3ed0da3e.ssl.cf5.rackcdn.com/818067/2/check/neutron-functional-with-uwsgi/48adb0f/testr_results.html15:31
obondarevseems some other issue15:31
jlibosvaobondarev: that looks like max_tunid is missing in NB_Global table when creating network -15:32
jlibosvahttps://7bed286b1abc124aef60-716c2febf7f730d66787c22f3ed0da3e.ssl.cf5.rackcdn.com/818067/2/check/neutron-functional-with-uwsgi/48adb0f/controller/logs/dsvm-functional-logs/neutron.tests.functional.plugins.ml2.drivers.ovn.mech_driver.test_mech_driver.TestProvnetPorts.test_network_segments_localnet_ports/testrun.txt15:32
slaweqobondarev: isn't that related to https://bugs.launchpad.net/neutron/+bug/1903008 ?15:33
slaweqor maybe it's something new15:34
obondarevslaweq: not sure, sorry15:34
slaweqit seems that the stacktrace is different there15:36
slaweqI will check it15:36
slaweq#action slaweq to check https://7bed286b1abc124aef60-716c2febf7f730d66787c22f3ed0da3e.ssl.cf5.rackcdn.com/818067/2/check/neutron-functional-with-uwsgi/48adb0f/testr_results.html15:36
slaweqok, I think we can move on to the next topics now15:38
slaweq#topic Tempest/Scenario15:38
slaweqhere, I found 2 or 3 times same test failing neutron_tempest_plugin.scenario.test_mac_learning.MacLearningTest in the ovn scenario job15:38
slaweq    https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_b75/815962/5/check/neutron-tempest-plugin-scenario-ovn/b75474f/testr_results.html15:38
slaweq    https://b30211aa4f809fc4a91b-baf4f807d40559415da582760ebf9456.ssl.cf2.rackcdn.com/817525/7/check/neutron-tempest-plugin-scenario-ovn/c356679/testr_results.html15:38
slaweqI think we should investigate why in that test ssh is not working from time to time15:39
slaweqmaybe it's coincidence, idk really15:39
slaweqanyone want's to investigate that?15:39
slaweqok, if I will have time, I will try to check it15:41
slaweqif not, let's wait for next week :)15:41
slaweqI will also report LP for that15:41
slaweq#action slaweq to report bug about failing neutron_tempest_plugin.scenario.test_mac_learning.MacLearningTest15:41
slaweqand that's all what I had prepared for You for today15:41
slaweqwe have one on demand topic15:42
slaweq#topic On Demand15:42
slaweqlajoskatona: move on with what You wanted to discuss15:42
lajoskatonait's about gate load15:42
lajoskatonahistory: beginning of this year a list was sent with data that Neutron is one of the biggest user of gate resources, and I asked clarkb if we can repeat the execution15:44
lajoskatonahttps://paste.opendev.org/show/bYTlHXfbX84aESK6cLMM/15:44
ralonsoh(I feel myself guilty looking at those figures)15:45
lajoskatonathe issue is that due to some zuul changes this is for only one executor so we have to have some other way to have real data for project's resource usage15:45
slaweqbut it's clear for me that neutron is still in the very top of that list :/15:45
lajoskatonaIn theory everything is availabel on https://graphite.opendev.org/15:45
lajoskatonayeah with clarkb we checked on graphite and the results from there correlate with the paste15:46
obondarevand that's why we started this 'rechecks' brainstorm, right?15:47
lajoskatonathe suggestion is to create a grafana dashboard, which I started: https://review.opendev.org/c/openstack/project-config/+/81823015:47
lajoskatonathe issue with it is mostly my lack of grfana background :-)15:47
slaweqI can't help with that :)15:48
slaweqsorry15:48
lajoskatonaI suppose if we have fresh data from this we could better act to things like we have a lot of rechecks, and more jobs than other projects15:49
obondarev+115:49
obondarevand to track out progress with improving those numbers15:50
obondarevour*15:50
slaweq+!15:50
slaweq+115:50
slaweq:)15:50
ralonsohyes, good idea15:50
slaweqthx for taking care of it lajoskatona 15:50
ralonsohand waiting for slaweq's summery15:50
lajoskatonaok, I will ask around to improve this dashboard and we can check that regularly15:50
slaweq++15:51
opendevreviewTerry Wilson proposed openstack/neutron master: WIP Use neutron db for ovn agents  https://review.opendev.org/c/openstack/neutron/+/81885015:51
lajoskatonayeah I will answer for that mail too :-)15:51
slaweqok, I think we are good with that topic for now15:52
slaweqanything else You want to discuss today?15:52
lajoskatonanothing from me15:52
ralonsohnothing, thanks15:52
bcafarelall good too15:53
slaweqif not, we can finish the meeting I guess :)15:53
slaweqthx for attending the meeting today15:53
slaweqand have a great week15:53
obondarevbye everyone!15:53
slaweq#endmeeting15:53
opendevmeetMeeting ended Tue Nov 23 15:53:29 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-23-15.01.html15:53
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-23-15.01.txt15:53
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_ci/2021/neutron_ci.2021-11-23-15.01.log.html15:53
lajoskatonao/15:53
ralonsohbye15:53
ykarelslaweq, https://etherpad.opendev.org/p/neutron-ci-meetings is the etherpad for this meeting, right?15:53
slaweqykarel: yes, that's agenda for that meeting15:54
ykarelokk there i see place:  #openstack-meeting-3, should be updated15:54
ykarelearlier i joined in that channel15:54
slaweqykarel: thx, good catch15:55
slaweqI forgot to update it :)15:55
ykarelnp :)15:55
*** ykarel is now known as ykarel|away15:55
opendevreviewMerged openstack/neutron stable/wallaby: [ovn] Add timeout option to ovsdb-client command  https://review.opendev.org/c/openstack/neutron/+/81879915:56
opendevreviewOleg Bondarev proposed openstack/neutron master: Add Local IP fullstack test cases  https://review.opendev.org/c/openstack/neutron/+/81632715:56
opendevreviewRodolfo Alonso proposed openstack/neutron master: Replace "target_tenant" with "target_project" in RBAC OVOs and models  https://review.opendev.org/c/openstack/neutron/+/81585516:11
opendevreviewTerry Wilson proposed openstack/neutron master: WIP Use neutron db for ovn agents  https://review.opendev.org/c/openstack/neutron/+/81885016:21
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Check new added segments in OVN mech driver  https://review.opendev.org/c/openstack/neutron/+/81685616:21
opendevreviewElvira GarcĂ­a Ruiz proposed openstack/networking-ovn stable/train: Enhanced set of warnings if an answers file or a templates directory is used.  https://review.opendev.org/c/openstack/networking-ovn/+/81898516:27
prometheanfireshould the job timeout be increased on wallaby too? https://review.opendev.org/81872916:53
erlonralonsoh, hey17:45
erlonso, I'm still trying to get the OVN FIP to work, there's not L3 agent to set the extensions for OVN right?17:46
erlonso, where do you set it?17:46
ralonsoherlon, no, there is no agent. But you need to define the qos-fip extension17:47
erlonralonsoh: where? on neutron.conf?17:47
ralonsohnot extension, plugin17:47
erlonit seems to ignore it17:48
ralonsohhow is your config file?17:48
erlonralonsoh: https://editor.mergely.com/7OBhOF8d/17:49
erlonleft is ovs, right ovn17:50
erlonignore the header comment "#ussuri"17:50
ralonsohdo you see something like this?17:50
ralonsohDEBUG neutron.api.extensions [None req-3b484393-130a-40bb-a700-163430778816 None None] Loading extension file: qos_fip.py {{(pid=371648) _load_all_extensions_from_path /opt/stack/neutron/neutron/api/extensions.py:450}}17:50
ralonsohDEBUG neutron.api.extensions [None req-3b484393-130a-40bb-a700-163430778816 None None] Ext name="Floating IP QoS" alias="qos-fip" description="The floating IP Quality of Service extension" updated="2017-07-20T00:00:00-00:00" {{(pid=371648) _check_extension /opt/stack/neutron/neutron/api/extensions.py:416}}17:50
ralonsohINFO neutron.api.extensions [None req-3b484393-130a-40bb-a700-163430778816 None None] Loaded extension: qos-fip17:50
ralonsohwhen Neutron server starts17:50
erlonlet grep it17:52
erlonralonsoh: yes17:54
erlon'2021-11-23 16:40:15.482 485289 DEBUG neutron.api.extensions [req-47dff3e6-3371-483e-a076-f6a18591578d - - - - -] Ext name="Floating IP QoS" alias="qos-fip" description="The floating IP Quality of Service extension" updated="2017-07-20T00:00:00-00:00" _check_extension /usr/lib/python3/dist-packages/neutron/api/extensions.py:416'17:54
erlonvery same line17:54
ralonsohand "Starting OVNClientQosExtension" 17:55
erlonthat one too17:56
ralonsohthen try to add a qos policy with a bw-limit rule17:56
ralonsohand assign this qos to a FIp17:57
ralonsohthen search in the OVN NB DB17:57
ralonsoh$ ovn-nbctl find qos17:57
erlonralonsoh: neutron is not adding it for the fip port18:03
erlonI can see it qhen I add in the internal port though18:04
ralonsohwhat can you see?18:04
opendevreviewMerged openstack/networking-ovn stable/train: [ovn] Add timeout option to ovsdb-client command  https://review.opendev.org/c/openstack/networking-ovn/+/81880318:04
ralonsohok, maybe I didn't say that the FIP must be assigned to a router (that means it must have a fixed port)18:06
ralonsohthe FIP will have a router18:06
ralonsohand therefore an exit port18:06
ralonsoha "resident_port"18:06
ralonsohthis is needed to set the qos rules on this port, linked to the FIP IP address18:07
erlonthis after I added in the fixed ip port: 18:07
erlonhttps://gist.github.com/sombrafam/eef5271996a4395845ded8e4f8c1f13918:07
ralonsoherlon, exactly18:07
erlonbefore it was empty18:08
ralonsohas commented, the FIP must have a fixed port18:08
ralonsohthan means it is associated to a router18:08
ralonsohand it has a resident port18:08
ralonsohon this port OVN applies the qos rules18:08
ralonsohyou'll see that better here18:08
ralonsohhttps://github.com/openstack/neutron/blob/4b1bf15f7bfae842669b61400c5469a6d7269eb6/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/extensions/qos.py#L279-L31218:09
opendevreviewRodolfo Alonso proposed openstack/neutron master: [WIP] [OVN][Placement] Drive binding by placement allocation  https://review.opendev.org/c/openstack/neutron/+/78647818:13
ralonsoherlon, anything else? I'm going to disconnect, is a bit late for me18:16
erlonralonsoh: Im trying to understand how to link the port to the FIP18:17
ralonsoh?18:17
ralonsohwhat do you mean?18:17
erlonI mean, to assign the FIP to a router18:17
ralonsohno no18:17
ralonsohyou don't assign a FIP to a router18:17
ralonsohyou create a FIP in an external network18:17
erlonright18:18
ralonsohthen you create a router linking the private network and the public network18:18
ralonsohnot public, external18:18
erlonI have that18:18
ralonsohand then you assign the port to the FIP18:18
erlonwithout that the vms will not even talk externally18:18
ralonsohright18:18
ralonsohwell no18:19
ralonsohyou can use nating18:19
ralonsohyou don't need a FIP to access to internet18:19
erlontrue, I can, but when I assign a fip to the vm it will not use nat anymore18:19
ralonsohyou'll have DNAT18:20
ralonsohhttps://docs.openstack.org/python-openstackclient/pike/cli/command-objects/floating-ip.html18:20
ralonsohthis is the CLI for floating IPs18:20
ralonsohhttps://docs.openstack.org/python-openstackclient/pike/cli/command-objects/floating-ip.html#floating-ip-set18:20
ralonsohto set a port or a fixed IP18:20
erlonhmm18:20
erlonso, Ill not hold you anymore18:21
ralonsohsee you 18:21
erlonIll keep trying and let you know tomorrow18:21
erlonbut thanks a lot for now!18:21
ralonsohyw18:21
opendevreviewMerged openstack/neutron stable/ussuri: [ovn] Add timeout option to ovsdb-client command  https://review.opendev.org/c/openstack/neutron/+/81880118:59
*** jamesdenton_alt is now known as jamesdenton20:12
opendevreviewJakub Libosvar proposed openstack/neutron master: ovn: Wait for northd in functional tests  https://review.opendev.org/c/openstack/neutron/+/81903222:30

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