14:00:51 #startmeeting networking 14:00:51 Meeting started Tue Aug 22 14:00:51 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:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:51 The meeting name has been set to 'networking' 14:00:54 hello all 14:00:56 \o 14:00:58 Hi 14:01:00 o/ 14:01:02 o/ 14:01:11 o/ 14:01:22 o/ 14:01:27 hi 14:01:45 o/ 14:01:56 o/ 14:02:02 ok, let's start 14:02:11 #topic announcements 14:02:19 #link https://releases.openstack.org/bobcat/schedule.html 14:02:44 very important this week: election nomination begins 14:03:01 so please send your candidacy mails to the mailing list 14:03:22 more info: https://governance.openstack.org/election/ 14:03:50 and we have the final release for the non-client libraries 14:04:03 os-ken: https://review.opendev.org/c/openstack/releases/+/892214 14:04:14 ovsdbapp: https://review.opendev.org/c/openstack/releases/+/892237 14:04:34 about https://review.opendev.org/c/openstack/releases/+/892120, I know this patch is older than the releases team one 14:04:46 but let's use the releases team one 14:04:55 frickler, in any case, thanks for proposing it 14:05:38 same as the previous week, just a reminder 14:05:53 we have a new openinfra episode 14:05:58 #link https://openinfra.dev/live/#all-episodes 14:06:07 and that's all I have this week 14:06:17 (we are getting closer to the release date!) 14:06:25 Am I missing something? 14:07:18 ok, let's move to bugs 14:07:21 #topic bugs 14:07:28 Report from obondarev: https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034777.html 14:07:41 (lucky you, that was an easy week) 14:07:48 true 14:07:53 only one unassigned bug 14:08:00 #link https://bugs.launchpad.net/neutron/+bug/2031520 14:08:43 I opened this bug because there could be (for sure) some confusion about DVR/SNAT in OVN with PF, load balancing, network types (tunelled or vlan), etc 14:09:14 so it could be very useful to have a documentation with all the config parameters, options and current implementation 14:09:18 and that's all! 14:09:21 people only file bugs on my week :-( 14:09:28 hehehehe 14:09:51 I'll try to take this bug at the end of this week, in any case, if some else didn't take it before 14:10:03 Am I missing any other bug you want to bring here? 14:10:16 it doesn't matter if it is an older bug 14:10:51 I think https://bugs.launchpad.net/neutron/+bug/2028651 is worth mentioning again 14:10:59 iiuc it still blocks octavia? 14:11:33 I need to check it, yes. But I don't know why the patch related introduced this regression 14:11:47 I mean https://review.opendev.org/c/openstack/neutron/+/882588 is preventing from using a VIP port as a VM port 14:12:23 I'll check it tomorrow morning, because gthiemonge will need it asap 14:12:56 frickler, did you have time to investifate it? 14:13:16 no, I'm just watching this from the outside 14:13:40 ok, I'll try to use the reproducer provided 14:14:12 any other bug? 14:14:42 This week isabek is the deputy, next week will be elvira. 14:14:43 ack? 14:14:47 o/ 14:14:47 ack o/ 14:14:50 thanks! 14:15:03 ok, let's jump to the next topic 14:15:06 #topic os-ken 14:15:16 I commented that before 14:15:25 frickler, pushed some patches for os-ken 14:15:41 and now we are releasing a new (and last for this cycle) release 14:15:53 hopefully that unblocks n-d-r 14:15:58 I hope si 14:16:00 so* 14:16:18 one side note from testing this is that the n-d-r job on os-ken is completely useless 14:16:18 and next release (during C), we'll try the new implementation with more time 14:16:38 why is so? 14:16:42 because it only tests the released os-ken, not the patch in question 14:17:05 Slawek Kaplonski proposed openstack/neutron master: [S-RBAC] Add service role in neutron policy https://review.opendev.org/c/openstack/neutron/+/886724 14:17:48 also I'm still not sure what actually happened that caused this regression 14:17:49 frickler, but I'm checking the "neutron-tempest-plugin-dynamic-routing" definition 14:17:55 and required-projects: os-ken 14:18:22 that does not seem to be enough 14:18:39 also os-ken is installed twice, once in the neutron venv and once in the tempest venv 14:18:50 but both get installed from pypi 14:19:53 I don;'t understand, if os-ken is in required projects, it should be git cloning the project and installing from source 14:19:59 I'll open a LP bug for this 14:20:48 it is not getting installed directly, just as dependency of n-d-r, I think that's what the issue comes from, but didn't check yet in detail 14:21:06 but would be nice if one of the CI ppl could have a look, too 14:21:10 I'll check the job logs before creating the LP bug 14:21:31 but yes, we should be able to install whatever version of os-ken we need 14:22:12 ok, let's move to the next topic then 14:22:17 #topic community_goals 14:22:23 1) Consistent and Secure Default RBAC 14:22:34 slaweq, https://bugs.launchpad.net/neutron/+bug/2026182 14:22:42 (I think I'll change the title of this section) 14:23:26 ok, I'll ping him later 14:23:37 there is an ongoing patch ready to be reviewed 14:23:40 #link https://review.opendev.org/c/openstack/neutron/+/886724 14:23:48 hi 14:23:50 but we won't merge it during this release 14:23:54 hi 14:24:08 I think that patch https://review.opendev.org/c/openstack/neutron/+/886724 is ready if You have time to release it 14:24:15 *to review 14:24:17 sorry :) 14:24:19 perfect! 14:24:38 it's not that big really as it mostly adds unit tests 14:24:50 and changes some of the policies (but not that many) 14:24:52 just one heads-up, I don't think we should merge it during this release 14:24:56 just in case 14:25:08 and service role is not mandatory during Bobcat 14:25:24 sure, we can wait for the beginning of the next cycle with it 14:25:30 and for that we need any change in nova for example? 14:25:35 it's fine for me 14:26:05 they should add this new role in the configuration and make these calls using it 14:26:08 Merged openstack/neutron stable/ussuri: [OVN] ovn-db-sync check for router port differences https://review.opendev.org/c/openstack/neutron/+/892183 14:26:13 lajoskatona I don't think so as we already had "advsvc" role 14:26:22 ok, thanks 14:26:34 but is Nova using it? 14:26:37 this patch actually deprecates it and renames it to the "service" role to be consistent with new policies and all projects 14:26:54 but CI is happy with it so far 14:28:10 sorry but I don't understand that 14:28:19 ADVSVC role was an internal one 14:28:32 only used in Neutron 14:29:39 yes, and now our context.is_advsvc returns True in both cases - if it's advsvc role or service role: https://github.com/openstack/neutron-lib/blob/master/neutron_lib/context.py#L84 14:30:09 ok, so we have "converted" this Neutron role to service role 14:30:16 yes 14:30:18 ok, understood 14:30:26 but with keeping old name for now too 14:30:40 in any case, you have moved some operations to be only performed by this new role 14:30:46 port binding, for example 14:31:08 yes 14:31:38 ok, maybe we could have some rants from user in a future 14:31:41 as it's not needed to be available for admin user and we can just allow it to the advsvc/service role 14:31:57 if they want to make this kind of operations manually (for debugging or testing) 14:32:21 it's just default policy and can be always overwritten in the policy.yaml file in such case 14:32:27 right 14:32:33 ok, sorry for this time 14:32:40 no problem 14:32:44 I only wanted to have some answers! 14:32:47 thx for the questions about it 14:32:50 thanks! 14:32:57 next section 14:33:03 2) Neutron client deprecation 14:33:07 lajoskatona, please 14:33:18 the usual etherpad: https://etherpad.opendev.org/p/python-neutronclient_deprecation 14:33:44 what is ongoing the sfc work: https://etherpad.opendev.org/p/python-neutronclient_deprecation#L40 14:34:04 but I suppose in SDK we have to wait with it till the new release will start 14:34:19 is it possible to have the sdk patches during this week? 14:34:24 before the release 14:34:50 I can ask sdk team 14:35:03 that could be perfect 14:35:08 and if you have time please review it, that can be a push for the malso :-) 14:35:14 sure 14:35:22 and I have approved the n-lib patch 14:35:35 I had it open today but I didn't push the buttong 14:35:35 Another thing is that I started to play with Horizon, but that is really just playing with it 14:35:47 ralonsoh: thanks 14:35:58 horizon is another beast... 14:36:03 https://review.opendev.org/c/openstack/horizon/+/891205 14:36:34 yes, it has some traps which I hit on my first try :-) 14:36:51 but yes, we can propose incremental changes in horizon 14:36:58 but anyway I got some help in review from the horizon team, so at least there's some attention 14:36:59 that could be easier, for sure 14:37:00 does n-lib also count as non-client lib and should be frozen this week? 14:37:06 nope 14:37:32 only (for us) os-ken and ovsdbapp 14:38:04 I thought n-lib also 14:38:21 let me check but I'm almost sure 14:38:26 ok 14:38:38 for the neutron-client topic, that's all from me 14:38:45 neutron-lib too AFAIK 14:38:48 both n-lib and os-ken have "type:library" 14:38:57 frickler exactly 14:39:11 ovn-octavia-provider is not in that category but n-lib is 14:39:35 so I'll ping release folks 14:39:44 (or maybe they didn't have time yet to push the patch) 14:39:56 but do we need new release of n-lib now? 14:40:04 it was released about 2-3 weeks ago 14:40:09 do we have anything new there? 14:40:23 yes but we need the cycle last release 14:40:28 and this is the week for that 14:40:39 I just checked and there is nothing new: 14:40:52 tools/list_unreleased_changes.sh master openstack/neutron-lib 14:40:52 [ Unreleased changes in openstack/neutron-lib (master) ] 14:40:52 Changes between 3.8.0 and 4f862dac 14:40:55 It was the last release 3 weeks ago: https://review.opendev.org/c/openstack/releases/+/890038 14:40:59 apart from lajoskatona patch, I don't think there is anything else pending 14:41:32 so this is why release folks didn't send a patch 14:41:39 yes 14:41:39 because there were no new patches 14:41:42 yeah possible 14:42:02 but if we want to merge and release something, that's fine if we will do it this week 14:42:07 lajoskatona, do you need https://review.opendev.org/c/openstack/neutron-lib/+/887193 during this cycle? 14:42:13 if so, we can release a new one 14:42:20 if not, we can keep the current one 14:42:34 api-ref don't need to be released 14:42:35 I dont' think so 14:42:40 it's just documentation 14:42:44 it's always rendered from the master branch IIRC 14:42:47 perfect, so let's keep the current version we have now 14:42:52 +1 14:43:19 and that's all I have here 14:43:21 let's move then 14:43:28 #topic on_demand 14:43:49 last weel stephenfin pinged me about including tox py310 with sqlalchemy master 14:44:14 as you saw last days, I added it and is now voting in the check queue 14:44:37 I also removed our local py311 implementation and we are now using the glocal openstack-tox-py311 14:44:49 I hope it won't break too often, especially now when we are close to the release 14:45:04 and fixed, as recommended by frickler, our bindep file for some debian library issues with py311 14:45:14 so far, we are good now 14:45:24 py311 should still be non-voting until next cycle 14:45:25 slaweq, the 2.0 release is in the oven 14:45:44 ++ 14:45:46 frickler, yes but at least we should manually check if we break something 14:46:02 one sec 14:46:16 yes, just responded to slaweq that it should not block the release 14:46:26 https://review.opendev.org/c/openstack/requirements/+/879743 14:46:38 frickler I was thinking more about py310 with sqlalchemy master :) 14:46:46 I know py311 is non voting for now 14:46:58 actually I prefer having it in the check queue 14:46:59 ah, then I misread that 14:47:18 2 weeks ago we introduced something that break the 2.0 compatibility 14:47:21 "select 1;" 14:47:33 now is fixed 14:48:08 ok, something else (apart from my dramas with sqlalchemy 2.0 hehehe) ?? 14:48:25 just FYI 14:48:31 I made no progress with building OVN 23.06 yet, did anyone test that successfully? 14:48:52 this week I sent email https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034778.html with proposal of some changes to the neutron related questions in OS user survey 14:49:08 I need to check one more thing and reply to last email from fungi still 14:49:16 that's all from me 14:49:22 can I get someone to push this over the edge, please: https://review.opendev.org/c/openstack/python-openstackclient/+/891557? 14:49:27 and thx all for the feedback in the etherpad 14:49:35 I agree that most people choose "OVS" but really mean "ML2/OVS" 14:49:43 slaweq, thanks for the time on this 14:49:52 mlavalle I will check this patch 14:50:00 slaweq: thanks 14:50:26 frickler, yes, always, no one is manyally configuring OVS without an orchestrator 14:50:36 same as OVN or SRIOV 14:50:57 frickler: I just checked and I have a devstack with OVN main, and northd said it is ovn-northd 23.06.90 14:51:17 frickler: I have OVS_BRANCH="v3.1.0" 14:51:39 lajoskatona: oh, testing with main would be an option I guess, yes, I can try that 14:51:43 but is this the git submodule hash recommended by OVN repo? 14:52:03 each OVN branch has a defined OVS branch provided by git submodule 14:52:35 to tell the truth I stolen it from one debvstack job after some unsuccessful tries 14:52:54 frickler, did you try that? I think I commented that in IRC last week 14:53:11 I did not try that yet, os-ken got in the way 14:53:27 but I will test both variants this week 14:53:42 ping me if you still have problems with this after using the recommended version 14:53:53 ack, thx 14:54:01 remember that in 5 mins we have the CI meeting 14:54:11 ++ 14:54:12 I'll give you some time to grab some coffee 14:54:17 see you in 5 mins 14:54:21 o/ 14:54:23 #endmeeting