14:00:29 #startmeeting networking 14:00:29 Meeting started Tue Sep 27 14:00:29 2016 UTC and is due to finish in 60 minutes. The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:33 The meeting name has been set to 'networking' 14:00:34 o/ 14:00:37 o/ 14:00:38 howdy 14:00:48 o/ 14:00:49 hello :) 14:00:49 hola 14:00:52 hi 14:00:53 o/ 14:00:54 o/ 14:00:54 hi 14:00:55 hello 14:00:55 o/ 14:00:57 o/ 14:00:57 o/ 14:00:59 hi 14:01:26 o/ 14:01:26 #link https://wiki.openstack.org/wiki/Network/Meetings Agenda 14:01:45 * ihrachys notes the agenda is not really in shape for the meeting, so he will improvise a bit 14:01:50 #topic Announcements 14:02:25 first, in case someone lives deep under a rock, I remind that armax is our PTL for Ocata 14:02:56 hi 14:02:56 summit planning has already started 14:03:14 moo. 14:03:23 I don't believe we had a discussion for neutron related setup for the summit yet, I bet armax will update us in next weeks. 14:03:36 but for cross project sessions, we are already collecting topics 14:03:40 #link https://etherpad.openstack.org/p/ocata-cross-project-sessions 14:03:58 make sure you walk thru the list and propose ideas for cross project sessions 14:04:11 I believe it's ~one week until the list is closed, so don't drag 14:04:29 o/ 14:04:56 as you noticed, master is open for Ocata for some time, and we land Ocata only patches already. 14:05:05 we still have *not* released Newton final 14:05:13 so far we released RC1 only 14:05:26 and we are looking to release RC2 in next day or two 14:05:38 after that, there is quiet period till Oct 6: http://lists.openstack.org/pipermail/openstack-dev/2016-September/104373.html 14:05:55 on that day, the last RC we release will be considered final and will officially ship to consumers 14:06:55 since Ocata cycle is open, I wanted to share with folks that I want to step down from being a release liaison for Ocata 14:07:12 people who feel like taking over the torch are highly welcome to step up 14:07:13 late o/ 14:07:55 ihrachys: thanks you very much as release liaison so far 14:07:59 if you don't step up, you effectively make your PTL a release liaison, and he will be sad about it 14:08:00 ihrachys: thanks for all your hard work as release liaison! 14:08:13 don't make your ptl sad 14:08:18 thanks folks, I appreciate 14:08:58 talk to me or armax if you feel you can help with the role 14:09:23 ihrachys: if you can provide more information about the role of release liaison, it will be helpful for folks who are thinking to serve as release liaison. 14:09:42 thank you ihrachys! 14:09:58 amotoki_: ++ 14:10:13 I think for the most part it's covered in https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management 14:10:15 amotoki_: ++ 14:10:20 amotoki_: ++ 14:10:21 and http://docs.openstack.org/project-team-guide/release-management.html 14:10:30 there is more info to that, but that should give the idea 14:10:34 amotoki_:++ 14:10:53 ihrachys: thanks. that would be enough for most cases. 14:10:57 basically, it's about creating release requests for the whole stadium, plus helping armax to track release critical fixes 14:11:48 while at it, I want to mention that I hold the oslo liaison role for several cycles already, and would be happy if someone takes that one over too, if anything, for the sake of rotation in the team. 14:12:23 that one involves in tracking 'oslo' tag in launchpad, plus attending a single oslo meeting per week :) 14:12:25 again, talk to me for details 14:12:27 do you want to be the docs liaison too? :) 14:12:34 ihrachys with the chances in the stadium, how many projects do you track for release? 14:13:04 Sam-I-Am: even with those off my shoulders, I still have stable liaison thing! 14:13:14 docs is moar fun! 14:13:31 johnsom: everything under https://github.com/openstack/governance/blob/master/reference/projects.yaml#L2810 14:13:45 though it doesn't take too much time now because the process is more streamlined lately 14:13:57 Still quite a number then. 14:14:25 Yes, the release team has done a great job at making it a smooth process 14:14:29 johnsom: yeah. I believe the list may shrink though. I hope it does. :) 14:14:51 I know one that will be coming off the list... Grin 14:15:09 I hope more will :) some for better some for worse 14:15:11 anyhoo 14:15:33 let's walk thru Newton release matters for a sec 14:15:35 #topic Closing Newton release 14:15:58 the RC2 request is up but it will need a respin after I clarify with armax the final bits to include into it: https://review.openstack.org/#/c/376998/ 14:16:23 fyi the dashboard to track the final bits is the same as before, https://launchpad.net/neutron/+milestone/newton-rc2 14:17:10 note that as per email from Armando you must not target any new bugs for the milestone without talking to him (or me): http://lists.openstack.org/pipermail/openstack-dev/2016-September/104547.html 14:17:34 if you feel like, just tag a critical bug with newton-rc-potential (and still talk to us) 14:18:01 reminder: postmortem is still up for comments, fill your PTL in with latest state if not already: https://review.openstack.org/#/c/360207/ 14:18:30 before we cut off RC2 that will probably be final, walk thru release notes for the release: 14:18:35 #link http://docs.openstack.org/releasenotes/neutron/newton.html 14:18:35 #link http://docs.openstack.org/releasenotes/neutron-dynamic-routing/newton.html 14:18:35 #link http://docs.openstack.org/releasenotes/neutron-fwaas/newton.html 14:18:35 #link http://docs.openstack.org/releasenotes/neutron-lbaas/newton.html 14:18:35 #link http://docs.openstack.org/releasenotes/neutron-vpnaas/newton.html 14:18:55 if you see an issue there, you still have time to propose a fix today. don't loose the chance. 14:19:44 btw njohnston, I haven't seen octavia release notes at https://releases.openstack.org/newton/ is it expected? is it because the project is release:independent? 14:20:24 I will check that out! 14:20:33 ok 14:20:45 njohnston: neutron-lbaas-dashboard too 14:20:54 the release brings me to the next topic which is… 14:20:57 #topic Docs 14:21:05 we have quite some doc bugs opened 14:21:05 #link https://bugs.launchpad.net/neutron/+bugs?field.tag=doc Doc bugs 14:21:22 ideally we would not have the list that huge at this point into release 14:21:37 please take a bug or two from the list and help with closing them 14:21:46 we want our docs in shape before the release amirite? 14:22:15 Sam-I-Am: since you are here, do you have any specific updates from the docs team? 14:22:36 ihrachys: not too much 14:22:43 i'm still working on updating all the deployment scenarios 14:22:47 its a lot of work, but moving along. 14:23:00 regarding docs, I send LBaaS v1 drop patch to the networking guide https://review.openstack.org/#/c/377229/ 14:23:03 i hope to get it merged in time for when the docs cut newton, plus a backport to mitaka 14:23:11 its also nice to see all the contributions from neutron folks 14:23:24 I would like to know how we can do database data migration from v1 to v2. 14:23:49 also, please tag me in any docs patches so i can help move them along 14:23:53 There is a script in the tools directory that can assist with v1 to v2 DB migrations 14:23:56 amotoki_: I think there was a conversion script, though not really tested. 14:24:03 +1 14:24:22 at this point I don't believe it would belong to official docs 14:24:31 johnsom: yeah, I see the script in neutron-lbaas repo, but I wonder how operators can use it. 14:24:41 regarding https://review.openstack.org/#/c/376976/ : I was asked to use project_id instead of tenant_id, but this would not be consistent with the rest of the documentation. Any insight? 14:24:54 Sam-I-Am: you could just track the link with all 'doc' tagged bugs for neutron to keep an eye on our backlog. wouldn't it work? 14:25:32 alraddarla_: sorry for late review on API reference. I will look at it soon. 14:25:41 ihrachys: i could do that, assuming they're all tagged :) 14:26:02 alraddarla_: at the moment, we use tenant_id now and would like to add project_id in a followup patch. 14:26:03 alraddarla_: I don't think the suggestion is correct: metering extension does NOT provide the project_id attribute, project_id extension does. The base metering extension supports just tenant_id 14:26:26 Sam-I-Am: I think they are, at least those created by the virtue of DocImpact 14:27:25 amotoki_ ihrachys : thank you! Just needs reviewed I believe then 14:27:34 Sam-I-Am: even if not all of them are, the list itself is quite long to keep us busy for some time :) 14:28:00 #topic Gate status 14:28:13 just wanted folks to be aware of the state of the gate 14:28:16 #link http://grafana.openstack.org/dashboard/db/neutron-failure-rate Grafana 14:28:29 one board that stands out is the one for unit tests in gate queue 14:28:35 #link http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=3&fullscreen Unit tests gate trend 14:29:02 it shows that our unit tests are ~25% failing rate in gate (?) 14:29:22 Yeah that should be 0 14:29:23 but I suspect it's the infra issue of a breakage of zuul-cloner 14:29:34 we had one yesterday I believe 14:29:48 so I hope it will get back to normal after a while 14:31:11 though the last time I reloaded it, I saw the raising trend which made me feel uneasy. if that would be a solved issue, wouldn't it go down? 14:31:24 (for some reason, it does not reload for me quick enough right now) 14:31:44 Too many people looking 14:31:59 oh it actually started to go down 14:32:30 it was 70% last night 14:32:36 ok then we are good :) 14:32:44 other dashboards are more or less in shape 14:33:06 note we track gate failures in launchpad 14:33:08 #link https://bugs.launchpad.net/neutron/+bugs?field.tag=gate-failure Known gate bugs 14:33:27 if your patch failed in gate, please DON'T recheck blindly 14:33:57 instead, look thru the logs, then the bug tracker and report a new bug with gate-failure tag if there is no existing bug for the failure you see 14:34:05 (and help driving it to a fix) 14:34:25 every time you recheck with no bug, a kitten dies somewhere 14:34:40 #topic Planning for Ocata 14:35:10 as I said before, there are still no specific directions from armax on summit planning 14:35:19 anyhow, neutron-drivers revived their meetings and will slowly process the backlog of RFEs 14:35:24 recheck with no bugs should be negative karma in stackalytics.... 14:35:39 also, if you own a spec, please repropose it for ocata (there is a directory for that in the tree) 14:35:47 ajo: haha, good idea 14:35:59 :-) 14:36:39 well the dying of kittens is bad enough 14:37:07 I see quite some blueprint specific topics in the agenda wiki page like for neutron-lib or OSC. I am not sure those should survive now that we are in Ocata mode. I will leave it up to armax to reformat the page for the new times. 14:37:47 I will take the liberty and skip those. if anything, blame me. 14:37:51 #topic On Demand Agenda 14:38:02 there are no new topics in the list on wiki for what I see 14:38:21 so unless someone raises a topic of interest to majority of the team now, I will call it a day. 14:38:33 and return you back your precious 20+ mins of life 14:39:29 oki-doki, the silence says it all. go get some coffee or whiskey depending on your timezone. 14:39:38 ciao 14:39:39 #endmeeting