14:00:24 <slaweq> #startmeeting networking 14:00:24 <opendevmeet> Meeting started Tue Aug 31 14:00:24 2021 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:24 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:24 <opendevmeet> The meeting name has been set to 'networking' 14:00:28 <mlavalle> o/ 14:00:30 <slaweq> o/ 14:00:31 <ralonsoh> hi 14:00:35 <slaweq> bcafarel++ :) 14:00:38 <ganso> o/ 14:00:55 <bcafarel> and o/ 14:00:57 <njohnston> o/ 14:01:19 <lajoskatona> o/ 14:01:30 <slaweq> #topic Announcements 14:01:31 <haleyb> hi 14:01:45 <slaweq> first, and the most important 14:01:58 <slaweq> please welcome lajoskatona as our new PTL for Yoga :) 14:02:02 <obondarev> hi 14:02:03 <slaweq> congtats lajoskatona 14:02:11 <gibi> \o/ 14:02:19 <lajoskatona> Thank you:-) 14:02:22 <bcafarel> crongratulations lajoskatona! 14:02:30 <ralonsoh> congrats! 14:02:36 <mlavalle> congratulations! 14:02:47 <bcafarel> and thanks again slaweq for the great 2 years of service :) 14:02:51 <obondarev> lajoskatona: congrats! 14:03:17 <haleyb> congrats and good luck! 14:03:29 <slaweq> thx bcafarel :) 14:03:32 <slaweq> ok, next one 14:03:34 <slaweq> Xena cycle calendar https://releases.openstack.org/xena/schedule.html 14:03:42 <slaweq> we are in the final stage of the Xena cycle 14:03:55 <thomasb06> slaweq: mlavalle: Hello. Last week I made contact with Kendall Nelson who is the point of contact for Academia at Opendev. She proposed to me to start with OpenStaceSDK and OpenStackClient as it gives a chance to see a bit of everything in OpenStack. And there are smaller chuncks for newcomers too. So I'd rather join her on these two projects. (But as Arnold Scharzenegger used to say: «I'll be 14:03:55 <thomasb06> back.» Those were the days) 14:04:01 <slaweq> this week is Xena-3 milestone and final release for client libraries - we need to do release of python-neutronclient 14:04:39 <mlavalle> thomasb06: that's good 14:04:50 <slaweq> thomasb06: sure, feel free to reach out to us if You will need any help regarding Neutron :) 14:05:03 <slaweq> neutronclient opened patches https://review.opendev.org/q/project:openstack/python-neutronclient+branch:master+status:open 14:05:06 <thomasb06> Thank you 14:05:34 <slaweq> my only question is about 2 from manub which are related to bgp speakers 14:05:51 <ralonsoh> why not in OSC? instead of n-client 14:05:52 <slaweq> do we want to prioritize them this week and get them merged before thursday? 14:06:29 <lajoskatona> ralonsoh: +1, I had a discussion few weeks ago with slaweq and amotoki: https://meetings.opendev.org/irclogs/%23openstack-neutron/%23openstack-neutron.2021-08-16.log.html 14:08:40 <lajoskatona> sorry with timestamp: https://meetings.opendev.org/irclogs/%23openstack-neutron/%23openstack-neutron.2021-08-16.log.html#t2021-08-16T12:49:26 14:09:38 <lajoskatona> the summary I think is: "so my answer to your question is to implement the support for a new feature of both CLI (OSC plugin) and bindings in dynamic-rotuing in python-neutronclient." 14:09:44 <lajoskatona> from amotoki 14:10:14 <ganso> sorry to interrupt, but "as of now, neutronclient OSC plugin consumes python bindings in python-neutronclient repo, so adding corresponding stuff to the neutronclient repo would be straight-forward." 14:10:20 <ganso> ^ is not very clear to me 14:10:35 <ganso> I heard python-neutronclient was deprecated and not accepting new patches 14:11:34 <ganso> forgot to include that amotoki mentioned the above statement I quoted 14:12:48 <slaweq> ganso: neutronclient is in fact 2 things - 1st, it's CLI client for neutron and that is deprecated 14:13:20 <slaweq> but also 2nd - it has python bindings, like SDK and that part isn't deprecated and still can accept patches 14:13:46 <ganso> oh I see, its "library" part that is consumed by other projects is still going forward 14:13:57 <slaweq> but probably amotoki is the best one to provide full explanation about it 14:14:42 <slaweq> lajoskatona: so IIUC (I didn't check those patches fully yet) those patches from manub have that "CLI" part so we don't need to merge them, right? 14:15:17 <manub> slaweq,regarding the bgp speaker related patches, it is not very urgent to merge it 14:15:29 <slaweq> manub: ok 14:15:31 <slaweq> thx 14:15:31 <lajoskatona> slaweq: agree, 14:15:40 <lajoskatona> ah, thanks manub 14:15:42 <slaweq> so we should be good to go now with python-neutronclient 14:15:55 <slaweq> thx 14:16:17 <slaweq> ok, let's move on 14:16:24 <slaweq> PTG in October 14:16:26 <slaweq> https://etherpad.opendev.org/p/neutron-yoga-ptg 14:16:42 <slaweq> just a reminder: please add Your ideas to the etherpad 14:16:55 <slaweq> next one 14:16:57 <slaweq> Operators pain points: http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024487.html 14:17:09 <slaweq> please read it - maybe You will want to help somehow in that effort 14:17:44 <slaweq> that are all announcements from me 14:17:54 <slaweq> do You have anything else to announce today? 14:19:05 <bcafarel> on releases schedule there was an email on missing deliverable for ovn-octavia-provider too 14:19:46 <slaweq> bcafarel: yes, thx 14:19:58 <slaweq> I proposed release today: https://review.opendev.org/c/openstack/releases/+/806716 14:20:15 <slaweq> but tbh we have 1.1.0 already released for Xena 14:20:31 <slaweq> so it seems for me like that this project was in that email by mistake 14:20:37 <bcafarel> slaweq++ 14:20:53 <bcafarel> probably because 1.1.0 was too long ago compared to Xena dates (at least in the check script) 14:21:13 <slaweq> maybe 14:21:36 <slaweq> but it is in deliverables/xena/ovn-octavia-provider.yaml file in the repo 14:21:39 <slaweq> so should be ok 14:23:27 <slaweq> ok, let's move on to the next topic 14:23:31 <slaweq> #topic Blueprints 14:23:37 <slaweq> Neutron Xena-3 https://bugs.launchpad.net/neutron/+milestone/xena-3 14:23:45 <slaweq> do You have any updates about them? 14:25:49 <slaweq> if not, I think I will move all of them to neutron-next now as I don't think any of them will be ready this week 14:25:56 <slaweq> so we should push them back to next cycle 14:26:04 <slaweq> are You agree with that? 14:26:39 <ralonsoh> ok 14:26:56 <lajoskatona> +1 14:27:06 <gibi> fyi nova is landing the minimum guaranteed pps series 14:27:21 <gibi> but it is OK to have it in nova even if it is not landing in neutron 14:27:40 <gibi> as nova has still support the old style port resource_request 14:28:18 <gibi> the whole thing in nova is guarded by the existence of the neutron port-resource-request-groups API extension 14:29:24 <lajoskatona> This is the series for min pps in neutron: https://review.opendev.org/q/topic:%2522bp/qos-minimum-guaranteed-packet-rate%2522+(status:open+OR+status:merged)+project:openstack/neutron 14:29:56 <gibi> thanks lajoskatona 14:30:07 <slaweq> it's already pushed to the next release on neutron side 14:30:11 <gibi> ack 14:32:01 <slaweq> ok, let's move on 14:32:06 <slaweq> #topic Bugs 14:32:13 <slaweq> hongbin was bug deputy last week. Report http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024523.html 14:32:29 <slaweq> it seems from that report that it was easy week 14:32:43 <slaweq> I saw there 2 unassigned issues 14:32:46 <slaweq> https://bugs.launchpad.net/neutron/+bug/1941537 - API policy issue, 14:32:47 <slaweq> https://bugs.launchpad.net/neutron/+bug/1940950 - ovn related, 14:34:23 <ralonsoh> I think last was is addressed, at least I remember talking to Terry 14:34:30 <ralonsoh> and I think this is not an issue 14:34:37 <slaweq> ralonsoh: ok, that's good, thx 14:35:06 <slaweq> I may try to check the first one but I don't know if I will have time really 14:35:25 <slaweq> so if there is anyone else who would like to check it, feel free to assign it to Yourself 14:36:42 <slaweq> ok, let's move on 14:36:48 <slaweq> this week our bug deputy is haleyb 14:36:54 <slaweq> and next week will be lajoskatona 14:37:00 <slaweq> lajoskatona: ok for You? 14:37:50 <bcafarel> feel free to create as many bugs as possible for our new PTL :) 14:38:03 <slaweq> bcafarel: LOL 14:39:00 <lajoskatona> YOu can postpone them 14:39:19 <lajoskatona> sure it's in my calendar 14:39:24 <slaweq> thx lajoskatona 14:39:33 <slaweq> let's move on to the last topic for today 14:39:38 <slaweq> #topic On Demand Agenda 14:39:44 <slaweq> ganso: You added topic there 14:39:50 <opendevreview> Przemyslaw Szczerbik proposed openstack/neutron master: Add port-resource-request-groups extension https://review.opendev.org/c/openstack/neutron/+/805637 14:40:06 <ganso> slaweq: yes 14:40:08 <ganso> thanks 14:40:15 <ganso> so, you partially answered my question previously 14:40:34 <ganso> now I have the impression that horizon will not be changing from using the python-neutronclient library 14:41:05 <ganso> as there may not be a reason to 14:41:57 <ganso> but just something I'd like to point out is that when implementing the change that I linked, I had previously implemented the --limit and --marker params in OSC as a test, and noticed it worked very differently than the python-neutronclient, not because of the CLI, but because of how the lib works 14:43:30 <ganso> so if horizon was to transition to use the osclib (or sdk, or something equivalent, I don't remember exactly what it uses), the logic of that patch would be slightly different, and I think the logic of some other pages would be impacted as well 14:43:54 <ganso> so my concern is whether this is in the roadmap or not, if it makes sense to ask this question here instead of the horizon team 14:45:24 <ganso> that's all I had to ask ^ 14:46:02 <opendevreview> Elvira García Ruiz proposed openstack/neutron master: [OVN] Change ControllerAgent type dinamically https://review.opendev.org/c/openstack/neutron/+/800278 14:46:14 <slaweq> You should ask about it horizon team 14:46:39 <slaweq> here maybe only amotoki would be able to give You some answer really 14:46:46 <ganso> slaweq: thanks 14:47:15 <lajoskatona> Neutron team can answer the part that ask if we will totally move everything (included python bindings) from python-neutronclient to some osc/sdk repo 14:47:16 <ganso> yea amotoki is not here today, will try to talk to him later when he is online 14:47:55 <ganso> lajoskatona: that's a good thing to know, is that planned? 14:49:23 <lajoskatona> The move of bindings is not a topic now, as we discussed previously 14:49:48 <ganso> ok, thanks! 14:50:04 <ganso> that's all I had 14:50:40 <slaweq> thx ganso and lajoskatona 14:51:00 <slaweq> if there are no other topic, I think I can give You few minutes back today 14:51:21 <slaweq> thx for attending the meeting and see You online 14:51:31 <bcafarel> o/ 14:51:32 <slaweq> #endmeeting