14:00:08 #startmeeting networking 14:00:09 Meeting started Tue Aug 11 14:00:08 2020 UTC and is due to finish in 60 minutes. The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:11 hi 14:00:13 The meeting name has been set to 'networking' 14:00:16 o/ 14:00:17 o/ 14:00:18 Hi 14:00:19 o/ 14:01:31 o/ 14:01:39 lets start 14:01:41 #topic Announcements 14:02:03 Release calendar https://releases.openstack.org/victoria/schedule.html reminders: 14:02:22 Our next milestone is Victoria-3 in the week of 7th September 14:02:45 but there is also proposal for release calendar for Wallaby cycle: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016391.html 14:03:11 Virtual PTG will be in the week of 26th of October: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016424.html 14:03:46 and that's short announcements from my today 14:03:56 anything else You want to share with the team maybe? 14:05:12 if not, lets move on to the next topic 14:05:14 #topic Blueprints 14:05:23 Blueprints for Victoria-3: https://launchpad.net/neutron/+milestone/victoria-3 14:05:35 do You have any updates about any of them? 14:05:56 https://blueprints.launchpad.net/neutron/+spec/replace-qos-of-bound-port 14:06:36 I discussed lst wee kwith ralonsoh, and we agreed to try with placement allocation update before db transaction, and today basically it worked 14:07:27 so that can be an option, the other one is to do it after db transaction, and in that case port update will be async, as placement update is time consuming 14:07:50 I tried to summarize these on bug page, when ralonsoh will be back we can discuss I suppose how to proceed 14:08:24 in the second solution You will need to rollback db changes if something will go wrong in placement? 14:09:35 no then the update will fail before db change 14:10:04 lajoskatona: ?? 14:10:06 you mean when placement update happens after db transaction? than we need rollback, sorry 14:10:12 yes 14:10:14 ok 14:10:50 so then we may have "weird" situation when user is doing port update to change QoS policy and it gets result which confirms him that policy is changed 14:11:15 but then placement fails to allocate new resources and qos policy is rollback to the old one 14:11:17 is that correct? 14:12:03 yes 14:12:26 or another extra should be to add some status for the update and user can poll that 14:12:41 and that can show if everythin (placement i.e.) succeeded 14:12:48 I'm not sure if that's good idea but we can discuss that with ralonsoh next week 14:13:04 slaweq: ok 14:13:32 next week I will be on PTO, but after that we can discuss if everybody have time 14:13:38 lajoskatona: ok 14:13:45 lajoskatona: thx for the update on this 14:14:01 slaweq: thanks for the time for it :-) 14:14:13 any other updates about BPs? 14:16:17 ok, so I have short update about some of them 14:16:27 first https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant 14:16:52 neutron and neutron-tempest-plugins: https://review.opendev.org/#/c/686343/ and https://review.opendev.org/#/c/733994/ are ready for review 14:17:04 and when it will be done, this RFE will be completed 14:17:14 please add it to Your review pile :) 14:17:32 and also similar with George framework: https://bugs.launchpad.net/neutron/+bug/1863113 14:17:33 Launchpad bug 1863113 in neutron "[RFE] Introduce new testing framework for Neutron - OVN integration - a.k.a George" [Wishlist,New] - Assigned to Jakub Libosvar (libosvar) 14:17:39 patches https://review.opendev.org/#/q/topic:george+(status:open+OR+status:merged) - all ready for review now 14:17:50 that's at least what jlibosva told me today :) 14:18:23 some have -1 from gerrit 14:18:32 for other BPs I'm trying to keep links to the opened patches in https://wiki.openstack.org/wiki/Network/Meetings#Blueprints so please take a look and review them if You will have some time 14:19:05 mlavalle: but I think that errors are unrelated 14:19:14 ack 14:19:43 I know that there is now (again) some issue with grenade jobs but I haven't got time to check it yet 14:20:25 ahh, and one more thing 14:20:45 are those grenade jobs not zuulv3 yet? 14:21:26 please also check ovn-devstack patches from lucasgomes: https://review.opendev.org/#/q/topic:ovn-devstack+(status:open+OR+status:merged) 14:21:33 we should move on with that 14:21:43 tosky: neutron grenade jobs are zuulv3 already, why? 14:21:52 slaweq: yes, they are 14:22:59 ok, speaking about zuulv3 migration 14:23:02 #topic Community Goals 14:23:16 any updates on community goals from You? 14:23:36 I didn't had time to work on zuulv3 nor Ubuntu 20.04 this week 14:23:41 I ported a job: https://review.opendev.org/#/c/745522/ 14:23:58 not sure it should live in that repository, but the point of the migration is just to convert it 14:24:24 apart from that, there are some WIP reviews that may need some love and help 14:24:38 reminder about the status, see from line 175 https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration 14:25:20 thx tosky 14:25:28 I will try to review them ASAP 14:27:08 ok, so I think we can move on with the next topics now, right? 14:27:48 I don't have anything else on this topic for now 14:28:11 #topic Bugs 14:28:18 mlavalle was our bug deputy last week 14:28:29 mlavalle: any bugs You want to highlight now? 14:28:45 yeah... 14:29:09 https://bugs.launchpad.net/neutron/+bug/1890445 needs owner 14:29:10 Launchpad bug 1890445 in neutron "[ovn] Tempest test test_update_router_admin_state failing very often" [Critical,Confirmed] 14:29:43 that's it 14:29:45 I asked jlibosva today if he can take a look at it 14:30:52 thx mlavalle 14:31:05 it seems from Your report that it was pretty quiet week 14:32:06 this week our bug deputy is rubasov and he's already aware of it 14:32:14 ack 14:32:28 next week will be ralonsoh and I will make sure that he will not forget :P 14:33:37 any other bugs anyone wants to discuss today? 14:35:18 ok, if not I think we can move on 14:35:28 I have one more item for today 14:35:33 #topic On demand agenda 14:35:46 User survey question 14:36:10 I recently got email from Kendall about this years user survey and if we want to change something in neutron related question 14:36:27 I should send proposal of changes this week 14:36:35 I already started looking at it 14:37:15 but I wanted to ask You if You want me to send it to the ML that we can discuss it together or do You want me to update possible options in the question? 14:38:30 what are our current questions? 14:38:44 njohnston: there is one which I got: 14:39:28 "Which of the following features in the Neutron project are you actively using, interested in using or looking forward to useing in your OpenStack deployment?" 14:39:57 and there is about 21 possible options to choose 14:40:24 ah yes, now I am rememberig 14:41:44 I think the list of options is pretty stable 14:41:56 yes, but I have couple of types to add there 14:42:12 like e.g. SR-IOV, Trunk ports or port forwarding 14:42:20 which are not there 14:42:54 +1 14:43:02 and for some of the answers I'm really not sure what they means exactly 14:43:18 like e.g.: "traffic steering" - is that networking-sfc? 14:43:24 or something different? 14:44:21 mlavalle: njohnston maybe You would know :) 14:44:43 when I think of "traffic steering" I think of something like lbaas 14:44:52 yeah 14:45:08 for lbaas is another option: "software load balancing" 14:45:30 then it probably refers to policy based routing, which is under the SFC umbrella 14:45:52 maybe remove any lbaas? there is this octavia project :) 14:46:03 njohnston: thx for clarification 14:46:13 haleyb: yes, that's another thing which I was thinking of 14:47:38 haleyb: I will propose to remove this option from the list :) 14:47:53 thanks! 14:48:21 there is also option "Port mirroring/monitoring" there 14:48:28 do we have something like that in Neutron? 14:48:46 tap-as-a-service? 14:48:48 we had TaaS project but is it related to it? 14:48:55 but that is in x/ namespace now 14:49:01 lajoskatona: exactly 14:49:11 that's why I'm not sure about it 14:49:25 tap as a service was all about port mirroring 14:49:53 and for sure it is used 14:50:02 ok, so lets keep it there 14:50:11 but far from being mature enough 14:50:20 it may be some argument to include it (or not) in stadium at some point if that will be requested :) 14:50:20 AFAIK TaaS is the only way to achieve real port mirroring 14:50:43 (in tenant networks) 14:51:15 so that were all doubts which I had 14:51:22 thx for help with it 14:51:42 and that's all from me for today 14:51:50 anything else You want to talk about? 14:53:38 ok, so I will give you few minutes back today 14:53:43 thx for attending the meeting 14:53:46 see You online 14:53:48 o/ 14:53:50 o/ 14:53:51 #endmeeting