14:00:05 #startmeeting networking 14:00:05 Meeting started Tue Aug 28 14:00:05 2018 UTC and is due to finish in 60 minutes. The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:08 The meeting name has been set to 'networking' 14:00:12 hi mlavalle 14:00:33 o/ 14:00:37 o/ 14:00:59 hi 14:01:08 hi 14:01:35 Hi Team, nice to see you all! 14:01:35 hi 14:02:03 Let's get going 14:02:13 #topic Announcements 14:02:42 This week the community releases OpenStack Rocky 14:02:55 o/ 14:02:59 Thanks you very much to all of you for your hard work 14:03:10 we made it to the end of another cycle 14:03:23 \o/ 14:04:17 congrats to the rocky contributors, now on to stein :) 14:04:19 The Stein PTG starts in a little less than two weeks in Denver. I am looking forward to see you many of you there \o/ 14:04:28 ++ 14:04:56 Remember that the etherpad is here: 14:05:04 #link https://etherpad.openstack.org/p/neutron-stein-ptg 14:05:53 Yesterday I had a quick conversation with melwitt and it seems we don't have Nova / Neutron cross projects topics to discuss this time around.... 14:06:16 rubasov: do we need to discuss anything with the Nova team regarding bandwidth based scheduling? 14:06:22 o/ 14:06:39 mlavalle: I'm not aware of anything 14:07:02 rubasov: that's cool. I don't want to force it. Just in case we had something pending 14:07:40 in any case, if the team thinks of anything we should discuss with Nova, please add it to the etherpad 14:07:56 mlavalle: gibi thinks the same, so I'm quite sure 14:08:07 rubasov: cool, then 14:08:22 * haleyb was lost in the ether somewhere or there was a netsplit 14:08:55 haleyb: looks like you found your way back in the end 14:09:29 Like last year, we are going to have our team dinner on Thursday 13th. I was thinking going to the same place we went last year: https://www.famousdaves.com/Denver-Stapleton 14:09:51 The food was good, very affordable and within walking distance of the hotel 14:09:59 what do folks think? 14:10:05 +1 first time for me in denver 14:10:29 +1 14:10:30 Sure, all the Famous Dave's restaurants around me closed about a year ago. Good BBQ. 14:10:59 I missed the first Denver train, so +1 (especially if good BBQ) 14:11:02 I never had any Famous Dave's restaurant around me so it's good for me :D 14:11:19 +1 from me, the food at the local brewery was only hit or miss at best 14:11:51 ok, cool. Please go to the etherpad and add a yes (or no) to the line where your name is to indicate whether you are attending the dinner 14:12:00 I will sned a message to the ML anyways 14:12:55 any other announcements from the team? 14:13:25 ok, let's move on.... 14:13:31 #topic Blueprints 14:14:32 I have rolled over the blueprints of Rocky into the Stein-1 dashboard: https://launchpad.net/neutron/+milestone/stein-1 14:15:10 and added some of the stuff that we have approved recently in the drivers meetings 14:16:08 njohnston: please note the addition to https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch 14:16:26 Yes, I was just reading that 14:16:36 so we can carry out the consolodation of this effort with https://blueprints.launchpad.net/neutron/+spec/adopt-oslo-versioned-objects-for-db 14:16:54 +1 14:17:01 this way the topic has visibility every week 14:17:38 I also added https://blueprints.launchpad.net/neutron/+spec/port-mirroring-sriov-vf 14:17:55 This is still in discussion, with a spec under review 14:18:16 #link https://review.openstack.org/#/c/574477/ 14:18:37 muninsh will be at the PTG, so it will be a topic of discussion there 14:18:54 I invite the team to read the spec and get familiar with the topic 14:19:50 I would like to also note https://blueprints.launchpad.net/neutron/+spec/speed-up-neutron-bulk-creation which is also a discussion topic at the PTG, I hope we can add this as well 14:20:19 * mlavalle will get back to bulk creation in a bit 14:20:32 Thanks, sorry to jump the line mlavalle :-) 14:21:24 munish needs help getting in shape the CI system of one of the networking sub-projects (I think it is tap as a service but not sure) 14:21:38 slaweq: maybe we give him some guidance 14:22:21 mlavalle: I can help, sure 14:22:32 cool thanks 14:23:09 njohnston: yeeeees.... On Firday, when I was working on this, I knew I was forgetting something big. Yes, that has been agreed upon since Dublin 14:23:34 if more discussion is needed in Denver, that is perfectly fine 14:24:14 I just added it to the dashboard 14:24:25 thanks mlavalle! 14:24:46 thanks for bringing it up :-) 14:25:39 anything else on blueprints 14:25:51 ? 14:26:51 ok, let's move on 14:27:02 #topic Community goals 14:27:46 Last week slaweq volunteered for the "Support Pre Upgrade Checks" community goal 14:27:53 I can help with ci too count me in 14:27:54 Thanks you very much!!!! 14:28:15 but I didn't do anything with it yet :/ 14:28:32 that's is fine,..... we are still officially in Rocky 14:28:35 ;-) 14:28:41 :) 14:28:48 slaweq: maybe start by adding a PTG topic? ;) 14:28:58 or is it coverd by the general neutron upgrades one 14:29:06 bcafarel: yes, that's good idea 14:29:11 I will add it there 14:29:16 ++ 14:29:40 any updates on the Python-3 goal, njohnston? 14:30:38 Nothing at the moment on the functional job, been pulled in other directions. Did we get any guidance on the tempest jobs from the TC? I don't recall if we had resolved that. 14:31:11 yeah, essentially the guidance is "let's convert everything to Python 3" 14:31:15 all the jobs 14:31:40 so py2 jobs will be dropped at some point ? 14:31:50 we should only have python 2.7 jobs for exeplicitely testing python 2.7 14:32:15 njohnston: does that help? 14:32:23 I think py2 will be dropped at some point, but as I understand that'll be mostly dependant on when the linux distros drop support 14:32:27 ok, so the option is that we can have a py27 and a py3 version of all the tempest jobs, or we can have either a py27 or a py3 version of each job and we transition from one to the other 14:33:04 or cut a list of "important" jobs to have both (ie make sure that py27 still works) 14:33:06 it sounds like they are OK with doubling the number of tempest jobs, so as long as that 14:33:13 guess pep8 etc only need py3 14:33:25 njohnston: no.... everything should be python 3, except where we are testing for python 2.7 explicitely 14:33:27 as long as that's not a zuulbreaker then I am good to get started on it 14:33:35 some of jobs, like scenario or others are not very stable and if we will run them all for both py27 and py3 I'm affraid we will be lost with rechecking :/ 14:33:47 and it will also consume a lot of infra resources 14:34:06 so which tempest jobs are important to keep in py27? Just one py27 full run, or do we need the scenario tests too? 14:34:33 I'd say have one py27 run 14:35:00 let's do only one 14:35:06 slaweq: do you think we should add a neutron specific CI topic at ptg? (to get a better passing rate) 14:35:28 and... we also can add a py3 topic 14:35:32 and maybe the py27 unit tests 14:35:42 o/ 14:36:06 ok, I can start with bifurcating the tempest-full into py3 and py27 jobs, and then I'll work on converting all the others to py3, one at a time 14:36:09 bcafarel: I think we can discuss on PTG about that what jobs should be run in both py27 and py3 and which only on py3 14:37:23 the general idea is that we need a minimum of py27, just to make sure we support it 14:37:31 but everything else should be py3 14:37:33 actually never mind, the bifurcation is already done and tempest-full-py3 already exists. so I'll get changes up for review to switch to py3 for the other jobs, but I'll -W them until after we discuss it at the PTG 14:37:57 njohnston: that is a good approach 14:38:31 njohnston: would you add the topic to the etherpad? 14:38:37 will do 14:38:55 njohnston: started it (point 14), feel free to expand 14:38:56 hi, I had trouble in connecting irc and reading the log today 14:38:57 ok 14:39:27 ok, let's move on 14:39:32 #topic Bugs 14:40:25 hongbin sent a comprehensive report here: http://lists.openstack.org/pipermail/openstack-dev/2018-August/133886.html 14:40:31 hi 14:40:53 yes, there are many reported bugs last week 14:41:14 one of them is critical, two of them are high 14:41:28 The critical bug was alfeady fixed by slaweq, correct? 14:41:52 mlavalle: it is assigned to you 14:42:08 hongbin: yeah, but he took it off my hands ;-) 14:42:17 #link https://bugs.launchpad.net/neutron/+bug/1788185 14:42:17 Launchpad bug 1788185 in neutron "[Stable/Queens] Functional tests neutron.tests.functional.agent.l3.test_ha_router failing 100% times " [Critical,Confirmed] - Assigned to Miguel Lavalle (minsel) 14:42:21 mlavalle: ok 14:42:26 mlavalle: but it was agreed with You :P 14:42:37 mlavalle: if it is already fixed, please mark the bug as fixed 14:42:40 yeah, you did, slaweq, LOL 14:42:52 hongbin: will do 14:42:56 mlavalle: thanks 14:42:59 not sure we got all the backports merged yet? 14:43:01 hongbin: I will mark as fixed when patches will land 14:43:07 now they are in the gate still 14:43:16 slaweq: ack 14:43:26 one the ofhigh priuorities: https://bugs.launchpad.net/neutron/+bug/1788006.... 14:43:26 Launchpad bug 1788006 in neutron "neutron_tempest_plugin DNS integration tests fail with "Server [UUID] failed to reach ACTIVE status and task state "None" within the required time ([INTEGER] s). Current status: BUILD. Current task state: spawning."" [High,Confirmed] - Assigned to Miguel Lavalle (minsel) 14:43:54 I worked on it over the weekend. It is really a NOva issue and I opened a correspondig bug on that side 14:44:18 I left comprenhensive notes in the bug 14:44:35 thanks very much for running that one down 14:45:07 +1 14:45:26 there is another one, which i traiged it as "high" 14:45:28 I see that the RFEs are properly tagged, so we will catch them in the RFE / Neutron drivers process 14:45:30 #link https://bugs.launchpad.net/neutron/+bug/1787919 14:45:30 Launchpad bug 1787919 in neutron "Upgrade router to L3 HA broke IPv6" [High,Confirmed] 14:46:53 for that one I added l3-dv-backlog tag. we will process it further on Thursday during the Le sub-team meeting 14:47:11 mlavalle: great. thanks 14:47:12 L3 subteam^^^ 14:47:15 hongbin: I added comment there also 14:47:37 it looks for me that You spotted different issue then described originally in bug report, can You check that? 14:48:11 ok, this week's deputy is hichihara. I already contacted him over email and he is working on it 14:48:16 let's move on 14:48:22 #topic neutron-lib 14:48:32 boden: any updates here? 14:48:37 hi 14:49:06 nothing exciting, just back to business as usual.. we've landed a number of neutron-lib patches and there's some consumption patches out there for review in neutron and others 14:49:24 I am keeping an eye on both 14:49:25 that's really all I have to report at this time unless there's comments/questions 14:49:41 not from me 14:49:57 ok, moving on 14:50:02 #topic Ryu 14:50:12 hongbin: you are up again.... 14:50:18 hi 14:50:32 * hongbin is checking the ryu patches 14:50:41 #link https://review.openstack.org/#/c/588358/ 14:50:58 above is the proposed patch and it looks very closed to merge 14:51:43 Great! 14:52:07 actually, checking the last comment, they said the patch was approved 14:52:23 even better 14:52:33 that's from the governance point of view 14:52:43 yes 14:52:43 you have one for the repo, right? 14:52:52 #link https://review.openstack.org/#/c/588355/ 14:53:08 this is the one to create the repo 14:53:24 and it got one +2 already 14:53:54 i think we will get that one approved soon, we are able to proceed 14:54:15 Great progress hongbin.... do you think the next step is to discuss in the PTG how to start importing from the new repo and giving maintenance to it? 14:54:21 I failed to follow this discussion, but naming ken is from the street fighter as the rival of ryu? 14:54:33 amotoki: exactly 14:54:33 mlavalle: sure, that would be a good idea 14:54:48 amotoki: ryu's best friend 14:54:56 njohnston: nice point 14:55:09 ok, let's move on 14:55:34 #topic CLI / SDK 14:55:42 amotoki: any updates here: 14:55:45 ? 14:55:53 I plan to release neutornclient next week 14:55:59 to include the gate fix 14:55:59 cool 14:56:20 it will happen in both stein and rocky branch. 14:56:51 apart from that, fwaas support in openstacksdk is proposed. 14:57:13 I will follow up and resume the SDK migration till PTG. 14:57:13 nice! 14:57:19 that's all from me this week. 14:57:24 thanks 14:57:29 #topic Open Agenda 14:57:54 Somobody pinged yesterday about a joint session Cyborg / Neutron during the PTG 14:58:02 I would like to ask for anoter round of reviews of https://review.openstack.org/#/c/594326/ 14:58:05 is that person around? 14:58:26 slaweq: I will look at it again 14:58:29 I would like to run it when it will be merged :) 14:58:32 mlavalle: thx a lot 14:59:00 ok 14:59:21 the other topic I wanted to mention is https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/graphql 14:59:58 This is a pilot to implement some of the Neutron API in GraphQL: https://graphql.org/ 15:00:13 I encourgae the team to take a look and help with reviews if you can 15:00:18 #endmeeting