21:00:37 #startmeeting networking 21:00:38 Meeting started Mon Sep 19 21:00:37 2016 UTC and is due to finish in 60 minutes. The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:42 The meeting name has been set to 'networking' 21:00:44 o/ 21:00:44 hi 21:00:49 o/ 21:01:03 hi 21:02:00 I suppose everyone is heads down testing RC1 21:02:01 is that right? 21:02:26 pretty much 21:02:28 it's monday, i'm just waiting for the fog in my head to clear. 21:02:39 it clears? 21:03:08 dougwig: if it’s any help I can keep the meeting short 21:03:20 I have only a couple of recommendations/announcements to make anyway 21:04:22 wow, the fog must be pretty tick 21:04:32 *thick 21:04:34 it is. 21:04:41 :) 21:04:44 :) 21:05:12 It's not fog, your head is just in The Cloud. 21:05:46 sigh 21:05:55 ok let’s dive in 21:06:56 njohnston: thanks for saving the embarassement 21:07:09 I was saying… 21:07:13 RC1 has been cut last week 21:07:51 we have roughly another week-ish to shake any outstanding bug between now and when we must call Newton done done 21:08:24 i'm curious if we have any limitations on merging at this point in the newton cycle? and are we freezing project-config changes, or is the gate crush far enough past? 21:08:28 so even though Ocata master is open, we should still be careful at what we merge between now and then 21:08:48 to make sure we don’t make cherry picks to stable/newton awkward 21:08:57 dougwig: excellent question 21:09:23 so as as far as neutron and neutron-related repos are concerned 21:09:51 there’s no strict limitation in force, though as I said earlier, we should make sure we don’t go down the path of big refactoring right now 21:09:58 dougwig: the gate crush seems past looking at today's activity 21:09:59 at least for the next few days 21:10:06 as for project-config changes 21:10:14 I’d say, low risk changes can be looked at 21:10:15 ok, so no 3000 line neutron-lib mass edits, or similar that would hurt backports. 21:10:27 as for others that may affect stable branches or may have wider impact 21:10:28 not the time to make huge design directions in testing though, but project config cleanups are fine 21:10:39 we should probably want to exercise a higher level of scrutiny 21:10:49 for p-c, perhaps unfreezing things that don't affect the integrated gate? 21:11:08 dougwig: yes 21:11:25 hello. 21:11:29 dougwig: to give you an instance, we probably won’t make fullstack voting this week 21:11:47 even though we may want to consider this soon enough 21:12:00 so 21:12:17 going back to what we should focus right now is the following: 21:12:19 testing 21:12:20 testing 21:12:22 and testing 21:12:24 oh 21:12:25 I forgot 21:12:27 documentation 21:12:29 and testing 21:12:29 hey! 21:12:31 heh 21:12:48 and by testing I don’t mean just poke the bears 21:12:58 but added more coverage to things you’re not happy with 21:13:18 HenryG for instance is doing that for the keystone v3 work 21:13:23 kevinbenton is doing for trunk 21:13:23 etc 21:13:45 the more test cases we add more holes will pop up that need filling 21:13:57 officially we’re gonna need an RC2 21:13:58 https://launchpad.net/neutron/+milestone/newton-rc2 21:14:16 if you find a bug, report it, tag it newton-rc-potential and we’ll vet it for inclusion 21:14:31 please review/give priority to patches that address RC issues 21:14:40 test-only patches are ok 21:14:51 but they should be address a real issue 21:15:17 TrivialFixes at this point are only clogging the gate unless they affect rst files 21:15:20 Should we add newton-rc-potential for bugs in projects handled by neutron release process, like *-aas? 21:15:30 njohnston: yes 21:15:34 good 21:15:48 njohnston: like I did here https://bugs.launchpad.net/bugs/1624496 21:15:50 Launchpad bug 1624496 in neutron "_create_or_update_agent used by neutron-dynamic-routing" [Critical,Fix released] - Assigned to Armando Migliaccio (armando-migliaccio) 21:15:51 for dynamic-routing 21:16:31 another thing to keep an eye on is: https://review.openstack.org/#/c/360207/ 21:16:33 #link v 21:16:36 #undo 21:16:37 Removing item from minutes: 21:16:39 #link https://review.openstack.org/#/c/360207/ 21:16:50 I’ll keep it current until we release officially 21:16:58 please keep me honest 21:17:33 please go over 21:17:34 #link https://bugs.launchpad.net/neutron/+bugs?field.tag=doc 21:17:43 and see if there’s anything you can contribute to plug a documentation hole 21:18:05 and make yourself familiar with 21:18:08 #link http://docs.openstack.org/developer/neutron/policies/release-checklist.html 21:18:29 to see what tasks are involved during this time of the year 21:19:05 re document, some of networking-guide bugs might be related too. 21:19:09 https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=networking-guide 21:19:24 there's plenty of holes in the networking guide 21:19:45 i'm *still* trying to get the scenario rearchitecture done. turns out teaching and words are hard. :/ 21:21:14 Sam-I-Am: is there anything specific we can do to help? 21:21:40 for the rearch, reviewing the complete content would be nice (its a large wip now) 21:21:55 for example, getting someone familiar with l3ha to validate the l3ha content 21:21:58 same with dvr 21:22:14 #link https://review.openstack.org/#/c/367691/ 21:23:16 ok, I’ll get amuller on this 21:23:38 sc68cal: are you on it for the rebase? 21:24:05 sean is helping a bit with content review 21:24:13 i'll need to rebase it due to some minor patches that merged 21:24:20 Sam-I-Am: sorry I misread the patch 21:24:25 Sam-I-Am: ack 21:24:27 ++ 21:25:13 I added amuller and carl_baldwin on that patch, hopefully they’ll turn around 21:25:22 cool, thats helpful 21:25:22 armax: ack 21:25:37 * carl_baldwin will look 21:25:41 Sam-I-Am: is there a specific cut off date by which doc changes are no longer accepted for Newton? 21:25:49 Sam-I-Am: I guess it’s the same for other projects 21:25:52 right? 21:26:14 usually we dont cut stable/newton until a couple weeks after release so bug fixes dont have to be backported 21:26:21 ok 21:26:25 so probably a week before barcelona we'll cut 21:26:30 nice 21:26:46 ok, we’ll do our best to add/revise as much content as we can 21:27:36 cool. i really like all the other contributions lately too. 21:27:37 Sam-I-Am: i will look as well, sorry, just got here 21:27:41 nice to see docs with features 21:27:45 and i dont have to prod :) 21:27:58 haleyb: all the new scenarios include v6 by default 21:28:06 none of this second class citizen stuff anymore 21:28:09 :-) 21:29:24 ok, is there any question so far? 21:32:07 ok 21:32:19 looks like you guys have this under control 21:33:00 folks, even. 21:33:41 "control" 21:33:46 its relative 21:34:21 ok if there’s nothing else, it looks like we’re covered for this week 21:34:25 our focus should be RC2 21:34:33 we have a few bugs to squash 21:34:41 and patches to push through 21:35:16 if there’s nothing else let’s get some of the time back to do just that! 21:36:29 one thing 21:37:00 do we need to encourage neutron stadium project wiht release independent to release neutron releases? 21:37:02 amotoki: go ahead 21:37:14 like octavia, l2gw, sfc and so on. 21:37:25 amotoki: it looks like you just did :) 21:37:47 if they need encouragement, shouldn't they be on a different release cycle, then? 21:38:07 according to the schedule https://releases.openstack.org/newton/schedule.html 21:38:24 Oct 17-21 R+2 is the suggested deadline. 21:38:40 See "Newton cycle-trailing Deadline" 21:38:45 amotoki: I’ll send an email reminder 21:38:59 thanks 21:39:12 amotoki: thank you 21:40:00 ok 21:40:09 thanks for your undevoted attention folks 21:40:24 we’ll continue our chat on our usual media 21:40:26 #endmeeting