| opendevreview | Merged openstack/neutron master: [OVN] Add vnic_type and binding profile capabilities to LSP info https://review.opendev.org/c/openstack/neutron/+/867359 | 02:16 |
|---|---|---|
| opendevreview | Merged openstack/neutron master: [OVN] Introduce the new OVN Neutron Agent https://review.opendev.org/c/openstack/neutron/+/869909 | 02:16 |
| *** ges_ is now known as ges | 09:21 | |
| lajoskatona | ralonsoh: Hi, gmann sent a mail regarding pypi extra maintainers over openstack-ci: https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848.html | 09:26 |
| lajoskatona | ralonsoh: I added this topic to on-demand agenda of the meeting, and I updated the etherpad (https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup ), but would be good to discuss I think together | 09:27 |
| ralonsoh | lajoskatona, did you add the names for the neutron related projects? | 09:29 |
| ges | Hello! We are currently thinking about adding a little debugging endpoint to the agents, notably to be able to inspect the remote resource cache. For now it looks like a unix socket the agent listens on that answers to basic commands (dump_resource_cache, or run a pdb session). Do you think that could be of intereset upstream? | 09:32 |
| ralonsoh | lajoskatona, anyway, thanks for this list, we'll review it today during the team meeting | 09:33 |
| lajoskatona | ralonsoh: I listed the stadiums or libs projects from the list, but perhaps I overlooked some :-) | 09:41 |
| ralonsoh | lajoskatona, no no, that's ok. Thanks a lot | 09:41 |
| ralonsoh | we'll check this list later today in the meeting | 09:41 |
| opendevreview | Gregory Thiemonge proposed openstack/ovn-octavia-provider master: WIP Removing python-neutronclient code https://review.opendev.org/c/openstack/ovn-octavia-provider/+/870514 | 09:49 |
| ralonsoh | ges, you can use https://github.com/openstack/nova/blob/master/doc/source/contributor/development-environment.rst#using-a-remote-debugger | 09:59 |
| ralonsoh | or you can use https://docs.openstack.org/neutron/latest/contributor/policies/gate-failure-triage.html | 09:59 |
| ralonsoh | using pdb or rpdb for this | 09:59 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron master: [OVN] New OVN Neutron Agent extension: QoS for HWOL https://review.opendev.org/c/openstack/neutron/+/870115 | 10:09 |
| ges | ralonsoh: thanks! I've used remote pdb in some places, but it's often useless at detecting or working on an issue that goes away after restarting the agent. To give you an example, we sometimes lose messages in rabbitmq and we would want to check whether resources in the cache are in sync with the ones in DB. That's why we are thinking about a permanent endpoint and not some | 10:12 |
| ges | set_trace() we could add to the code here and there. I think it's a different use-case, no? | 10:12 |
| ralonsoh | ges, I don't think the community will agree on having an open backport for debugging. Maybe you can propose to have an API to retrieve from the neutron server what is the info in the agent | 10:13 |
| ralonsoh | this could be an idea | 10:13 |
| ralonsoh | you can propose it in a launchpad bug as a RFE | 10:14 |
| ralonsoh | and propose it in the drivers meeting # | 10:14 |
| ralonsoh | #link https://meetings.opendev.org/#Neutron_drivers_Meeting | 10:14 |
| amorin | hey team | 10:16 |
| amorin | I am with ges involved in this topic, I fact we want something out of band, to collect metrics/status of the agent, without neutron-server involved | 10:16 |
| amorin | it looks like the oslo_messaging rpc_ping endpoint, which you we enabled to reach the agents without going through the server | 10:17 |
| amorin | but this time, we want metrics | 10:17 |
| ralonsoh | what metrics? | 10:18 |
| amorin | like number of local lvm in lvm-manager | 10:18 |
| amorin | or version of objects in the remote-cache | 10:19 |
| amorin | we started this because we found some inconsistencies within security groups, some of our agent were not managing them correctly | 10:19 |
| amorin | while we dont know yet the root cause, we wanted to dump the remote-cache live in order to see which agent is having which version of the objects | 10:20 |
| ralonsoh | amorin, and how do you want to expose this debugging endpoint? do you want to be able to talk directly to the agent? | 10:22 |
| ralonsoh | I don't think this is going to be allowed nor accepted | 10:22 |
| amorin | ges implemented something based on a local socket | 10:22 |
| ralonsoh | like a pdb | 10:23 |
| amorin | yeah | 10:23 |
| ralonsoh | you can propose it but as commented, I don't think this will be accepted | 10:23 |
| ralonsoh | this is an official backdoor | 10:24 |
| ralonsoh | and a security risk | 10:24 |
| amorin | of course, this should be secured and false by default | 10:26 |
| amorin | we are preparing a paste to show you exemple | 10:27 |
| amorin | example* | 10:27 |
| ges | I don't think it's a security risk more than say, having configuration files on the server, provided the socket has the correct rights. | 10:31 |
| ges | Here's the paste of what we came up with: https://paste.opendev.org/show/bsXrvJYFpIPnJhsN6bOi/ | 10:34 |
| lajoskatona | ges, ralonsoh, amorin: Hi, this idea looks passing to the healthcheck API | 10:41 |
| lajoskatona | ges, ralonsoh, amorin: oslo-middlerware gives endpoint for this, but as I remember there is no pdb option for example | 10:42 |
| lajoskatona | ges, ralonsoh, amorin: When I playedd with it a lot of debate come and we agreed to forget it, but would be interesting to check it again, see my patch and the comments on it: https://review.opendev.org/c/openstack/neutron/+/731554 | 10:43 |
| amorin | lajoskatona: this is a good idea what you propose, we are also doing that on our side with external tools (doing neutron agent list, checking RPC link, etc) | 10:46 |
| amorin | This time, we want to have deeper "live" info about the agent | 10:46 |
| opendevreview | Lajos Katona proposed openstack/neutron-lib master: api-ref: Add dragent scheduler api-ref https://review.opendev.org/c/openstack/neutron-lib/+/870582 | 10:47 |
| amorin | anyway we are going to maintain something like this downstream, we just wanted to let you know and see if it could be benefit for the community as well | 10:48 |
| ges | lajoskatona: It could fit there, but the healtcheck API doesn't seem to give any introspection capability. And I think it is really important for us to have an out-of-band solution. | 10:49 |
| ralonsoh | ges, amorin please propose this as a launchpad bug and in the drivers meeting | 11:02 |
| opendevreview | Maurice Escher proposed openstack/neutron master: allow manila ports to do multiple port binding for ML2 https://review.opendev.org/c/openstack/neutron/+/869295 | 12:42 |
| opendevreview | Lajos Katona proposed openstack/neutron master: Fullstack: Wait placement process fixtrue to really stop https://review.opendev.org/c/openstack/neutron/+/870956 | 13:42 |
| opendevreview | Lajos Katona proposed openstack/neutron master: Fullstack: Wait placement process fixtrue to really stop https://review.opendev.org/c/openstack/neutron/+/870956 | 13:53 |
| *** dasm|off is now known as dasm | 13:58 | |
| ralonsoh | PING LIST SERVICE (provided by OpenStack): bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, sahid, slawek, tobias-urdin, ykarel, lajoskatona | 13:59 |
| ralonsoh | 1 min left to the Neutron meeting | 13:59 |
| bcafarel | fancy service :) | 13:59 |
| ralonsoh | hehehe | 13:59 |
| mlavalle | thank you ralonsoh | 14:00 |
| ralonsoh | #startmeeting networking | 14:00 |
| opendevmeet | Meeting started Tue Jan 24 14:00:19 2023 UTC and is due to finish in 60 minutes. The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| opendevmeet | The meeting name has been set to 'networking' | 14:00 |
| mlavalle | o/ | 14:00 |
| ralonsoh | hello all | 14:00 |
| obondarev | hi | 14:00 |
| haleyb | o/ | 14:00 |
| frickler | \o | 14:00 |
| lajoskatona | o/ | 14:00 |
| ykarel | o/ | 14:00 |
| slaweq | o/ | 14:00 |
| ralonsoh | let's start | 14:01 |
| ralonsoh | #topic announcements | 14:01 |
| ralonsoh | #link https://releases.openstack.org/antelope/schedule.html | 14:01 |
| ralonsoh | we are in R-8 | 14:01 |
| ralonsoh | three weeks before the A-3 milestone | 14:01 |
| ralonsoh | that is the feature freeze! | 14:02 |
| ralonsoh | along with the requirements and clients freeze | 14:02 |
| ralonsoh | please be aware of this | 14:02 |
| ralonsoh | Also please check the Openinfra presentations | 14:02 |
| ralonsoh | #link https://openinfra.dev/live/#all-episodes | 14:02 |
| ralonsoh | there is a new one | 14:03 |
| ralonsoh | Distributing OpenStack Architecture with BGP and Kubernetes Integration | 14:03 |
| ralonsoh | #link https://www.youtube.com/watch?v=r8WLM9TM6w4 | 14:03 |
| mlavalle | ++ | 14:03 |
| ralonsoh | it could be a bit scary, but this presentation provides a lot of information | 14:04 |
| lajoskatona | thanks the topic is really interesting and it is on my watch list | 14:04 |
| ralonsoh | and a very good starting point to know aboyt BGP (and kubernetes) | 14:04 |
| ralonsoh | let's move to the next topic then | 14:05 |
| ralonsoh | #topic bugs | 14:05 |
| ralonsoh | this is the report from jlibosva | 14:05 |
| ralonsoh | #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031868.html | 14:05 |
| ralonsoh | most of the bugs are attended now | 14:05 |
| elvira | hi, sorry for the delay o/ | 14:05 |
| ralonsoh | hi! | 14:05 |
| ralonsoh | but we have 2 of them still not assigned | 14:05 |
| ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/2003532 | 14:06 |
| ralonsoh | ^^ for this one I'm spawning an env to try to reproduce it | 14:06 |
| ralonsoh | but I didn't have time to start with it | 14:06 |
| ralonsoh | you are welcome to check it too | 14:06 |
| ralonsoh | the second one | 14:07 |
| ralonsoh | #link https://bugs.launchpad.net/neutron/+bug/2003359 | 14:07 |
| ralonsoh | it seems to be a problem with a race condition | 14:07 |
| ralonsoh | if you create and delete routers too fast | 14:07 |
| ralonsoh | there is also a reproducer, forcing a wait sleep during the GW port creation | 14:08 |
| ralonsoh | can anyone check this one? | 14:08 |
| lajoskatona | I can check | 14:08 |
| ralonsoh | lajoskatona, thanks a lot! | 14:08 |
| ralonsoh | we also have a new RFE but we'll talk about this one later | 14:09 |
| ralonsoh | this week obondarev is the deputy, next week will be isabek | 14:09 |
| isabek | o/ | 14:09 |
| obondarev | yep, on it | 14:09 |
| ralonsoh | thanks folks | 14:09 |
| ralonsoh | ok, I think we can move to the next topic | 14:10 |
| ralonsoh | #topic specs | 14:10 |
| ralonsoh | #link https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open | 14:10 |
| ralonsoh | we have a new one: https://review.opendev.org/c/openstack/neutron-specs/+/870030 | 14:10 |
| ralonsoh | the RFE will be discussed this Friday | 14:10 |
| ralonsoh | #link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers | 14:11 |
| ralonsoh | about the second one https://bugs.launchpad.net/neutron/+bug/2003095 | 14:11 |
| ralonsoh | I'll ping the reporter to have it discussed during the drivers meeting | 14:11 |
| ralonsoh | so, in advance, please attend to the drivers meeting next Friday | 14:12 |
| ralonsoh | anything else on this topic? | 14:12 |
| ralonsoh | ok, let's move to the next topic | 14:13 |
| lajoskatona | Just a small one: the first patches are up for https://specs.openstack.org/openstack/neutron-specs/specs/2023.1/ovs-tx-steering.html so if you have time please check them (from rubasov :-) | 14:13 |
| ralonsoh | I'm trying to find the links | 14:14 |
| lajoskatona | I just found the api-def: https://review.opendev.org/c/openstack/neutron-lib/+/870080 | 14:15 |
| ralonsoh | ok, it will be better to use the launchpad bug topic | 14:15 |
| ralonsoh | lajoskatona, ok thanks a lot, I'll add it to my review pile | 14:16 |
| lajoskatona | thanks folks | 14:17 |
| ralonsoh | let's move to the next topic | 14:17 |
| ralonsoh | #topic community_goals | 14:17 |
| ralonsoh | 1) Consistent and Secure Default RBAC | 14:17 |
| ralonsoh | #link https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/867518 | 14:17 |
| ralonsoh | slaweq, pushed a DNM patch using the new RBAC policies | 14:18 |
| ralonsoh | did you have time to check what is failing there? | 14:18 |
| slaweq | ralonsoh not yet | 14:18 |
| slaweq | sorry | 14:18 |
| ralonsoh | no no, no problem | 14:19 |
| ralonsoh | btw, will we have the new RBAC enforced this release? | 14:19 |
| ralonsoh | I mean, we'll we swap to this by default? | 14:19 |
| slaweq | I'm not sure if it's not too late | 14:19 |
| slaweq | I will sync with gmann about it | 14:19 |
| ralonsoh | I think so too | 14:19 |
| ralonsoh | thanks! | 14:19 |
| lajoskatona | if yes I suppose it will be a good release with nervous people running around :-) | 14:20 |
| ralonsoh | yeah, I don't know the status of other projects | 14:20 |
| ralonsoh | but from Neutron point of view, we need to polish those failing tests | 14:20 |
| ralonsoh | most probably missing permissions, users, etc | 14:21 |
| slaweq | yes, it seems that mostly our internal RBAC isn't working fine with those new policies | 14:21 |
| slaweq | I will open bugs for that today or tomorrow so we can work on them | 14:21 |
| ralonsoh | that will be perfect | 14:22 |
| ralonsoh | and thanks again | 14:22 |
| ralonsoh | next one | 14:22 |
| ralonsoh | 2) Neutron client deprecation | 14:22 |
| ralonsoh | #link https://review.opendev.org/q/topic:bug%252F1999774 | 14:23 |
| lajoskatona | +1, thanks for the link | 14:23 |
| ralonsoh | I hope we have the trunk commands migrated and released soon | 14:23 |
| ralonsoh | we need another +2 in the SDK patch | 14:23 |
| ralonsoh | and then we have the other sdk patch | 14:23 |
| ralonsoh | #link https://review.opendev.org/c/openstack/openstacksdk/+/869485 | 14:23 |
| mlavalle | I can look at it today | 14:23 |
| ralonsoh | thanks | 14:24 |
| lajoskatona | mlavalle: you also have +2 rights for SDK< | 14:24 |
| lajoskatona | ? | 14:24 |
| ralonsoh | the SDK bgp patch is OK, IMO | 14:24 |
| mlavalle | lajoskatona: ah no | 14:24 |
| lajoskatona | :-( | 14:24 |
| ralonsoh | we can ping stephenfin or Artem | 14:24 |
| lajoskatona | I go and ask on sdk channel than to ask for review than | 14:24 |
| ralonsoh | cool | 14:25 |
| lajoskatona | ralonsoh: ack | 14:25 |
| ralonsoh | and again, thanks for working on this | 14:25 |
| slaweq | I have +2 in SDK repo, I will review it | 14:25 |
| lajoskatona | frickler: if you can check the BGP patches that would be really helpful | 14:25 |
| ralonsoh | ah, btw, just asking | 14:25 |
| ralonsoh | do we want to push the patch removing all CLI from neutronclient? | 14:25 |
| slaweq | ralonsoh I think it is time to do it finally | 14:26 |
| ralonsoh | (do we really need that? or we can wait until we definetly remove the repo) | 14:26 |
| ralonsoh | ok | 14:26 |
| mlavalle | I think so | 14:26 |
| ralonsoh | I'll do it this week | 14:26 |
| slaweq | it was deprecated some time ago already | 14:26 |
| slaweq | ralonsoh++ | 14:26 |
| frickler | lajoskatona: I'll be away for the coming two weeks, will have to wait until after that | 14:26 |
| mlavalle | lajoskatona: would you give me again the pointer to the etherpad? | 14:26 |
| lajoskatona | frickler: ack, not urgent I think, it will be a long story anyway :-) | 14:26 |
| lajoskatona | mlavalle: https://etherpad.opendev.org/p/python-neutronclient_deprecation | 14:27 |
| mlavalle | Thanks! | 14:27 |
| ralonsoh | I'll add this link to the bug | 14:27 |
| lajoskatona | ralonsoh: good idea, should have done that | 14:27 |
| ralonsoh | done | 14:28 |
| lajoskatona | thanks | 14:28 |
| ralonsoh | and I think we are done here | 14:28 |
| ralonsoh | the last topic is | 14:28 |
| ralonsoh | #topic on_demand | 14:28 |
| ralonsoh | lajoskatona, please | 14:28 |
| lajoskatona | thanks | 14:29 |
| lajoskatona | I added one, gmann sent a mail regarding the maintainers on pypi: https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848.html | 14:29 |
| lajoskatona | there is an etherpad: https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup | 14:29 |
| lajoskatona | where I added our stadiums which suprisingly mostly have maintainers over openstack-ci | 14:30 |
| lajoskatona | and the goal is today that QA (or TC) want to have only openstack-ci as maintainer for all openstack projects | 14:30 |
| lajoskatona | I think this is a good goal, but as in the thread there are thngs which should be discussed | 14:31 |
| opendevreview | Arnaud Morin proposed openstack/neutron master: Set DVR qr-xyz interfaces DOWN on backup node https://review.opendev.org/c/openstack/neutron/+/869741 | 14:31 |
| ralonsoh | but if we have pypi mantainers, that means we'll have someone that can release without any permission from OpenStack | 14:32 |
| lajoskatona | if you check the etherpad some of the maintainers are now not active around openstack or Neutron, or even there is one really suspicious id (login.launchpad.net_179 ) | 14:32 |
| ralonsoh | yeah | 14:32 |
| lajoskatona | yes exactly, that happened with some horizon lib I think | 14:32 |
| ralonsoh | checking those Neutron related repos, all of them are actively mantained by the Neutron community | 14:33 |
| ralonsoh | I don't think we should allow external maintainers | 14:33 |
| obondarev | +1 | 14:34 |
| lajoskatona | yes, and I hope that no deployment or build system depends in the outside world to have these rights for these people | 14:34 |
| ralonsoh | for example, we all now otherwiseguy is the father of ovsdbapp. But if he wants to push something, he know how to push a patch and release (in openstack) a new version | 14:34 |
| lajoskatona | exactly | 14:34 |
| ralonsoh | so if you agree, I'll add the comment "Ok to remove additional maintainers" to all Neutron related repos | 14:35 |
| * otherwiseguy waves | 14:35 | |
| lajoskatona | and if there is some issue with the release the release team has the tools to fix it (I hope) | 14:35 |
| ralonsoh | exactly | 14:35 |
| lajoskatona | ok, that was it from me to have a quick discussion of this topic | 14:35 |
| ralonsoh | sorry, just for the records, do you mind to vote on this? | 14:35 |
| amotoki | I am fine with it. it is just because I created *-dashboard pypi projects per the project team guide | 14:36 |
| lajoskatona | +1 to keep only openstack-ci as maintainer | 14:36 |
| lajoskatona | amotoki: thanks | 14:36 |
| obondarev | same here, +1 | 14:36 |
| ralonsoh | ok, thanks, I'll update the etherpad | 14:37 |
| ralonsoh | and I have another topic | 14:37 |
| ralonsoh | #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031745.html | 14:37 |
| ralonsoh | this is related to the in-person PTG | 14:38 |
| ralonsoh | we know we have, at least this year, two virtual PTGs | 14:38 |
| mlavalle | +1 | 14:38 |
| ralonsoh | the point here is what about the Vancouver event? | 14:38 |
| ralonsoh | what should be the agenda? | 14:39 |
| mlavalle | at the very least pizza and beer | 14:39 |
| ralonsoh | you have proposed to have a lighweight agenda for this event | 14:39 |
| slaweq | mlavalle++ | 14:39 |
| ralonsoh | mlavalle, yeah but this is difficult to be justified | 14:39 |
| lajoskatona | Shall we open an etherpad and collect topics? | 14:39 |
| mlavalle | jokes aside, meeting in person is necessary after such a long time | 14:40 |
| ralonsoh | I mean, if we don't have a good planned agenda, this year ( | 14:40 |
| slaweq | and seriously, for sure some "feedback from operarors" or something like that | 14:40 |
| ralonsoh | lajoskatona, yes, that could be a very good starting point | 14:40 |
| ralonsoh | slaweq, yes, this is another good topic | 14:40 |
| ralonsoh | even better is that is done in person | 14:40 |
| ralonsoh | ok | 14:40 |
| ralonsoh | I'll reply to the mail chain | 14:40 |
| mlavalle | ralonsoh: do we have a deadline for an agenda? | 14:40 |
| ralonsoh | and the first think I'll do is to create this etherpad | 14:41 |
| ralonsoh | not really, I will ask TC folks | 14:41 |
| lajoskatona | thanks | 14:41 |
| ralonsoh | but just remember this Vancouver event is in june (13-15) | 14:41 |
| mlavalle | so I'm pretty sure we can como up with an agenda that includes operators feedback, pizaa / beer and more topics | 14:42 |
| lajoskatona | yeah, we started to beg for travel budget :-) | 14:42 |
| ralonsoh | lajoskatona, exactly! (and this is a very accurate verb) | 14:42 |
| mlavalle | let's start with the etherpad now | 14:42 |
| ralonsoh | I'll do it tomorrow morning, I'll send a mail | 14:42 |
| ralonsoh | and thanks for the feedback! | 14:43 |
| lajoskatona | Sorry I have to run for my kid to school, o/ | 14:43 |
| ralonsoh | sure | 14:43 |
| ralonsoh | I think we don't have nothing else in the agenda | 14:43 |
| ralonsoh | so thank you all for attending | 14:43 |
| ralonsoh | and remember today we don't have the CI meeting | 14:43 |
| ralonsoh | see you online! | 14:43 |
| obondarev | o/ | 14:43 |
| ralonsoh | #endmeeting | 14:43 |
| opendevmeet | Meeting ended Tue Jan 24 14:43:52 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:43 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/networking/2023/networking.2023-01-24-14.00.html | 14:43 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/networking/2023/networking.2023-01-24-14.00.txt | 14:43 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/networking/2023/networking.2023-01-24-14.00.log.html | 14:43 |
| opendevreview | Brian Haley proposed openstack/neutron master: Change flag check order in wait_until_address_ready() https://review.opendev.org/c/openstack/neutron/+/871389 | 14:46 |
| mlavalle | o/ | 14:47 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/xena: Since OVN 20.06, config is stored in "Chassis.other_config" https://review.opendev.org/c/openstack/neutron/+/871637 | 15:30 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/wallaby: Since OVN 20.06, config is stored in "Chassis.other_config" https://review.opendev.org/c/openstack/neutron/+/871640 | 16:20 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/wallaby: Since OVN 20.06, config is stored in "Chassis.other_config" https://review.opendev.org/c/openstack/neutron/+/871640 | 16:44 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/xena: Since OVN 20.06, config is stored in "Chassis.other_config" https://review.opendev.org/c/openstack/neutron/+/871637 | 16:46 |
| opendevreview | Rodolfo Alonso proposed openstack/neutron stable/wallaby: Since OVN 20.06, config is stored in "Chassis.other_config" https://review.opendev.org/c/openstack/neutron/+/871640 | 16:47 |
| opendevreview | Jakub Libosvar proposed openstack/neutron master: ovn-migration: Don't clone interfaces to br-migration https://review.opendev.org/c/openstack/neutron/+/871650 | 17:52 |
| opendevreview | Merged openstack/neutron-lib master: add DEVICE_OWNER_MANILA_PREFIX to constants https://review.opendev.org/c/openstack/neutron-lib/+/869294 | 18:38 |
| opendevreview | Brian Haley proposed openstack/neutron master: Add doc note on nf_conntrack module requirement https://review.opendev.org/c/openstack/neutron/+/871659 | 20:19 |
| *** dasm is now known as dasm|off | 23:09 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!