Friday, 2022-10-28

opendevreviewliuhuajie proposed openstack/neutron master: Refactor generate address pools by cidr  https://review.opendev.org/c/openstack/neutron/+/86221702:52
opendevreviewMerged openstack/networking-odl master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/networking-odl/+/85799707:17
*** cstone5 is now known as cstone08:07
*** carloss_ is now known as carloss08:07
*** andrewbonney_ is now known as andrewbonney08:07
*** open10k8s_ is now known as open10k8s08:07
*** erbarr_ is now known as erbarr08:07
*** TheJulia_ is now known as TheJulia08:07
*** gouthamr_ is now known as gouthamr08:07
*** PrinzElvis_ is now known as PrinzElvis08:07
*** chateaulav_ is now known as chateaulav08:07
elodillesralonsoh: with lajoskatona we just checked the stable/wallaby state of neutron and we see that neutron (any maybe 1 or 2 other repo) could have a final release before the EM transition (see the patch: https://review.opendev.org/c/openstack/releases/+/862333 )08:34
elodillesralonsoh: does the neutron team plan a release for these? (next week is the transition deadline)08:34
elodillesralonsoh: no worries if that is not planned as things can be consumed from EM branches (downstream) as well, though (but no upstream release is possible after the transition)08:36
ralonsohelodilles, yes, I'm now checking this08:37
ralonsohhttps://review.opendev.org/c/openstack/releases/+/677478/08:37
ralonsohto EOL up to Stein08:37
ralonsohI'll push this patch today08:37
elodillesyepp, EOL'ing old stable branches. that's another story :) let me know if you need help08:38
ralonsohelodilles, we didn't discuss about EM wallaby08:39
ralonsohshould we?08:39
elodillesralonsoh: these 4 easy steps need to be followed: https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life08:39
ralonsohelodilles, ok, I'll work on both issues, but first Wallaby08:40
elodillesfor EOL08:40
elodillesfor wallaby: 08:40
elodilleshttps://lists.openstack.org/pipermail/openstack-discuss/2022-October/030937.html08:40
ralonsoh(this is all new for me)08:40
elodillesit's worth to follow the [release] and [ptl] tags on openstack-discuss to see these kind of things08:41
ralonsohyeah, I know08:41
elodillesand don't worry, feel free to ask if you have any question :)08:42
lajoskatonaralonsoh: I am bad with these rules, but I can help :-)08:42
ralonsohelodilles, that applies to other neutron related projects?08:42
ralonsohfwaas, neutron-lib, etc?08:42
ralonsohthe wallaby EM?08:42
elodillesralonsoh: all deliverables that are owned by neutron team08:43
ralonsohunderstood08:43
elodillesso everything that is listed in the patch ( https://review.opendev.org/c/openstack/releases/+/862333 )08:44
ralonsohyeah, I had the same opened08:44
ralonsohI'll update it now08:44
elodillesralonsoh: don't need to update, if there are no new release08:45
bcafarelltomasbo: froyo_ ^^ any backports you want to send for ovn-octavia-provider wallaby before EM? I just W+1 https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258509:08
froyo_bcafarel: on my side are all of them! thx09:09
ltomasbobcafarel, I have one extra one I          need09:10
ltomasbobcafarel, this one: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86078109:11
bcafarelltomasbo: ack thanks I commented on releases patch https://review.opendev.org/c/openstack/releases/+/86233309:13
bcafarelstill doable to get it in before Nov 209:14
ltomasboI'll trigger the cherry-pick right after the previous one gets merged09:15
ltomasboshould be doable, yes09:15
ltomasbofingers crossed on the gates09:15
bcafarel:)09:15
ralonsohltomasbo, bcafarel I'll include those tags09:33
opendevreviewMerged openstack/ovn-octavia-provider stable/xena: Optimization for find_ls_for_lr  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258410:05
ralonsohltomasbo, https://review.opendev.org/c/openstack/releases/+/862333/1..2/deliverables/wallaby/ovn-octavia-provider.yaml10:10
ralonsohis that ok?10:10
ltomasboralonsoh, I don't think so, I need to create the wallaby backport10:11
ralonsohltomasbo, I though you merged the patch...10:12
ltomasboralonsoh, but depends on the previous one... as soon as it merges, I'll create it10:12
ralonsohahhh ok10:12
ralonsohno rush, I need to update the releases patch because of neutron10:12
ralonsohltomasbo, ping me once is done10:12
ltomasbono no, we need to backport 2 (chained) patch sets... ones is on the merging gate at the moment, the other one is not even created as it depends on the previous noe10:12
ltomasboralonsoh, I'll do!10:12
ralonsohelodilles, sorry, what does it mean? -->10:19
ralonsohhttps://zuul.opendev.org/t/openstack/build/965bd96e6d2b471b8aedc1776308f3d110:19
ralonsohdo I need to create a new release for those hashes to be EM that have no version?10:20
ralonsohlajoskatona, ^ maybe you happen to know this10:30
elodillesralonsoh: the *-em tag only be applied towards a release10:30
ralonsohelodilles, so can I add in the same patch a new release and the -em tag?10:30
elodillesralonsoh: so it need to be the same hash as in the latest release10:30
ralonsohor should I push first a patch to create these new releases?10:31
elodillesralonsoh: in short: it needs a separate release patch10:31
ralonsohperfect10:31
ralonsohI'll do it10:31
elodillesthanks10:31
lajoskatonaralonsoh, elodilles: ok, I misunderstood this part also, push release patches for stadiums where need10:45
opendevreviewRodolfo Alonso proposed openstack/neutron master: [WIP] Placement tunnelled networks  https://review.opendev.org/c/openstack/neutron/+/86063910:49
opendevreviewMerged openstack/ovn-octavia-provider stable/wallaby: Optimization for find_ls_for_lr  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258510:54
opendevreviewMerged openstack/ovn-octavia-provider stable/victoria: Optimization for find_ls_for_lr  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258610:55
opendevreviewMerged openstack/ovn-octavia-provider stable/ussuri: Optimization for find_ls_for_lr  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86235710:55
opendevreviewMerged openstack/neutron stable/wallaby: [OVN] Set the default OVN metadata worker number to 0  https://review.opendev.org/c/openstack/neutron/+/86271211:02
opendevreviewMerged openstack/neutron stable/xena: [OVN] Set the default OVN metadata worker number to 0  https://review.opendev.org/c/openstack/neutron/+/86271111:02
opendevreviewMerged openstack/neutron stable/yoga: [OVN] Set the default OVN metadata worker number to 0  https://review.opendev.org/c/openstack/neutron/+/86271011:03
opendevreviewMerged openstack/neutron stable/zed: [OVN] Set the default OVN metadata worker number to 0  https://review.opendev.org/c/openstack/neutron/+/86258911:27
opendevreviewMerged openstack/networking-ovn stable/train: Optimization for find_ls_for_lr  https://review.opendev.org/c/openstack/networking-ovn/+/86235811:32
ralonsohltomasbo, https://review.opendev.org/c/openstack/ovn-octavia-provider/+/862585 is that the last patch?11:35
opendevreviewMerged openstack/ovn-octavia-provider stable/zed: Optimization for find_ls_for_lr  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258212:01
ltomasboralonsoh, no... let me generate the right one12:24
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/zed: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258112:31
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/xena: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86289012:33
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/wallaby: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86289112:34
ltomasbobcafarel, ralonsoh: this is the patch to include for ovn-octavia: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86289112:34
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/victoria: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86289212:34
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/zed: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258112:47
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/ussuri: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86236212:48
opendevreviewLuis Tomas Bolivar proposed openstack/networking-ovn stable/train: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/networking-ovn/+/86236313:07
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-octavia-provider stable/yoga: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86236413:15
ralonsoh#startmeeting neutron_drivers14:00
opendevmeetMeeting started Fri Oct 28 14:00:39 2022 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. 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
mlavalleo/14:00
ralonsohhello all14:00
haleyb_hi14:00
lajoskatonaHi14:01
njohnsto-o/14:01
ralonsohI think we have quorum14:02
ralonsohlet's start14:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/199413714:02
*** njohnsto- is now known as njohnsto_14:02
ralonsoh[RFE] Specify the precedence of port routes if multiple ports attached to a VM14:02
ralonsohthere are many proposals for this RFE14:02
ralonsohnot incompatible between them14:02
obondare_hi14:03
*** haleyb_ is now known as haleyb14:03
*** obondare_ is now known as obondarev14:03
ralonsohthe first one is adding the router metric into the cloud-init14:03
ralonsohas commented by Sean14:03
ralonsohbut I don't know if we can provide this info via dnsmasq14:04
ralonsohif we need this feature, then we'll need to use config drive 14:04
ralonsoh(that's what I think)14:04
ralonsoha second alternative (not incompatible with the other one): https://bugs.launchpad.net/neutron/+bug/171756014:05
ralonsohto disable the subnet default route14:05
ralonsohthe dnsmasq won't provide the default GW, that means the kernel won't provide a default route for this subnet14:06
lajoskatonathe above one is an old RFE, wasn't that implemented?14:06
lajoskatonaor it was just forgotten?14:06
ralonsohno, just abandoned 14:06
lajoskatonaok14:06
ralonsohthat requires to set a dnsmasq option 14:06
ralonsoh(let me find it again)14:07
ralonsohdhcp-option=314:07
ralonsohthat disables the default route14:08
ralonsohof course, that will be for any port on this subnet14:08
ralonsohany opinion?14:09
njohnsto_Just out of curiosity, how would it work in OVN without dnsmasq?14:10
lajoskatonaif I understand well the first one to add metric to cloud init is more a workaround, or am I wrong?14:10
ralonsohnjohnsto_, no, that feature will need to be implemented in the internal dhcp server14:11
obondarevfor the second option it says "API extension for a new 'default_route' attribute on the subnet resource" - can't this be for a port rather than subnet?14:12
ralonsohlajoskatona, not really, if you add a metric, you can have multiple default routes with different metrics14:12
ralonsoh(not very useful) but works14:12
ralonsohobondarev, that will depend on the DHCP service14:12
obondarevagree14:12
lajoskatonaobondarev: that would overwrite the gateway on subnet?14:12
ralonsohfor dnsmasq, for example, this is for all ports in the subnet14:13
ralonsohbecause this is a config in the service14:13
ralonsohfor OVN could be implemented independently (but just guessing, no idea)14:13
obondarevlajoskatona: I think it's more a flag rather than actual value14:13
njohnsto_To me, passing the metric to cloud-unit seems like the best and least intrusive solution on first look14:14
lajoskatonaobondarev: yeah, that's true14:14
ralonsohnjohnsto_, that implies not using dhcp service14:15
mlavalleshould get more input from chateaulav?14:15
mlavalle(the person who brought this up in the pain points etherpad)14:16
chateaulavmlavalle: all for providing more info14:17
mlavallegood to see you here...14:18
mlavalledid you have an approach in mind when you brought this up?14:18
lajoskatonachateaulav: welcome :-)14:18
chateaulavalways been here. just not a full-time openstack dev so always pulled 5 ways to the wind14:19
mlavalleor could you provide more detail?14:19
chateaulavlol14:19
ralonsohchateaulav, so do you have an implementation in mind when you proposed this RFE?14:21
ralonsoh(am I connected?)14:22
chateaulav```14:22
chateaulavroot@hack-the-power-de-ctf-dev-1-powerplant-sel351:~# ip route14:22
chateaulavdefault via 10.30.20.1 dev ens4 proto dhcp src 10.30.20.5 metric 100 14:22
chateaulavdefault via 192.168.20.1 dev ens3 proto dhcp src 192.168.20.113 metric 100 14:22
chateaulav10.30.20.0/24 dev ens4 proto kernel scope link src 10.30.20.5 14:22
lajoskatonaralonsoh: yes14:22
chateaulav169.254.169.254 via 10.30.20.1 dev ens4 proto dhcp src 10.30.20.5 metric 100 14:22
chateaulav169.254.169.254 via 192.168.20.1 dev ens3 proto dhcp src 192.168.20.113 metric 100 14:22
chateaulav192.168.20.0/24 dev ens3 proto kernel scope link src 192.168.20.113 14:22
chateaulav```14:22
chateaulavthis is an example when both subnets have dhcp enabled.14:22
chateaulavi know we discussed the option of potentially passing through a route metric14:23
chateaulavmulitple df gw's arent bad, they just cant all be 100. and correct me if im wrong or missing something as far as being able to accomodate this now14:24
ralonsohno, I can't create two default routes, using two different interfaces with the same metric14:26
ralonsohbut the goal is just the opposite, in any case14:27
ralonsohhow do you suggest to do this? via a config drive?14:27
ralonsohhello?14:29
mlavallewe are all here14:29
mlavalleprobabble chateaulav has a bad connection14:29
lajoskatonaWe can also ask for more details in the RFE, ot understand better the possibilities14:30
ralonsohyes, that exactly what I was going to say14:30
ralonsohI don't want you to spend more time on this14:31
ralonsohI'll update the launchpad bug requesting more information14:31
ralonsohif we have feedback, we'll continue with this14:31
ralonsohof for you?14:31
ralonsohok for you?14:31
mlavalleyeap14:31
lajoskatona+114:32
obondarev+114:32
mlavalle+114:32
haleyb+114:32
ralonsohok, sorry for the lack of progress in this meeting, next time I'll try to have the owners of the requests before starting14:33
ralonsohhave a nice weekend, see you14:33
obondarevo/14:33
ralonsoh#endmeeting14:33
opendevmeetMeeting ended Fri Oct 28 14:33:22 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:33
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-10-28-14.00.html14:33
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-10-28-14.00.txt14:33
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-10-28-14.00.log.html14:33
lajoskatonaSee, you, have a nice weekend14:33
mlavalleo/14:33
lajoskatonao/14:33
chateaulavSounds good14:35
*** dasm|off is now known as dasm14:58
atmarkHello, I have old openstack deployment running stable/ussuri. What's the correct order to remove FWaaS from a tenant?14:59
atmarkI managed to get the FW group STATE and STATUS to down but I notice it's dropping incoming traffic. When I go to active router, I see this chain `neutron-l3-agent-fwaas-defau` 15:01
atmark -A neutron-l3-agent-fwaas-defau -j neutron-l3-agent-dropped15:02
opendevreviewLajos Katona proposed openstack/networking-bagpipe stable/wallaby: Follow pyroute2 changes  https://review.opendev.org/c/openstack/networking-bagpipe/+/86289315:44
opendevreviewLajos Katona proposed openstack/networking-bagpipe stable/wallaby: Add required projects where necessary  https://review.opendev.org/c/openstack/networking-bagpipe/+/86250215:45
opendevreviewMerged openstack/ovn-octavia-provider stable/xena: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86289016:09
opendevreviewMerged openstack/ovn-octavia-provider stable/wallaby: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86289116:09
opendevreviewMerged openstack/ovn-octavia-provider stable/victoria: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86289216:09
opendevreviewMerged openstack/ovn-octavia-provider stable/ussuri: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86236216:22
opendevreviewMerged openstack/ovn-octavia-provider stable/zed: Ensure OVN-LB is properly configured upon LS removal from LR  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/86258116:22
opendevreviewRodolfo Alonso proposed openstack/neutron master: [WIP] Placement tunnelled networks  https://review.opendev.org/c/openstack/neutron/+/86063916:38
ralonsohelodilles, one qq about EOL: if there are new patches submitted between a EM branch and the current stable head, what should I do there?16:40
ralonsohe.g.: in Neutron queens, between the EM hash and the queens current hash, there are some new patches16:40
ralonsohok, I see an example: https://review.opendev.org/c/openstack/releases/+/862520/1/deliverables/queens/nova.yaml16:42
ralonsohI can just push the new hash in the tag EOL, without releasing a new branch16:42
mnasiadka_Has something changed between Xena and Yoga? I use neutron-dhcp-agent with OVN for baremetal ports, and dhcp agents stopped working - Horizon/CLI can't list dhcp agents in network - the error is "No controller found for: dhcp-agents"17:09
ralonsohmnasiadka_, please open a launchpad bug describing the issue you have17:56
mnasiadka_ralonsoh: will do18:16
elodillesralonsoh: yes, sorry, so: *-em tags are always shares the hash of the *latest release*, while *-eol tag should have the HEAD/tip of the branch, so as when the branch is deleted, the final state is not lost as it can be seen via checking out the *-eol tag18:27
*** dasm is now known as dasm|off20:23

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