Friday, 2024-03-01

opendevreviewMiguel Lavalle proposed openstack/neutron master: Enable HA for OVN router flavors  https://review.opendev.org/c/openstack/neutron/+/90151301:44
opendevreviewMerged openstack/neutron stable/zed: Retry ``set|get_link_attribute(s)`` if the interface is not present  https://review.opendev.org/c/openstack/neutron/+/91035705:08
opendevreviewMerged openstack/neutron stable/wallaby: Add max limit to agent_down_time  https://review.opendev.org/c/openstack/neutron/+/90533205:41
opendevreviewMerged openstack/neutron master: Replace CRLF by LF  https://review.opendev.org/c/openstack/neutron/+/90692806:13
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Remove OVN_GATEWAY_INVALID_CHASSIS artifact  https://review.opendev.org/c/openstack/neutron/+/90930507:03
opendevreviewMerged openstack/neutron master: [OVN] Identify the LR GW port with "external_ids:neutron:is_ext_gw"  https://review.opendev.org/c/openstack/neutron/+/90931107:53
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] "Logical_Router" pinned to chassis, OVN L3 scheduler  https://review.opendev.org/c/openstack/neutron/+/90919408:02
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Provide HA functionality to "Logical_Router" chassis pinning  https://review.opendev.org/c/openstack/neutron/+/90943708:02
opendevreviewRodolfo Alonso proposed openstack/neutron master: [eventlet] Do not monkey patch OVN agents  https://review.opendev.org/c/openstack/neutron/+/91070208:21
opendevreviewFernando Royo proposed openstack/ovn-bgp-agent master: Fix OVN LB Delete events for NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90578308:42
opendevreviewMerged openstack/neutron stable/zed: Stable-Only: Temporary stop running grenade jobs on Zed  https://review.opendev.org/c/openstack/neutron/+/91037908:57
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Implement OVN agent metadata extension  https://review.opendev.org/c/openstack/neutron/+/89823809:10
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron master: scheduler: make auto_scheduler_network uderstanding dhcp_agents_per_network  https://review.opendev.org/c/openstack/neutron/+/91070809:11
opendevreviewMerged openstack/neutron-lib master: [netaddr>=1.0.0] Do not use netaddr.core.ZEROFILL flag with IPv6  https://review.opendev.org/c/openstack/neutron-lib/+/91033109:28
opendevreviewRodolfo Alonso proposed openstack/neutron master: WIP - Add ``OVNGatewayHAChassisGroup`` scheduler class  https://review.opendev.org/c/openstack/neutron/+/87203309:38
fnordahlhum, two different tempest jobs failed in the same way on `tempest.api.identity.admin.v3.test_roles.RolesV3TestJSON.test_role_create_update_show_list`, I wonder if there is a breakage somewhere else09:41
fnordahlhttps://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_0d9/878543/64/check/neutron-ovs-grenade-multinode-skip-level/0d9fc53/controller/logs/grenade.sh_log.txt09:41
fnordahlhttps://0aea9c217e86134e83d8-9ea232b51691ad27ed2d3f8993736155.ssl.cf1.rackcdn.com/878543/64/check/neutron-ovs-grenade-multinode/b169cfa/controller/logs/grenade.sh_log.txt09:41
opendevreviewFernando Royo proposed openstack/ovn-bgp-agent master: Fix OVN LB Delete events for NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90578309:43
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Set MTU of the VETH interfaces between OVS and metadata  https://review.opendev.org/c/openstack/neutron/+/90968410:18
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2023.2: [stable-only][OVN] Set VETH interface MAC address before up  https://review.opendev.org/c/openstack/neutron/+/91071410:29
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2023.1: [stable-only][OVN] Set VETH interface MAC address before up  https://review.opendev.org/c/openstack/neutron/+/91071510:29
opendevreviewRodolfo Alonso proposed openstack/neutron stable/zed: [stable-only][OVN] Set VETH interface MAC address before up  https://review.opendev.org/c/openstack/neutron/+/91071610:29
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2023.2: [OVN] Set MTU of the VETH interfaces between OVS and metadata  https://review.opendev.org/c/openstack/neutron/+/91071710:30
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2023.2: [OVN] Set MTU of the VETH interfaces between OVS and metadata  https://review.opendev.org/c/openstack/neutron/+/91071710:31
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2023.1: [OVN] Set MTU of the VETH interfaces between OVS and metadata  https://review.opendev.org/c/openstack/neutron/+/91071810:32
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Add support for l3vpn with NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90650510:57
opendevreviewMerged openstack/neutron master: [OVN][FT] Check ``WaitForCreatePortBindingEvent`` wait result  https://review.opendev.org/c/openstack/neutron/+/91036311:03
opendevreviewRodolfo Alonso proposed openstack/neutron master: Add "socket" NUMA affinity policy  https://review.opendev.org/c/openstack/neutron/+/91059411:05
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Add support for l3vpn with NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90650511:12
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Add support for l3vpn with NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90650511:28
opendevreviewMerged openstack/neutron master: [ovn] Ensure OVN DB update on change of number of GW ports  https://review.opendev.org/c/openstack/neutron/+/90995512:43
haleybi am canceling the drivers meeting as there is nothing on the agenda, happy reviewing! and have a nice weekend14:01
slaweqthx haleyb 14:01
slaweqhave a nice weekend :)14:02
ralonsohthanks14:02
ralonsohhaleyb, I'm checking the nested ovs routers14:02
ralonsohand again, I can't forward the traffic14:02
lajoskatonathanks haleyb14:02
ralonsohI have a live env right now14:02
ralonsohI'm going to finish the testing with legacy and ha routers14:02
haleybralonsoh: i still have mine that is working, i just ran all the commands in the bug14:04
lajoskatonaI retweet(X) my Tuesday question regarding openinfra days to have feedback from Other time zones also:14:04
lajoskatonabcafarel, elvira, mlavalle, mtomaska, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki: general question: do you know if you can travel to any of the OpenInfra days (https://openinfra.dev/days )?14:04
lajoskatonaif yes we should sync it to meet and discuss (drink a beer :-))  in person and than I can start asking my management for travel budget :-)14:05
haleybralonsoh: well, the ml2/ovs is working, the ovn is not unless i apply the patch14:05
ralonsohlajoskatona, I'm not in this list, I guess14:05
ralonsohlajoskatona, sorry, I'll be in parental leave at this time14:05
lajoskatonaralonsoh: sorry, I copied it from somewhere....14:05
ralonsohhaleyb, is this a all-in-one env?14:05
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-bgp-agent master: Bump OVS version (branch 3.3) for devstack local.conf sample  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/91049114:05
ralonsohI'm not saying this patch works, what I'm saying is that 1) I can't reproduce that with ml2/ovs (so I don't think this is a regression)14:06
lajoskatonaralonsoh: thanks, the question is more if we (E/// team) want to do the time consuming meetings with management for travel budget or just live with online meetings14:06
ralonsohand 2) allowing the nating between a external network and other networks not directly attached to a router could be a security issue14:06
ralonsohhaleyb, is yours an all-in-one env?14:07
haleybralonsoh: but this is for nating an internal network using the default snat address to an external network14:07
haleybyes, all in one14:07
ralonsohhaleyb, what I don't know is if your environment (the kernel) is somehow redirecting this traffic14:09
ralonsohhaleyb, what kind of router do you have? legacy, dvr or ha?14:09
haleybLinux 22-04-ovs 6.5.0-21-generic #21~22.04.1-Ubuntu14:09
haleybstandard lts kernel14:09
ralonsohI've seen some "gaps" with ml2/ovs14:10
haleybralonsoh: legacy, no dvr in this deployment14:10
ralonsohfor example, allowing snat from an internal network vm to an external vm using an OVS DVR router14:11
ralonsohthe same config but with HA router is not working14:11
haleybso if you boot a vm on the nested network, you can't ping 8.8.8.8 ?14:11
ralonsohand neither in oVN14:11
ralonsohno, I can't 14:11
ralonsohI have this14:11
ralonsoh$ ping 10.0.0.22114:11
ralonsohPING 10.0.0.221 (10.0.0.221) 56(84) bytes of data.14:11
ralonsohFrom 10.20.0.1 icmp_seq=1 Destination Net Unreachable14:11
ralonsohFrom 10.20.0.1 icmp_seq=2 Destination Net Unreachable14:11
ralonsohI'm still writing my comment in the LP bug14:11
ralonsohbecause I've only tested with dvr routers14:11
ralonsohI'm going to use now legacy and ha14:12
ralonsoh--> not finished reply in my buffer: https://paste.opendev.org/show/bmP3wxEqLMvwYcQjfwDp/14:12
haleybis that subnet from the v4 default pool? or same pool as the other subnet?14:13
ralonsohhaleyb, I'm not using subnet pools14:13
ralonsohI have an external subnet (10.0.0.0/24), private1 (10.10.0.0/24) and private2 (10.20.0.0/24)14:14
mlavalleralonsoh: I followed your suggestion here https://review.opendev.org/c/openstack/neutron/+/901513/19/neutron/services/ovn_l3/plugin.py#418. But now I hit this https://60a62e10d8b9b798ee87-e7edb05e06a1172316eb4206e173039e.ssl.cf1.rackcdn.com/901513/21/check/neutron-tempest-plugin-ovn/790b675/testr_results.html14:14
mlavalleralonsoh: what do you suggest?14:14
haleybthat might have something to do with it, my memory is foggy but perhaps the different scope of the subnets is affecting forwarding14:15
ralonsohdifferent scope?14:15
haleybip rule type stuff, i'd have to check in the namespaces14:16
ralonsohall subnets should not collide14:16
ralonsohno no, we are not using address scopes14:16
ralonsohmlavalle, I'll check it once I finish this ongoing issue14:17
mlavalleralonsoh: thanks!14:17
haleybralonsoh: well your setup is different than mine not being all in one. but our customer has an ml2/ovs deployment that is working fine today, and it's 3-network nodes, multiple compute nodes14:21
ralonsohhaleyb, I would need to know what is the external network type and the router types14:22
ralonsohhaleyb, I'm checking now with other router types14:22
haleybralonsoh: so the VM you booted can ping the internal interface of the gw router, but not the external?14:24
ralonsohno14:24
ralonsohI can't ping router_ext GW port14:24
haleyb10.20.0.1 is the internal IP?14:26
ralonsohyes, router_ext internal IP14:26
haleybthat is responding to the ping with a dest unreach, hmm14:27
* haleyb runs to get coffee14:27
opendevreviewMerged openstack/ovn-bgp-agent master: Bump OVS version (branch 3.3) for devstack local.conf sample  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/91049114:27
ykarellajoskatona, no plan to travel for those days14:32
*** ykarel is now known as ykarel|away14:33
lajoskatonaykarel: thanks14:34
haleyblajoskatona: can you look at https://review.opendev.org/c/openstack/neutron/+/894399 again? it was only rebased since last ps14:43
lajoskatonahaleyb: on it14:45
ralonsohhaleyb, with legacy routers (this is the first time I test them), I can ping14:45
ralonsohbut it is not possible with ha nor dvr14:46
ralonsohso this is more a bug than a feature14:46
haleybslaweq: can you look at https://review.opendev.org/c/openstack/neutron/+/909943 - and i might ping you about more reviews later :)14:46
haleybralonsoh: so i just reached out the the admin of this cloud, and it is running l3-ha with neutron gateway nodes (i.e. network nodes)14:48
ralonsohno, I can't ping with HA routers14:49
ralonsohonly with legacy14:49
haleybralonsoh: so with dvr i wonder what is different, i can change my config. but the bug could be in dvr14:59
ralonsohno no, I can't ping with HA nor DVR14:59
ralonsohI don't know why your customer can with HA15:00
ralonsohbut I can't reproduce that with HA15:00
ralonsohin any case, I'm now talking to some core OVN folks, raising this question of nested routing15:00
ralonsohand if that should work and how15:00
haleybralonsoh: ack, thanks, my next step was going to be that ML but you have an inside track to them15:02
opendevreviewMerged openstack/ovn-bgp-agent master: Fix address scope test and add address scope unit tests  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90718715:03
haleybralonsoh: https://bugs.launchpad.net/neutron/+bug/2029722 - i just remembered this bug, dvr has issues with this scenario, missing a rule15:04
opendevreviewLuis Tomas Bolivar proposed openstack/ovn-bgp-agent stable/2023.2: Fix address scope test and add address scope unit tests  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/91061815:04
ralonsohhaleyb, I've created the same env with OVN (never tested that before)15:33
ralonsohhaleyb, I can ping, from the internal VM to the ext GW port15:33
haleyback, but not the external network i'd guess15:33
ralonsohyes15:34
ralonsohthe external network GW port15:34
haleybovn-nbctl lr-nat-list neutron-$routerid15:34
ralonsohI have this in a devstack deployment, but I'm deploying now a multinode one15:35
haleybstephenfin: can you take a look at https://review.opendev.org/c/openstack/python-openstackclient/+/887976 and the dependent? the code is basically merged in neutron but we don't have +W in the client repo. thanks!15:44
stephenfinI've held off approving anything this week as gtema told me not to15:44
haleybfnordahl: is https://review.opendev.org/c/openstack/neutron/+/899402 still a WIP?15:44
haleybstephenfin: oh, did we pass the client freeze?15:45
stephenfinI suspect so15:46
stephenfinIf we have, we can backport this (there's no issues with feature backports). Otherwise, we could ask for a FFE (if those are a thing for client libs)15:46
stephenfinProbably best to ask gtema?15:46
haleybstephenfin: ack, maybe i'm confused by the schedule15:48
gtemahonestly speaking I am also not able to understand the schedule reliably15:49
gtemawe are now in requirements freeze, soft strings freeze, final release for client libraries15:49
haleybhttps://releases.openstack.org/caracal/schedule.html has a non-client and client library freeze, i figures python-openstackclient was the latter?15:50
gtemayes15:50
gtemaand basically RM asked me last week to stop accepting anything15:50
haleybgtema: "release management" ? i was going by the schedule15:51
gtemayes15:51
gtemaI am also now looking at the schedule and not able to say for sure15:51
haleyb¯\_(ツ)_/¯15:53
haleybi only see "Feb 26 - Mar 01"15:53
gtemaright, on the other hand the final release itself is done15:54
opendevreviewMerged openstack/ovn-bgp-agent stable/2023.2: Fix address scope test and add address scope unit tests  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/91061815:55
haleybgtema: ok, so we merge these to master (eventually), then backport to stable/2024.1 when it opens?15:56
gtemaI'm currently asking release team15:56
gtemaare we surely need this change in 2024.1 branch? I mean osc itself is a "rolling" stuff15:57
haleybgreat, thanks, i'm in that channel too. it's more of a "feature complete" thing as we're updating the neutron guide15:58
stephenfinhaleyb: One potential bug/optimisation noted in https://review.opendev.org/c/openstack/python-openstackclient/+/88797616:07
gtemahaleyb: so if you address changes till lets say mid of next week we can make this16:32
haleybfnordahl: ^^16:32
haleybfnordahl: can't tell if one of the functional test failures in https://review.opendev.org/c/openstack/neutron/+/878543 is related to the change, test_gateway_chassis_rebalance17:02
opendevreviewVasyl Saienko proposed openstack/neutron master: Remove unneeded check in dhcp.py  https://review.opendev.org/c/openstack/neutron/+/91020817:36
noonedeadpunkI need some help now with understanding of how ovn-bgp-agent works with outgoing traffic. As it feels it does eerything as it's supposed to right now, but I'm missing 1 very-very important bit. I'm trying to use nb_ovn_bgp_driver and underlay exposing method17:39
noonedeadpunkSo, I did have a working OVN deployment, and now trying to convert it to BGP one basically. As an br-ex I do have br-provider bridge. In clean OVN setup I have bond0 as part of br-provider, and then leveraged VLAN networks to get connectivity17:41
noonedeadpunkSo, ovn-bgp-agent seems to do quite proper job at the momement, and creates all promised wiring and routing tables, as well as expose IPs through the FRR17:41
noonedeadpunkIt did created br-provide.1001 vlan (which is defined in neutron as external VLAN network) and I do see traffic on it from VMs.17:42
noonedeadpunkAnd I dropped bond0 from br-provider bridge in OVN17:43
noonedeadpunkBut the part I'm missing obviously - is how now to wire bond0 with br-provider? 17:43
noonedeadpunkAs I assume br-provider must still exist in OVS, so it makes it a valid bridge17:43
noonedeadpunkBut then ovn-bgp-agent detects it, and uses more or less as simple interface? 17:44
noonedeadpunkie https://paste.openstack.org/show/b5lvx55Pp9AiWbV669lq/17:47
noonedeadpunkbut how in the world is should reach actual bond0.3102 as expected?17:47
noonedeadpunkOr well, maybe it should not be bond0.3102... but then what?17:48
noonedeadpunkor it should not use the OVS bridge name for it? as according to doc it is...17:49
noonedeadpunkso basically how I should wire/tell the path for external traffic (CR-LRP_IP) as it comes to br-ex.vlan and that's pretty much it...17:53
noonedeadpunkAs I see statement "the physical NICs are not directly attached to br-ex" which exactly the case I have... But then how to wire these physical nics to br-ex...17:54
noonedeadpunkI feel I'm missing smth very basic and very stupid...17:56
noonedeadpunkSo basically I can't understand how outgoing connectivity is reached, when physical interface is disconnected from br-ex18:15
noonedeadpunkand connect br-ex.3114 with bond0.3114 more or less?18:17
noonedeadpunkhm, ok, so actually I should have just left bond0 as part of the br-ex bridge despite what's written here https://docs.openstack.org/ovn-bgp-agent/latest/contributor/drivers/ovn_bgp_mode_design.html#proposed-solution18:19
noonedeadpunk"y contrast, in the default BGP driver solution (see [NB DB] NB OVN BGP Agent: Design of the BGP Driver with kernel routing), the physical NICs are not directly attached to br-ex, but rely on kernel networking (ip routes and ip rules) to redirect the traffic to br-ex."18:20
noonedeadpunkor probably that's for incoming traffic only....18:20
noonedeadpunkbut then it's also slightly wrong, as I'd need vlan->vlan mapping, and if bond0 is part of br-ex, then packets appear on bond0 directly, not vlan interface18:25
mlavallehaleyb: It's almost 8pm in Madrid. I don't think ralonsoh will follow up with me. I'll be on PTO next week. So I propose to go back to the way I was handling the extension in https://review.opendev.org/c/openstack/neutron/+/90151318:54
ralonsohmlavalle, no18:55
ralonsohI'm working on this18:55
ralonsohbut no, we should not have an extension not declared in this list18:55
ralonsohand no, this is a problem in n-t-p test18:55
ralonsohinstead of this, you can propose a patch in n-t-p testing what is happening in this test18:56
ralonsohand why Neutron is returning an extension that is not loaded18:56
ralonsohor should not be loaded because you are using ovn-router and not ovn-router-ha18:56
mlavalleralonsoh: what is n-t-p testing?18:57
mlavalleralonsoh: what is n-t-p testing?19:00
ralonsoh_neutron-tempest-plugin19:00
mlavalleralonsoh_: so what did you mean above when you said you were working on this?19:03
ralonsoh_yes19:03
mlavallewhat did you mean? what are you working on?19:04
opendevreviewRodolfo Alonso proposed openstack/neutron-tempest-plugin master: TEST patch 901513  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/91083219:08
ralonsoh_mlavalle, ^this19:08
*** ralonsoh_ is now known as ralonsoh19:08
ralonsohmlavalle, these test are failing because Neutron is returning the extension "l3-ha", that should not be loaded because "ovn-router" plugin is used19:09
ralonsohand not "ovn-router-ha"19:09
ralonsohlocally I can't reproduce this error: Neutron is returning the extensions loaded correctly (I don't see "l3-ha")19:10
ralonsohbut there is something wrong in the test19:10
noonedeadpunkhm, is this change does anything except set attribute to HA? Meaning - what are practical differences with current behaviour of L3 routers in OVN?19:10
mlavalleralonsoh: ok, thanks. will wait for the results19:12
noonedeadpunkJust trying to understand for myself as don't see any obvious behaviour change in the patch19:12
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Add support for l3vpn with NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90650519:13
mlavallenoonedeadpunk: there is no change in behavior for ovn routers. It is directed towards user defined router flavors19:13
mlavallein that scenario, we just want to signal that ovn routers are ha by nature19:13
mlavallethat's all19:13
noonedeadpunkyeah, ok, thanks!19:13
mlavalleconsistency in the API19:13
noonedeadpunkthen probably we can easily change defaults to this new driver without changing anyones behaviour :)19:14
ralonsohand why not to implement the API (same as for OVS ones) and do not allow to change it?19:14
ralonsohbecause now we have an ovn router plugin that is not consistent with the API19:15
ralonsoh(same topic with DVR)19:15
ralonsohactually what is proposed now, is a config driven API19:15
ralonsohif ovn-router is selected, the ha API will fail19:15
mlavalleralonsoh: what you mean is an extension?19:16
ralonsohha is an API extension, yes19:16
ralonsohand is implemented for non-ovn routers19:16
ralonsohbut ovn routers don't implement it19:16
mlavalleralonsoh: yeap, so far I follow19:16
ralonsohso the proposal is to implement HA extension for ovn-router (and keep it as is now)19:17
ralonsohand force, in the server, to always have ha=True in OVN19:17
ralonsoh(that is true and not configurable)19:17
ralonsohand allow to create a router with and without "ha", the second one will fail in ml2/ovn19:18
ralonsohand if we unset this "ha" in an ovn router, same error19:18
mlavallemy proposal at this point is to have HA = tue only when the ovn-router-ha is used19:18
ralonsoh(as long as we can't define a non-ha ovn router)19:18
ralonsohyes but why?19:18
ralonsohthat makes no sense19:18
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Add support for l3vpn with NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90650519:18
ralonsohovn-router is ha by default19:19
ralonsohand always enabled19:19
mlavalleif the ovn-router plugin is used, the ha attribute is not not returned19:19
ralonsohso enable it19:19
ralonsohenable this extension in ovn-router19:19
ralonsohand return this value19:19
ralonsohand, by default, any new router will have ha=true19:19
noonedeadpunkyeah, that what confused me as well19:19
ralonsohand if we try to create a non-ha ovn-rotuer, raise an exception19:20
ralonsohsame if we want to change an ovn-rotuer ha flag19:20
noonedeadpunkthat a separate driver being defined makes most sense when behaviour is changed for end users19:20
noonedeadpunkand then you give user an option if to return HA router as HA or return HA as non-HA19:21
ralonsohand I think my proposal will be easier to implement (this is what I initially think)19:21
ralonsohmlavalle, in any case, because you'll be in PTO, I can propose something next monday and wait until you come back19:21
mlavalleralonsoh: sure, go ahead, we can discuss when I come back19:22
mlavallethanks!19:22
ralonsohperfect19:22
mlavalleralonsoh: the only point that I want to make is that I was trying to not have any changes in behavior, unless you are interested in router flavors19:23
mlavallewhich is a very limited number of users19:23
mlavallethat is why I wnt that way19:23
ralonsohha and dvr API is a tech debt in the OVN router code19:24
ralonsohso better to implement it19:24
noonedeadpunkwell, reporting HA is HA is fair change in behaviour, if you'd ask me...19:24
mlavalleok, cool, in that case we can kill two birds with one stone19:24
noonedeadpunkI can't imagine users complaining about it19:25
ralonsohthere will be, if the output change19:25
mlavalleralonsoh: so yeah go ahead and propose something and we discuss when I come back19:25
noonedeadpunkI'd pretty much treat it as bugfix rather then feature...19:26
noonedeadpunkmeaning - there was a tech debt and renderring was incorrect - it's fixed now19:26
noonedeadpunkbut anyway:)19:26
* noonedeadpunk was just looking for some help with ovn-bgp-agent...19:27
ralonsohnoonedeadpunk, please open a LP bug, this is the best way to track an issue19:27
ralonsohchecking the IRC logs, I see a long description19:27
ralonsohplease report that in launchpad and we'll triage this bug next tuesday19:28
noonedeadpunkI don't think it's an issue. Rather I'm not getting a basic things19:28
noonedeadpunk(or they're not fully described in docs)19:28
ralonsohI can help you very little with bgp agent19:29
noonedeadpunkAs eventually agent does everything it promises to do19:29
noonedeadpunkbut I'm not getting how traffic should exit br-ext.vlan interface and where it should flow further...19:29
ralonsohmaybe ltombaso, but on European working time19:29
noonedeadpunk++19:29
noonedeadpunkthanks, will try to bother folks on Monday19:30
ralonsohit's 2030 for me, have a nice weekend19:30
noonedeadpunksame for me :p19:30
opendevreviewMichel Nederlof proposed openstack/ovn-bgp-agent master: Add support for l3vpn with NB driver  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/90650520:01
fnordahlthis one has one +2, green CI and could use one more review and WF: https://review.opendev.org/c/openstack/neutron/+/878543 haleyb maybe?20:05
haleybfnordahl: that's finally green? let me look20:07
haleybfnordahl: approved, so i guess just the doc patch? it's still marked WIP20:08
fnordahlhaleyb: thanks a bunch, really appreachiate all the time you and others have put into reviewing this series. Yes the doc did not progress as far as I hoped this week, got tied up in various review feedback and hunting CI issues, but I will not drop that20:13
fnordahlhaleyb: I trust it would be OK to get the doc merged early next week?20:14
fnordahlIt's the client patches too, but that is perhaps on a different release/freeze schedule20:15
haleybfnordahl: yes, and we can always cherry-pick. and the client changes will probably need to do the same20:15
fnordahlI see there are some comments from Stephen, I'll look at those asap20:15
opendevreviewMerged openstack/neutron master: [OVN] Remove OVN_GATEWAY_INVALID_CHASSIS artifact  https://review.opendev.org/c/openstack/neutron/+/90930520:38
opendevreviewMerged openstack/neutron master: Make common Metadata Driver classes  https://review.opendev.org/c/openstack/neutron/+/89439920:59
opendevreviewMerged openstack/neutron master: [ovn] Add support for enable_default_route_bfd attribute  https://review.opendev.org/c/openstack/neutron/+/87854323:04
opendevreviewMerged openstack/neutron stable/xena: Add max limit to agent_down_time  https://review.opendev.org/c/openstack/neutron/+/90533123:05

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