21:00:23 <armax> #startmeeting networking
21:00:24 <openstack> Meeting started Mon Jul 11 21:00:23 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:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:28 <openstack> The meeting name has been set to 'networking'
21:00:29 <blogan> hello
21:00:30 <njohnston> o/
21:00:33 <mlavalle> o/
21:00:33 <HenryG> o/
21:00:36 <Sam-I-Am> yo yo yo
21:00:41 * regXboi is still listening for the intro music
21:00:43 <regXboi> \o
21:00:52 * ihrachys lurks
21:00:57 <dougwig> regXboi: you'll be waiting awhile.
21:01:07 * regXboi hands Sam-I-Am a yo-yo
21:01:41 <armax> hello to everybody
21:01:47 <mlavalle> regXboi: https://www.youtube.com/watch?v=1qP-NglUeZU
21:01:50 <armax> welcome to milestone week
21:01:58 <armax> agenda for today
21:02:05 <regXboi> mlavalle: seriously?!?!
21:02:12 <armax> #link https://wiki.openstack.org/wiki/Network/Meetings
21:02:41 <dasm> o/
21:02:43 <armax> I trust ihrachys is on top of everything, but let’s not digress
21:02:53 <armax> #topic Announcements
21:02:54 <ihrachys> WAT
21:03:09 <armax> ihrachys: you are the release emperor are you not?
21:03:19 <ihrachys> oh ok, not everything.
21:03:28 <armax> ihrachys: relax
21:03:34 <armax> ihrachys: your time will come
21:03:42 <armax> (to freak out)
21:03:46 <armax> anyhoo
21:03:48 <armax> #link https://wiki.openstack.org/wiki/Network/Meetings#Announcements_.2F_Reminders
21:04:00 <mlavalle> it is a little too late for ihrachys. He may be stressed out
21:04:10 <armax> so, a few reminders
21:04:14 <armax> …kind reminders
21:04:27 <armax> #link https://blueprints.launchpad.net/neutron/newton/+assignments
21:04:31 <armax> if you are on that list
21:04:47 <armax> please make sure you do your job
21:04:58 <armax> as approver
21:05:02 <armax> or assignee
21:05:27 <armax> which primarily involves reviewing code/specs associated with teh blueprint/RFE
21:05:41 * regXboi coninues to play a marotte carrying jester
21:05:47 <armax> and update the BP whiteboard to reflect the latest status of the feature
21:06:10 <armax> let’s make sure that by the end of N-2 we got an updated snapshot of what’s going on
21:07:03 <armax> I see that a few things are rather stale
21:09:10 <armax> for any questions, please feel free to ask
21:09:26 <armax> if you are an assignee and your approver doesn’t support you
21:09:42 <armax> please reach out and we can figure out a solution together
21:11:02 <armax> ok moving on
21:11:08 <armax> #link http://lists.openstack.org/pipermail/openstack-dev/2016-July/099046.html
21:11:21 <armax> this is a light thread you may want to be aware of
21:11:33 <armax> each project has been asked to come up with a project mascot
21:12:14 <dougwig> is the mushroom cloud taken yet?
21:12:14 <Sam-I-Am> yeah
21:12:17 <Sam-I-Am> hahahaha
21:12:19 <armax> as soon as I learn more, I’ll share it with the team so that we can find out a mascot for Neutron
21:12:20 <dougwig> or a tire on fire?
21:12:22 <johnsom> Walrus?
21:12:22 <blogan> http://www.chicagonow.com/art-talk-chicago/files/2011/06/radioactive-man-up-and-atom.png
21:12:23 <Sam-I-Am> dougwig: you and i were thinking the same thing
21:12:50 <njohnston> since a neutron has 2 down and 1 up quark, I thought about something like this: http://imgur.com/9AsnYrP
21:13:06 <regXboi> njohnston: I was going to say a three-d of that
21:13:11 <johnsom> #link http://www.openstack.org/project-mascots
21:13:13 <regXboi> with u and d and assign colors
21:13:21 <Sam-I-Am> actually, the logo should have booze somewhere
21:13:32 <armax> johnsom: it’s gotta probably an animal or animals that evoke something network-y
21:13:48 <blogan> redwood trees
21:13:52 <ihrachys> fish in a net :)
21:14:00 <johnsom> I was purely kidding...
21:14:13 <Sam-I-Am> that derailed quickly...
21:14:13 <armax> I am delighed to see people’s responses on the things that matter our release!
21:14:21 <armax> nicely done
21:14:27 <regXboi> armax: you expected otherwise?
21:14:31 * regXboi shakes head
21:14:37 <armax> regXboi: of course not
21:14:49 <njohnston> Why do something productive when we can bikeshed and yak shave AT THE SAME TIME
21:14:50 <Sam-I-Am> we bike shed really well
21:14:50 <armax> regXboi: we should probably have more of these announcements to keep the meetings lively
21:14:59 <dasm> armax: ++
21:15:11 <johnsom> I was streamlining the process by picking an animal that no one will fight us for....
21:15:20 * regXboi rotflmao
21:16:30 <armax> ok
21:16:33 <armax> let’s move on
21:16:37 <Sam-I-Am> next!
21:16:45 * Sam-I-Am waits for precious docs
21:16:47 <armax> #topic Blueprints
21:16:50 <armax> #link https://wiki.openstack.org/wiki/Network/Meetings#Blueprints
21:17:06 <regXboi> hey... bugs before docs :)
21:17:09 <armax> since we’re about to get into the last milestone of the cycle
21:17:39 <armax> please be aware that things are going to get busier than average, the gate is gonna jam more easily etc
21:19:08 <armax> remember that the last week of August is the last useful time to get in your client and lib dependencies in
21:19:38 <armax> even though we can stretch ourselves an extra couple of weeks after that as far as Neutron itself goes
21:19:52 <dougwig> though not with neutron-lib
21:20:12 <armax> dougwig: neutron-lib included
21:20:16 <armax> because that goes into g-r
21:20:28 <armax> anything that doesn’t make into neutron-lib, python-neutronclient, python-openstack-client, oslo-* is likely deferred to Ocata
21:20:32 <dougwig> as in, we can't stretch n-l.  it depends on global requirements changes and such, just like other libs.
21:20:43 <armax> unless there’s a good reason for it
21:21:23 <armax> also if your pending work has DB schema changes and API changes
21:22:15 <armax> please make sure you flag them ahead of time to your approver or the PTL, whether I happen to be both or not :)
21:23:00 <armax> any question?
21:24:07 <armax> looks like we’re square
21:24:37 <armax> let’s sse how many of us are gonna get bitten by this
21:24:44 <armax> #topic Bugs
21:25:15 <armax> #link https://wiki.openstack.org/wiki/Network/Meetings#Bugs_and_Gate_failures
21:26:19 <armax> there are a few gate failures
21:26:21 <armax> #link v
21:26:24 <armax> #undo
21:26:24 <openstack> Removing item from minutes: <ircmeeting.items.Link object at 0x7f5bc000d3d0>
21:26:30 <armax> #link https://bugs.launchpad.net/neutron/+bugs?field.tag=gate-failure
21:27:09 <armax> some of them look stale
21:27:30 <johnsom> The DIB one is really stale
21:27:42 <armax> if you’re the deputy, please make sure to have a look at http://status.openstack.org/elastic-recheck/data/uncategorized.html to see if there are new ones to be reported
21:28:26 <blogan> ill be bug deputy for the rest of this week
21:29:24 <armax> blogan: thanks
21:29:32 <armax> the functional job looks it’s acting up again
21:29:41 <armax> #link http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=6&fullscreen
21:30:09 <armax> also sc68cal
21:30:25 <armax> is proposing  grenade+dvr voting in the gate
21:30:59 <ihrachys> ++ for getting it sooner than later in the cycle
21:31:11 <armax> the dvr multinode compared to the non dvr one seems a bit more edgy
21:31:56 <armax> the long term plan is to drop the non-dvr multi jobs in the gate so it’d be nice to see whether there’s soemthing to worry about
21:32:22 <armax> now that we’re going into N-3
21:32:38 <armax> please be particularly careful about reports/patches that deprecate or touch config options
21:33:51 <armax> these need a release note typically
21:33:58 <dasm> what is the rule of thumb? every time when something gets deprecated or removed, it's needed to have reno?
21:34:33 <armax> I’d say yes
21:34:57 <armax> we want to be careful on how we message the change to our users
21:35:40 <armax> one more thing
21:35:44 * regXboi wanders out early to run errands before stores close
21:35:50 <armax> typically a DocImpact may be redundant if we have a release note added
21:35:58 <Sam-I-Am> regXboi: you live in the middle of nowhere? :)
21:36:00 * regXboi waves as he sneaks out
21:36:07 <Sam-I-Am> depends on the nature of the patch
21:36:11 <regXboi> Sam-I-Am: store closes at 5:30 pm
21:36:12 <Sam-I-Am> release notes are not docs
21:36:20 <armax> DocImpact in commit message generates a bug in the docs
21:36:28 <armax> project
21:36:32 <armax> my point being
21:36:45 <hichihara> Do we need reno when removing something according with deprecation?
21:37:04 <Sam-I-Am> we could make rel notes a lot more informative, but that requires me (or someone in docs) keeping up with them
21:37:08 <armax> if you think the change requires changes to the docs, then make sure you fix the doc bug too :)
21:37:20 <armax> or help the bug triage process
21:38:13 <armax> hichihara: adding a note in the patch and take it out afterwards is better than not having it at all
21:38:48 <armax> any comment/question?
21:39:00 <armax> we got covered for bug deputy for next week thanks to mlavalle
21:39:08 <hichihara> armax: I got it.
21:39:13 <armax> we’re still drowning a bit
21:39:18 <mlavalle> armax: yes, I am on the hook next week
21:39:35 <armax> since Newton started we have 700+ bugs filed and <300 fixed
21:39:41 <Sam-I-Am> i'm always here if you're wondering if something needs docs
21:39:51 <armax> Sam-I-Am: ack
21:40:14 <armax> someone wants to volunteer for the week of the 25th?
21:40:38 <dougwig> i'll be fishing in alaska, so i'd be a bad choice that week.  :)
21:40:53 <Sam-I-Am> dougwig: satellite wifi, sir :)
21:41:07 <Sam-I-Am> youcannotescape
21:41:07 <njohnston> I'll be sheep-wrangling at the county fair, so I'll have to wait for August
21:41:07 <armax> dougwig: what Sam-I-Am said :)
21:41:18 <Sam-I-Am> njohnston: isnt that what we do here?
21:41:21 <armax> ok let’s move on
21:41:27 <dougwig> heh, i've done it 3 times already, but i'll cover if no one else steps up.
21:41:33 <armax> #topic Docs
21:41:37 <Sam-I-Am> hey!
21:41:55 <Sam-I-Am> so, i was off for two weeks... and actually stayed away from the computer
21:41:58 <armax> Sam-I-Am: your thread doesn’t seem was very well received
21:42:00 <armax> #link http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
21:42:01 <Sam-I-Am> so thing kind of stalled a bit
21:42:03 <armax> at least so far
21:42:04 <Sam-I-Am> armax: yeah, i know :/
21:42:22 <Sam-I-Am> however, neutron is a great example (that i've been using with other PTLs) about how we can all make docs work
21:42:39 <armax> so I assume the marching order for now is to keep docs changes targeting openstack-manuals?
21:42:56 <Sam-I-Am> yeah, for now. for neutron it'd be easy to move the networking guide in-tree.
21:42:56 <armax> Sam-I-Am: pace will pick up as soon as we get after FF
21:43:02 <armax> Sam-I-Am: ack
21:43:02 <Sam-I-Am> neutron is the least of my worries, of course
21:43:08 <Sam-I-Am> you're setting a great example
21:43:12 <johnsom> I support this.  Octavia is working to put it's docs into the Octavia repo
21:43:24 <Sam-I-Am> ehhh well :)
21:43:48 <Sam-I-Am> make sure you at least a patch to the networking guide so people can find those docs
21:44:00 <Sam-I-Am> anyway, i'm currently working on fixing up an SFC docs patch
21:44:29 <Sam-I-Am> plus i'm still working on rearranging the net guide
21:44:33 <armax> Sam-I-Am: I am refreshing some instructions here https://review.openstack.org/#/c/335739/
21:44:50 <armax> Sam-I-Am: I’ll add details on how to get docs published for stadium projects
21:44:59 <armax> anything else on docs?
21:45:00 <Sam-I-Am> excellent
21:45:07 <armax> we’re running a bit tight
21:45:09 <Sam-I-Am> not much, just a lot of catch-up right now
21:45:19 <Sam-I-Am> and of course my email to the dev list
21:45:42 <armax> ok tanks
21:45:44 <armax> thanks
21:45:58 <armax> #topic transition to OSC
21:46:16 <armax> neither amotoki nor rtheis seem around
21:46:43 <jckasper> rtheis is out on vacation this week
21:46:59 <armax> jckasper: ack
21:47:03 <armax> change https://review.openstack.org/#/c/309587/ merged
21:47:07 <njohnston> I filed an OSC blueprint to get all the neutron QoS commands pulled over; I'll work it as soon as they approve it
21:47:12 <jckasper> back on the 19th I believe.
21:47:13 <njohnston> #link https://blueprints.launchpad.net/python-openstackclient/+spec/neutron-client-qos
21:48:12 <armax> ok
21:48:14 <armax> thanks
21:48:19 <armax> #topic Keystone v3
21:48:28 <armax> dasm, HenryG ^
21:48:42 <armax> anything worth sharing with the team, patch that needs some love?
21:48:50 <sbelous> so, i'm here again with the questions about making keystone-v3 job voting :) is there any news? are there a reasons to keep it not-voting?
21:48:56 <armax> last week I did promise an email to the rest of the team
21:49:05 <sbelous> may be some additional work is required? i'm ready to help if it needed
21:49:10 <armax> I did talk with HenryG about it and we have an etherpad up
21:49:29 <dasm> here. db patch is rolling: https://review.openstack.org/#/c/335786/
21:49:48 <HenryG> The next patchset will be very good if all comments are addressed. :)
21:49:49 <dasm> pretty much high level of failures, but didn't have time to dive into this. will look at this soon.
21:49:50 <armax> sbelous: it’s probably just getting stuck in review, let’s me look at it one more time
21:50:02 <armax> HenryG: cool
21:50:15 <armax> I guess we’re past the major errors
21:50:25 <sbelous> armax: ok, thanks
21:50:36 <HenryG> armax: yes, I think so
21:50:47 <armax> ok cool
21:51:26 <armax> if you have a patch that may be potentially affected by this transition please reach out to see how we can help
21:51:56 <armax> #topic neutron-lib
21:52:08 <armax> HenryG, dougwig, anything worth sharing?
21:52:19 <armax> I did post a simple patch this morning
21:52:21 <dougwig> mostly let's just highlight the reviewing change.
21:52:36 <armax> https://review.openstack.org/#/c/340523/
21:52:38 <dougwig> any neutron core can now +2, so everyone is encouraged to start reviewing.
21:53:03 <dougwig> the lib has special review guidelines, mostly around backwards compat, that can be found in the docs section.
21:53:08 <armax> that’s to make sure that once the API and API refs are ported over to Neutron lib these nicely show up in http://developer.openstack.org/api-ref/networking/
21:54:14 <armax> ok
21:54:21 <armax> #topic Open Discussion
21:54:33 <armax> there’s a topic
21:54:41 <armax> on Feature Classification Framework/Matrix
21:54:54 <armax> I have been meaning to review it
21:54:57 <armax> #link https://review.openstack.org/#/c/318192/
21:55:20 <armax> if I can get a couple of eyes over that’d be great
21:55:39 <ihrachys> I have something. anything to land before we cut N2? or I am free to go and push a openstack/releases patch?
21:56:15 <armax> ihrachys: let’s send an email out
21:56:24 <ihrachys> ack
21:56:28 <armax> ihrachys: and then you and I can get together tomorrow to go over the backlog
21:56:39 <armax> to see what we can push in and what we leave out
21:56:42 <Sam-I-Am> armax: does it make sense to link the support matrix from the networking guide?
21:56:55 <ihrachys> armax: ack. note I am Boston time this week.
21:56:59 <armax> Sam-I-Am: once the support matrix is well agreed on, yes
21:57:03 <Sam-I-Am> since it might be useful to operators
21:57:04 <Sam-I-Am> ok
21:57:10 <armax> ihrachys: ah so you can work 32 hours a day this week
21:57:10 <armax> nice
21:57:15 <ihrachys> right
21:57:21 <ihrachys> but not on upstream
21:57:29 <armax> ihrachys: I feel cheated
21:57:57 <armax> ihrachys: oh well, if you can spare a few minutes tomorrow morning, ping me
21:58:01 <armax> pls
21:58:05 <ihrachys> ack
21:58:42 <armax> ok
21:58:46 <armax> 2 minutes to the hour
21:58:52 <armax> anything else anyone would like to add?
21:59:06 <manjeets_> armax some old bugs
21:59:21 <armax> manjeets_: ?
21:59:27 <manjeets_> https://bugs.launchpad.net/neutron/+bug/1546910 affecting networking-odl
21:59:27 <openstack> Launchpad bug 1546910 in neutron "args pass to securitygroup precommit event should include the complete info" [Wishlist,In progress] - Assigned to Manjeet Singh Bhatia (manjeet-s-bhatia)
21:59:36 <armax> manjeets_: I’ll look into it
21:59:38 <manjeets_> patches are up there missing reviews
21:59:43 <manjeets_> thanks
21:59:50 <armax> #endmeeting