Friday, 2022-03-25

gmannslaweq: I am summarizing the RBAC goal progress for Yoga. If I am understanding correctly, neutron work is still in progress and not ready for operator to try? 00:01
gmann https://review.opendev.org/c/openstack/neutron/+/82120800:01
opendevreviewZhouHeng proposed openstack/neutron master: [test][unit]creating resources support set project_id  https://review.opendev.org/c/openstack/neutron/+/83487401:20
opendevreviewMerged openstack/neutron-tempest-plugin master: CI: Fix typo for override-checkout and branch_override  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/83511306:04
opendevreviewliuyulong proposed openstack/neutron master: Add tag to port more earlier  https://review.opendev.org/c/openstack/neutron/+/81956708:39
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/+/83426008:46
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Lower memory footprint in the functional tests job  https://review.opendev.org/c/openstack/neutron/+/83517908:49
*** mgoddard- is now known as mgoddard09:11
slaweqralonsoh: lajoskatona obondarev hi, when You will have some time, please check https://review.opendev.org/c/openstack/neutron/+/82687209:28
ralonsohsure09:28
slaweqamotoki: and also You, if You can ^^ :)09:28
slaweqthx in advance09:28
slaweqralonsoh lajoskatona obondarev and also https://review.opendev.org/c/openstack/neutron/+/83485209:29
opendevreviewSlawek Kaplonski proposed openstack/neutron-lib master: Rehome missing ovs constants into neutron-lib  https://review.opendev.org/c/openstack/neutron-lib/+/83490809:29
bcafarelok stable/yoga is done for requirements https://review.opendev.org/c/openstack/releases/+/833610 we should have yoga CI soon :)09:30
ralonsohslaweq, https://review.opendev.org/c/openstack/neutron/+/826872/3/neutron/policy.py09:39
ralonsohsmall question, maybe I'm missing something09:39
slaweqsure09:39
amotokislaweq: ack. looking at it now09:44
slaweqralonsoh: I just replied to Your comment there09:45
slaweqamotoki: thx09:45
ralonsohthanks09:46
opendevreviewMerged openstack/ovn-octavia-provider master: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83379909:59
opendevreviewMerged openstack/ovn-octavia-provider stable/yoga: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83387209:59
amotokislaweq: I added a comment on InvalidScope from enforce(). could you check it?10:00
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/yoga: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83519410:11
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/xena: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83519510:13
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/wallaby: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83519610:13
opendevreviewMerged openstack/ovn-octavia-provider stable/wallaby: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83388210:14
opendevreviewMerged openstack/ovn-octavia-provider stable/victoria: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83388410:14
opendevreviewMerged openstack/ovn-octavia-provider stable/ussuri: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83399510:14
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/victoria: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83519810:25
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83519910:37
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83520410:59
opendevreviewSlawek Kaplonski proposed openstack/neutron master: [API] Return 403 for POST requests when user is not authorized  https://review.opendev.org/c/openstack/neutron/+/83417111:27
slaweqamotoki lajoskatona ralonsoh if You have some time, please also check ^^11:27
slaweqthx in advance11:27
ralonsohsure11:28
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Lower memory footprint in the functional tests job  https://review.opendev.org/c/openstack/neutron/+/83517911:41
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83520411:49
opendevreviewMerged openstack/networking-ovn stable/train: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/networking-ovn/+/83405512:03
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/ussuri: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83520412:07
opendevreviewMerged openstack/ovn-octavia-provider stable/xena: Retry logical switch associations to load balancers  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/83388512:15
opendevreviewFernando Royo proposed openstack/networking-ovn stable/train: Fix deletion of members without subnet_id  https://review.opendev.org/c/openstack/networking-ovn/+/83521612:44
opendevreviewMerged openstack/neutron master: Add extra logs to the ip_monitor class  https://review.opendev.org/c/openstack/neutron/+/83343412:49
lajoskatona1noonedeadpunk, trident, damiandabrowski[m]: Hi, can you attend from 14:00UTC the drivers meeting for the GARP issue? (https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda )13:03
noonedeadpunkyup, will be around!13:13
lajoskatona1noonedeadpunk: ok, thanks13:14
damiandabrowski[m]i will also be there13:43
opendevreviewSlawek Kaplonski proposed openstack/neutron master: Handle properly InvalidScope exceptions to not return error 500  https://review.opendev.org/c/openstack/neutron/+/82687213:49
tridentMe too...13:52
opendevreviewSlawek Kaplonski proposed openstack/neutron-lib master: Add oslo_policy.InvalidScope exception to the api faults map  https://review.opendev.org/c/openstack/neutron-lib/+/83523413:52
lajoskatona1#startmeeting neutron_drivers14:00
opendevmeetMeeting started Fri Mar 25 14:00:14 2022 UTC and is due to finish in 60 minutes.  The chair is lajoskatona1. 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
lajoskatona1o/14:00
yamamotohi14:00
ralonsohhello14:00
noonedeadpunko/14:00
tridentHello14:00
slaweqo/14:01
damiandabrowski[m]hi!14:01
lajoskatona1So first topic for today (again :-))):14:02
haleybhi14:02
lajoskatona1Gratuitous ARPs are not sent during master transition: (#link https://bugs.launchpad.net/neutron/+bug/1952907)14:02
lajoskatona1We have some patches (which I know about):14:02
lajoskatona1#link https://review.opendev.org/c/openstack/neutron/+/82143414:02
lajoskatona1#link https://review.opendev.org/c/openstack/neutron/+/82143314:02
lajoskatona1#link https://review.opendev.org/c/openstack/neutron/+/71247414:02
lajoskatona1last time we discussed it damiandabrowski[m] and trident perhaps promised that they try to test the issue more14:03
damiandabrowski[m]yes, i spent some time on this14:04
damiandabrowski[m]in my bug report i mentioned that this bug may be already fixed by keepalived: https://github.com/acassen/keepalived/commit/72c4e54e9f2a9b5081814e549c47c7fc58b82df014:04
damiandabrowski[m]but AFAIK we don't use vmac interfaces so it's not relevant14:05
damiandabrowski[m]and what's most important: i think keepalived has nothing to do with it, as slaweq's bug report(the reason why we keep qg- interface down on backup routers) describes the problem pretty well14:07
tridentTo clarify, we originally thought that keepalived fix actually remedied https://review.opendev.org/c/openstack/neutron/+/707406 - which is what causes https://bugs.launchpad.net/neutron/+bug/195290714:07
lajoskatona1damiandabrowski[m]: ok, so it seems that we need some code change on Neutron side?14:07
damiandabrowski[m]i think yes, https://bugs.launchpad.net/neutron/+bug/1859832  is slaweq's bugs report, the problem starts when neutron flushes link-local address on qg- interface, then interfaces sends multicast unsubscribe14:08
tridentSo as damiandabrowski[m] says, just reverting https://review.opendev.org/c/openstack/neutron/+/707406 won't be a solution as we initially thought.14:08
damiandabrowski[m]i'm not sure how we can fix this issue, but maybe we can do something else rather than just "flush link-local ip"14:09
damiandabrowski[m]or maybe we can prevent sending multicast unsubscribe packets, maybe with some sysctl parameters?14:09
damiandabrowski[m]i just think we need to think about better solution for this bug: https://bugs.launchpad.net/neutron/+bug/185983214:10
damiandabrowski[m]as the current solution(keeping qg- interfaces down on backup routers), solved one problem but created another one14:11
slaweqthere was different solution for that bug https://review.opendev.org/c/openstack/neutron/+/702856/14:11
slaweqbut we decided to go with liu's patch which was simpler approach (only in L3 agent)14:11
ralonsohjust asking, none of the proposed patches/strategies are valid for you? 14:12
damiandabrowski[m]it may be worth to consider https://review.opendev.org/c/openstack/neutron/+/702856/ as well14:12
damiandabrowski[m]solutions 2. and 3. from my bug report https://bugs.launchpad.net/neutron/+bug/1952907 should work fine(at least for ipv4, not sure about ipv6)14:13
slaweqin keepalived there is setting vrrp_garp_master_repeat - how about setting it to e.g. 2 or 3 seconds?14:13
damiandabrowski[m]but ideally, we would wan't to drop keepalived's dependency do neutron control plane during failovers14:13
slaweqso keepalived would try a bit later to send second set of GARPs14:13
damiandabrowski[m]it won't help, if keepalived won't send another GARPs if first one fails14:14
damiandabrowski[m]i tried using different keepalived options but couldn't get it working this way14:14
damiandabrowski[m]*it won't help, keepalived won't send another GARPs if first one fails14:14
tridentTo be honest I don't really like https://review.opendev.org/c/openstack/neutron/+/707406 ... The fact that it suddenly moves neutron into the failover scenario, which now requires neutron agents fully working and may take some additional time during failover as states have to be detected and ports brought up by neutron after a failover. If 500 routers fail over at the same time, that may actually be significant time compared to just a14:15
trident VRRP fail over.14:15
slaweqin the past we had such code in keepalived-state-change-monitor to send garps there14:15
slaweqbut we removed it with https://review.opendev.org/c/openstack/neutron/+/75236014:15
ralonsoh^^ could be an option14:15
damiandabrowski[m]yes, one of my proposed solutons is to bring this eature back, but it's not ideal(i agree with @trindent): https://review.opendev.org/c/openstack/neutron/+/82143314:16
ralonsohright14:16
slaweqwe removed that because we saw an issue when basically many garps send by many routers were killing openvswitch14:17
slaweqralonsoh: probably remembers that issue well :)14:17
ralonsohyes, with 200 virtual routers in one compute14:17
ralonsohone controller14:17
tridentI wonder if https://bugs.launchpad.net/neutron/+bug/1859832 could be solved by just filtering MLDv2 or if we could even disable IPv6 on the interface initially to not get a link local address before keepalived is started etc...14:18
mlavalleso in this scenario we need to keep neutron involved in the failover business14:18
slaweqif there would be way to disable sending garps by keepalived and do it only from neutron-keepalived-state-change or l3 agent, that would be IMO the best solution14:18
ralonsohtrident, I agree with investigating an option to just filter the "wrong" traffic. In this case MLDv2 packets14:19
slaweqtrident: IIRC that MLDv2 issue couldn't be solved by disabling IPv6 on interface as when You enabled/disabled IPv6 those packets were sent immediately14:19
ralonsohand reverting the patch to set the interfaces down14:19
lajoskatona1slaweq: true, that is not dependent on 3rd party version14:19
ralonsohbut filtering the traffic?14:20
slaweqso the only option was to bring interfaces down or block them e.g in OVS (what patch https://review.opendev.org/c/openstack/neutron/+/702856/ proposed)14:20
damiandabrowski[m]i only wonder how keepalived(used outside the openstack) solves this issue, as basically it may be affected by the same issue when rebooting backup keepalived(but i don't have an answer for this ATM)14:21
mlavallecrazy idea... in damiandabrowski[m] original report he mentions "When I add random port to this router to trigger keepalived's reload, then all GARPs are sent properly". Can we force this in Neutron?14:21
mlavalleI mean the reload14:22
slaweqmlavalle: I don't see reason why, easier would be to revert https://review.opendev.org/c/openstack/neutron/+/752360 and send additional garps from neutron directly14:22
lajoskatona1yeah I fear that is considered at a time as bug in keepalived....14:22
mlavalleI said it was crazy idea... brainstorming14:23
lajoskatona1mlavalle: +114:23
tridentI do have a slight memory of seeing a proposed fix (that I think was abandoned) to that issue or some other similar issue which actually filtered the problematic traffic quite some time ago. I have however not been able to locate it. Does it ring any bells for anyone?14:23
slaweq:)14:23
slaweqtrident: You mean https://review.opendev.org/c/openstack/neutron/+/702856/ ?14:24
tridentslaweq: Nope, I think it was iptables or ebtables...14:24
slaweqtrident: but we can't filter that traffic completly as it may break some IPv6 functionalities in the "master" router, no?14:25
tridentslaweq: But we could instead of taking the interface down completely as we do today, apply filters and then instead of bringing the whole interface up, we could remove the filters.14:26
slaweqtrident: You mean apply iptables fiters when router is going to be "backup" and then remove them when router is going to be "primary"?14:27
slaweqinstead of doing "ip link set down" and "ip link set up" like we have now14:27
tridentslaweq: Yes. Note that I have not done any testing on that idea though, I just thought of it an hour or so before this meeting.14:27
slaweqtrident: I think that can work14:28
slaweqTBH I don't remember now why I was trying to block it in OVS not iptables14:28
slaweqmaybe there was some reason for that or maybe it was just that I was somehow biased then :)14:28
slaweqIMO worth try14:29
mlavalleso we have two working hypothesis: 1) have neutron do the garps 2) apply and remove filters14:29
mlavalleis that a good summary?14:30
lajoskatona1malavalle: thanks, thats my understanding too14:30
slaweqmlavalle: for 1) I would be ok with only if we can somehow disable garps in keepalived14:30
slaweqas we had issues with ovs when there was too much garps send14:30
slaweqso we should avoid that IMO14:30
mlavalleslaweq: yeah, that was my assumption. I just wanted to be brief in the summary14:30
slaweq++14:31
ralonsoh2) can also solve frequent problems we have, at least in the CI, with race conditions when failing over14:31
slaweqralonsoh: yeah, hopefully :)14:32
mlavalleso if we have to pick the most promising alternative, is 2) the one?14:32
slaweqso I would really give a try to the solution 2) first14:32
lajoskatona1sounds good alternative14:33
mlavalletrident, damiandabrowski[m]: you ok with thi plan? will you propose a patch?14:33
damiandabrowski[m]or 3) do not engage neutron in keepalived's failover process at all? it's probably the best solution, but also the hardest one14:34
damiandabrowski[m]as if i understand correctly, 1) and 2) is still dependent from neutron14:34
lajoskatona1yes, it's true14:35
slaweqdamiandabrowski: I'm not sure if I understand correctly, can You elaborate on that one?14:35
tridentI am afraid I might not be familiar enough with the code base to propose such a patch within reasonable time :/ I would however be most willing to help with testing!14:35
mlavallesepartion of concerns is always ideal... life is messy, though ;-)14:36
damiandabrowski[m]slaweq: because currently neutron is responsible for keeping interfaces up/down, with 1) neutron will send garps, with 2) neutron will be responsible for updating iptables rules14:37
lajoskatona1noonedeadpunk: Do you have also some idea about the listed aproaches?14:37
damiandabrowski[m]it makes keepalived failover process fully dependent from neutron which is not ideal situation14:38
damiandabrowski[m]because technically, keepalived should be able to failover even when neutron is not functioning properly14:38
noonedeadpunkI'm not huge expert in code, but updating iptables sounds like an idea. Especially if that help out with race conditions in CI...14:38
*** dasm|off is now known as dasm14:38
ralonsohdamiandabrowski[m], you are right on this, but then keepalived should be able to block this traffic14:39
lajoskatona1noonedeadpunk: thanks14:39
mlavalleso what you say is once the router is setup, it should function on its own regardlees of what happens to the neutron control plane14:39
tridentralonsoh: Which it probably _could_ not, as this if I understand it correctly happens before keepalived is even started?14:39
tridentralonsoh: When neutron flushes the link local address from the interface and adds it to keepalived config.14:39
noonedeadpunkbut issue happens on router setup indeed?14:40
noonedeadpunkwhich kind of makes sense at least to me that neutron is responsible for setup of l314:40
noonedeadpunkbut I guess then keepalived manages himself anyway?14:40
damiandabrowski[m]not exactly, the original issue(reported by slaweq) happens  when You reboot backup keepalived14:41
noonedeadpunkouch14:41
noonedeadpunkok14:41
tridentHm, if we could make the filters apply only between "router startup" until keepalived has been started perhaps? As long as the link local address flush, addition to keepalived and start of keepalived happens while filter is applied it would be fine I guess.14:41
ralonsohso block traffic only until keepalived is in charge14:42
damiandabrowski[m]ah, i think You're right14:43
damiandabrowski[m]so yeah, swapping https://review.opendev.org/c/openstack/neutron/+/707406/ with some 'iptables filtering solution' sounds like an idea for me14:44
slaweqI think that it is exactly what patch https://review.opendev.org/c/openstack/neutron/+/702856 was doing but with OVS instead of iptables rules14:44
damiandabrowski[m]slaweq:  +114:45
slaweqbut iptables filtering may be better here14:45
tridentslaweq: With the difference that it will filter all traffic.14:46
slaweqtrident: but only when router is created, not later during failover, right?14:47
mlavalleyes, afterwards we would let keepalioved do its job14:48
slaweq++14:48
tridentslaweq: Oh, that might be true actually. In that case that might actually be a great solution!14:48
mlavalleralonsoh put it very clearly: block traffic only until keepalived is in charge14:49
lajoskatona1trident, damiandabrowski[m]: do you think that you can work on it? Or just testing?14:50
damiandabrowski[m]i can help with testing but i dont feel confident to write a patch :/14:50
ralonsohlet me talk to my manager to see if we can spend time on this patch14:51
lajoskatona1ralonsoh: thanks, I don't know how often we see effects of this in the CI14:52
lajoskatona1so we can have few minutes during the PTG also if you think14:52
ralonsohfor sure (btw, I have good feedback so I'll take care of it)14:53
mlavalle++14:53
slaweqralonsoh++ thx14:53
lajoskatona1ok, as I see we have a plan, is that ok for everybody?14:53
mlavallethanks14:53
mlavalle+114:53
ralonsoh+114:53
tridentGreat ralonsoh, thanks! I'll also be available for testing and review!14:53
trident+114:54
damiandabrowski[m]awesome, thanks for Your engagement everyone!14:54
lajoskatona1yeah thanks everybody :-)14:54
lajoskatona1Ok next topic:14:54
lajoskatona1#topic On Demand Agenda14:54
mlavalleactually it's been a very enlightening conversation14:55
lajoskatona1(ralonsoh): #link https://bugs.launchpad.net/neutron/+bug/196457514:55
lajoskatona1mlavalle: I agree14:55
ralonsohvery quick: this is related to the sqlalchemy 2.0 migration14:55
ralonsohthe session transaction, in 2.0, will be created and never finished14:55
ralonsohother side effect is that we don't have the implicit transaction creation, commit and deletion14:56
ralonsohthis is why it is a MUST to always we create a DB operation, to open a context (reader/writer)14:56
ralonsohthis is, in a nutshell, the summary14:56
lajoskatona1ralonsoh: thanks14:56
ralonsohthat's all thansk14:57
lajoskatona1this is the patch you mentioned on the wiki: https://review.opendev.org/c/openstack/neutron/+/83324714:57
ralonsohexactly14:57
ralonsohand then we'll have the n-lib patch to set autocommit=False14:57
ralonsoh(that will enable the 2.0 feature)14:57
mlavallecool14:57
mlavallethank you14:58
slaweqralonsoh: so another "migration to new engine facade" like story for couple of cycles? :)14:58
ralonsohpfffff kind of !!!14:58
lajoskatona1:-)14:58
lajoskatona1ok so we will have topic for next cycles than :P14:58
slaweqlajoskatona1: yeah :)14:58
mlavallelol14:59
ralonsohI think so... we'll need keep an eye on this14:59
lajoskatona1If nothing more for this I have 2 small topics14:59
slaweqshouldn't this be a community wide goal then?14:59
slaweqor only neutron is affected by that change?14:59
ralonsohcommunity (but this should be raise by oslo.db cores in TC)15:00
ralonsohwe'll have time for this15:00
ralonsohlajoskatona1, please15:00
lajoskatona1slaweq: I saw perhaps nova changes15:00
lajoskatona1ralonsoh: ok ,thanks15:00
lajoskatona1PTG etherpad: #link https://etherpad.opendev.org/p/neutron-zed-ptg15:00
lajoskatona1please add your topics :-)15:00
* mlavalle will be on PTO next week, so won't attend this meeting15:01
lajoskatona1mlavalle: the PTG?15:01
lajoskatona1The other one is that there will be openinfra episode next week for cycle highlights15:02
lajoskatona1there is a slideset: #link https://docs.google.com/presentation/d/1PhTzrIUo6kfCzdoPO5V3xgQCt6ktqGP3Q1y6BXMryzg/edit#slide=id.g11ee73f15e5_1_415:02
lajoskatona1if you have time please check it I added few sentences for Neutron15:02
mlavalleI will attend the PTG on the week of april 4 - 815:02
lajoskatona1mlavalle: ok15:03
mlavalle\I will just be on PTO this coming week15:03
mlavalleso if there is drivers meeting on 1st, I won't attend15:03
lajoskatona1For next week I plane to cancel both the team meeting and the drivers meeting as the week after is the PTG15:03
mlavallegreat15:03
mlavallethen nvm15:03
lajoskatona1mlavalle: ok, thanks15:03
lajoskatona1and that's it from me, thanks for attending15:03
ralonsohthanks!15:04
mlavalleo/15:04
lajoskatona1#endmeeting15:04
opendevmeetMeeting ended Fri Mar 25 15:04:08 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:04
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-25-14.00.html15:04
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-25-14.00.txt15:04
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-25-14.00.log.html15:04
lajoskatona1o/15:04
slaweqo/15:04
lajoskatona1and sorry for overtime....15:04
yamamotogood night15:04
slaweqhave a great weekend @all :)15:04
lajoskatona1thanks the same to you15:05
gmannslaweq: ping for rbac goal status query. in case you missed  my ms. 15:20
slaweqgmann: I think I missed your message15:34
slaweqwhat query are You asking for?15:35
gmannslaweq: NP!15:35
gmannslaweq: I am summarizing the RBAC goal progress for Yoga. If I am understanding correctly, neutron work is still in progress and not ready for operator to try? 15:35
gmann https://review.opendev.org/c/openstack/neutron/+/82120815:35
slaweqgmann: we have some bugs there, like https://bugs.launchpad.net/neutron/+bug/195933315:37
slaweqbut patches are in review currently15:37
gmannslaweq: ok, I will mark neutron as in-progress then. also will try to review these next week15:37
slaweqI know that devstack has job with those new defaults in neutron and that job is running fine IIRC15:37
gmannslaweq: ack15:38
slaweqthe main part which we miss are neutron-tempest-plugin tests (or tempest) which would use new personas/scopes15:38
gmannslaweq: yeah, tempest tests can be migrated to new scope and defaults15:39
slaweqgmann: with some switch in config or something like that?15:39
gmannslaweq: plan is with switch but for stable branch. and for master it run on new default with scope15:40
gmannend goal is tempest/plugins tests start using new defaults15:40
slaweqok15:40
gmannthat might be lot of work which i am going to start for nova in zed15:41
gmannslaweq: anyways, I will check neutron changes next week, something we have done in nova and needs to be done in neutron too15:41
slaweqthx a lot15:41
gmannslaweq: thanks for updates, and have a good weekend.15:41
slaweqthx, You too15:44
*** elvira4 is now known as elvira16:39
opendevreviewJakub Libosvar proposed openstack/neutron master: ovn: Make ovn metadata agent report optional  https://review.opendev.org/c/openstack/neutron/+/79299817:26
opendevreviewRodolfo Alonso proposed openstack/neutron master: [L3][QoS] L3 agent QoS extension to handle duplicated FIPs  https://review.opendev.org/c/openstack/neutron/+/83123817:28
opendevreviewRodolfo Alonso proposed openstack/neutron master: [WIP][L3] QoS inherit network  https://review.opendev.org/c/openstack/neutron/+/81914717:28
opendevreviewRodolfo Alonso proposed openstack/neutron master: [WIP][L3] QoS inherit network  https://review.opendev.org/c/openstack/neutron/+/81914717:37
opendevreviewRodolfo Alonso proposed openstack/neutron-lib master: [WIP][DNM] Refactor session "is_active" handling for sqlalchemy-20  https://review.opendev.org/c/openstack/neutron-lib/+/82873817:50
opendevreviewRodolfo Alonso proposed openstack/neutron-lib master: [WIP][DNM] Refactor session "is_active" handling for sqlalchemy-20  https://review.opendev.org/c/openstack/neutron-lib/+/82873817:52
opendevreviewMerged openstack/neutron master: Fix some Openvswitch firewall doc typos  https://review.opendev.org/c/openstack/neutron/+/83512818:50
opendevreviewMerged openstack/neutron master: ovn migration: Remove usage of tripleo-ansible-inventory  https://review.opendev.org/c/openstack/neutron/+/83492518:50
opendevreviewMerged openstack/neutron master: [OVN] Reschedule router GW chassis when AZ updated  https://review.opendev.org/c/openstack/neutron/+/82507318:50
opendevreviewJakub Libosvar proposed openstack/neutron stable/yoga: ovn migration: Remove usage of tripleo-ansible-inventory  https://review.opendev.org/c/openstack/neutron/+/83514719:02
opendevreviewJakub Libosvar proposed openstack/neutron stable/xena: ovn migration: Remove usage of tripleo-ansible-inventory  https://review.opendev.org/c/openstack/neutron/+/83514819:02
opendevreviewJakub Libosvar proposed openstack/neutron stable/wallaby: ovn migration: Remove usage of tripleo-ansible-inventory  https://review.opendev.org/c/openstack/neutron/+/83514919:02
*** dasm is now known as dasm|off19:14
opendevreviewMiguel Lavalle proposed openstack/python-neutronclient stable/wallaby: Dropping lower constraints testing (stable Wallaby)  https://review.opendev.org/c/openstack/python-neutronclient/+/83497621:51
opendevreviewMiguel Lavalle proposed openstack/python-neutronclient stable/wallaby: tests: change safe_hasattr to hasattr  https://review.opendev.org/c/openstack/python-neutronclient/+/83494221:54
opendevreviewMiguel Lavalle proposed openstack/python-neutronclient stable/wallaby: Use yaml.safe_load instead of yaml.load  https://review.opendev.org/c/openstack/python-neutronclient/+/83493021:55

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