14:01:01 <ihrachys> #startmeeting networking
14:01:01 <openstack> Meeting started Tue Oct 11 14:01:01 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:04 <openstack> The meeting name has been set to 'networking'
14:01:09 <njohnston> o/
14:01:10 <rossella_s> hi :)
14:01:11 <dasm> o/
14:01:11 <sbelous> hi
14:01:13 <alraddarla> hi
14:01:13 <electrocucaracha> o/
14:01:14 <ajo> \o/
14:01:16 <yanyan> ihrachys, sorry for postpone :)
14:01:17 <hoangcx> hi
14:01:18 <mlavalle> o/
14:01:19 <johndperkins> o/
14:01:20 <HenryG> o/
14:01:25 <andreas_s> o/
14:01:25 <bcafarel> hi
14:01:27 <haleyb> hi
14:01:27 <dasanind_> hi
14:01:38 <ihrachys> yanyan: nevermind :)
14:01:40 <hichihara> hi
14:01:53 <ihrachys> #link https://wiki.openstack.org/wiki/Network/Meetings Agenda
14:02:23 <ihrachys> #topic Announcements
14:02:31 <johnsom> o/
14:02:35 <yamahata> hello
14:02:35 <john-davidge> o/
14:02:40 <ihrachys> first thing first, for those who maybe missed that... Newton is released!
14:02:49 <dasm> boooo!
14:02:51 <ihrachys> we are now officially in pure Ocata mode
14:02:56 <dasm> ooops... yay!
14:03:03 * john-davidge wears a party hat
14:03:29 <ihrachys> that said, we plan to release the first patch release for newton in next week or two, so if you have proper candidates to backport, please propose for review
14:04:27 <ihrachys> in other news, stable/mitaka and stable/liberty branches change their support phases that are defined in:
14:04:29 <ihrachys> #link http://docs.openstack.org/project-team-guide/stable-branches.html#support-phases
14:04:57 <ihrachys> I proposed final releases for the branches in previous status
14:05:03 <ihrachys> #link https://review.openstack.org/#/c/383781/ mitaka
14:05:03 <ihrachys> #link https://review.openstack.org/#/c/383789/ liberty
14:05:06 <ajo> so liberty goes into " Only critical bugfixes and security patches are acceptable"
14:05:30 <ajo> sorry
14:05:31 <ajo> that's mitaka :)
14:05:33 <ihrachys> if you believe something worthy must be included in any of those, please talk to neutron-stable-maint members
14:05:36 <dasm> announcement: http://lists.openstack.org/pipermail/openstack-dev/2016-October/105302.html
14:05:45 <ihrachys> ajo: yes, mitaka is critical/CVE, and liberty is CVE only now
14:05:50 <amotoki> it seems worth releasing neutornclient mitaka too.
14:05:52 <ihrachys> meaning, no backports into liberty in general
14:05:54 <ajo> ack, thanks ihrachys
14:06:09 <ihrachys> amotoki: ack. do you want to propose that, or should I?
14:06:21 <amotoki> ihrachys: will do it and let you know
14:06:26 <ihrachys> amotoki: thanks!
14:06:39 <ihrachys> speaking of releases, dasm is our new release liaison for Ocata time frame
14:06:54 <amotoki> dasm: thanks!
14:06:58 <ihrachys> also known as Dariusz (Darek) Smigel :)
14:07:04 <hichihara> dasm: Thanks!
14:07:19 <dasm> ihrachys: and after ocata, release liason probbably won't be needed (everything will be automated). am i right ihrachys?
14:07:24 <ajo> dasm++ thank you
14:07:38 <ihrachys> dasm: we still need someone to take care of proposed patches to make sense
14:07:57 <dasm> APPROVE EVERYTHING!
14:07:59 <ihrachys> dasm: f.e. so that we don't release something that breaks the rules
14:08:02 <dasm> ;)
14:08:04 <ajo> lol dasm
14:08:22 <ihrachys> dasm: I don't appreciate that attitude from someone who wears a release liaison hat ;)
14:08:46 <dasm> ;)
14:08:49 <ihrachys> to give everyone a reminder, we release neutron bits thru the following repo:     - https://git.openstack.org/cgit/openstack/releases
14:09:12 <ihrachys> and for stadium participants, the following guidelines may be of use: http://docs.openstack.org/developer/neutron/stadium/guidelines.html#releases
14:09:26 <ihrachys> speaking of liaisons, HenryG is our new oslo liaison for Ocata
14:09:32 <dasm> \o/
14:09:37 <ihrachys> welcome to both of liaisons :)
14:09:39 <ajo> HenryG, thank you too
14:10:08 <rossella_s> thanks dasm and HenryG
14:10:15 <ihrachys> [for those wondering what oslo liaison does, it's mostly being present on oslo team meetings, and raising red flags from our project there if we have an oslo related problem]
14:10:18 <amotoki> ihrachys: thank you for both liaison (especially oslo liaison so long)
14:10:52 <ihrachys> amotoki: my pleasure
14:11:12 <ihrachys> another set of announcements is related to summit planning
14:11:30 <electrocucaracha> long live the liaisons
14:11:35 <ihrachys> PTL is currently working with neutron-drivers team to define topics for design summit sessions for neutron
14:11:47 <ihrachys> #link https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Neutron%3A Neutron design summit
14:12:10 <ihrachys> there are some slots captured by the filter that are not relevant
14:12:17 <ihrachys> but I guess we'll live with it
14:12:31 <ihrachys> the topics should be complete in next two days
14:12:56 <ihrachys> at that time we should have all etherpad links properly set, and you'll be able to review their agendas in advance
14:13:14 <ihrachys> #topic Ocata planning
14:13:20 <dasm> speaking about Summit. Different projects announce presence on PTG. Is this required?
14:13:38 <ihrachys> dasm: I wonder. probably you should talk to armax.
14:13:43 <dasm> ihrachys: ack
14:13:44 <ajo> PTG?
14:13:51 <ihrachys> ajo: project team gathering
14:13:52 <dasm> Project Team Gathering == midcycle
14:13:54 <amotoki> Project team gatghering
14:14:03 <ajo> ahh thanks :)
14:14:09 <amotoki> http://www.openstack.org/ptg/
14:14:12 <john-davidge> dasm: except at the beginning of the cycle :P
14:14:39 <ihrachys> ok, speaking of Ocata cycle, this one will be quite short due to changes in the summit event planning
14:14:49 <ihrachys> #link https://releases.openstack.org/ocata/schedule.html Ocata schedule
14:15:07 <ihrachys> it's basically 4 months this time
14:15:17 <hichihara> There's only 19 weeks left Ocata release. We must keep in our mind ;)
14:15:23 <ihrachys> including Christmas
14:15:51 <ihrachys> which gets me to the next thing...
14:16:02 <hichihara> And including Summit.
14:16:19 <john-davidge> and thanksgiving...
14:16:29 <ihrachys> neutron-drivers team discussed the matter on the previous meeting, and the preliminary decision is to make this cycle more calm, stabilizing things and completing features that were incomplete in Newton
14:16:48 <ihrachys> #link http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-10-06-22.01.log.html Drivers meeting logs
14:16:49 <john-davidge> ihrachys: ++
14:16:56 <ihrachys> that section is starting @ 22:23:59
14:17:43 <ihrachys> so, don't expect many new features allowed in this cycle, if at all. the team will focus on "boring" stuff, like gate stability, bug fixing, and such.
14:18:01 <ihrachys> plus incomplete things, like push-notifications and such
14:18:32 <ihrachys> another thing that Armando wants to tackle this cycle is to complete stadium consolidation
14:18:38 <HenryG> There will be some neutron-lib work too, I think
14:18:52 <ihrachys> HenryG: sure thing, I guess it's part of ongoing/incomplete bucket
14:19:01 <ihrachys> #link http://lists.openstack.org/pipermail/openstack-dev/2016-October/105276.html
14:19:02 <hichihara> And OVO too?
14:19:21 <amotoki> yes, OVO is one of ongoing things.
14:19:35 <ihrachys> right
14:19:35 <ihrachys> all stadium participants, please review the email from PTL I linked above
14:19:46 <ihrachys> there is an action item for all of you
14:19:48 <njohnston> yep
14:20:22 <ihrachys> armax started a bunch of patches that review the current compliance of stadium projects with requirements
14:20:26 <ihrachys> #link https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs+branch:master+topic:stadium-implosion
14:20:54 <ihrachys> please review what's relevant to you, and fill in the missing gaps with info about your subprojects
14:21:29 <ihrachys> also, there should be a discussion on the summit around the final steps for the effort, if you are in Barcelona, please join it.
14:22:21 <ihrachys> #topic Bugs and Gate failures
14:22:33 <ihrachys> the previous week, dougwig was a bug deputy
14:23:01 <ihrachys> I wonder whether he is already up, because I haven't seen a report from him :)
14:23:27 <ihrachys> apparently not. #sad
14:23:57 <ihrachys> ok, I'll reach out to him out-of-band later
14:24:07 <ihrachys> we need a bug deputy volunteer for the next week.
14:24:26 <ihrachys> if there are volunteers for the summit week, and the week after that, that's also cool.
14:24:44 <dasm> i volunteer for summit week. i won't be attending, so at least i can try to help in other way
14:24:45 <ihrachys> for the latter, ideally, that should be someone not going to the summit
14:24:58 <john-davidge> I can do next week
14:25:00 <ihrachys> dasm: yay for you! it's yours
14:25:07 <dasm> sold!
14:25:21 <ihrachys> john-davidge: next as in Oct 17+?
14:25:40 <john-davidge> ihrachys: wait, did you need a deputy for this week or next?
14:25:46 <john-davidge> I can do either :)
14:25:48 <ihrachys> john-davidge: this one, but next is good too :)
14:25:52 <ihrachys> john-davidge: then take this one!
14:25:58 <john-davidge> ihrachys: done!
14:26:04 <ihrachys> john-davidge: and we'll need to find someone for the next one on the next meeting
14:26:06 <dasanind_> i can do next week too if john0davidge is doing this week
14:26:13 <ihrachys> dasanind_: great.
14:26:50 <ihrachys> john-davidge: dasanind_: dasm: make sure you understand responsibilities
14:26:53 <ihrachys> #link http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy
14:27:20 <john-davidge> For now, can I get some attention on: #link https://bugs.launchpad.net/neutron/+bug/1631693
14:27:20 <openstack> Launchpad bug 1631693 in neutron "prefix delegation does not work in newton" [High,In progress] - Assigned to John Davidge (john-davidge)
14:27:24 <ihrachys> thanks a lot folks, please someone of you, update https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy after the meeting with your names
14:27:34 <john-davidge> Prefix delegation bug went unnoticed after the pluggable ipam switch
14:27:55 <john-davidge> ihrachys: doing
14:28:26 <dasm> ihrachys: done. Bug deputy list updated.
14:28:31 <ihrachys> john-davidge: it makes it obvious it is not gated on
14:28:39 <ihrachys> dasm: thanks
14:28:58 <ihrachys> john-davidge: we'll look into the fix in due course, would be nice to see it in first patch release for Newton
14:29:04 <john-davidge> ihrachys: Yes, there are still many gaps in PD testing
14:29:45 <ihrachys> john-davidge: I believe some of them are actionable, so it's a matter of priorities. now that we have Ocata more conservative in terms of what's allowed in, you should have more time for testing coverage ;)
14:30:24 <ihrachys> #link http://grafana.openstack.org/dashboard/db/neutron-failure-rate Gate failure trend
14:30:57 <ihrachys> periodic job for neutron-lib-master is at 100%, but it's a known issue fixed by https://review.openstack.org/#/c/384041/
14:31:18 <ihrachys> grenade and tempest jobs in gate queue are not feeling great it seems too
14:31:21 <john-davidge> ihrachys: Yes, it's on my radar for sure :)
14:32:02 <ihrachys> I see grenade jobs trending at ~ 25% on the graph
14:32:33 <ihrachys> tempest full is a bit lower, staying at ~15%
14:33:24 <ihrachys> the latter graph makes me wonder why we have three 'gate-tempest-dsvm-full' named jobs there :-x
14:33:30 <ihrachys> here: http://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=5&fullscreen
14:33:43 <ihrachys> other jobs seem to be duplicated too
14:33:47 <ihrachys> is it just me?..
14:33:56 <haleyb> so we can fail 3x as often?
14:34:18 <ihrachys> it's not a separate job. I would think it's a dashboard definition bug?
14:34:19 <amotoki> actually there are three result dsvm-full, -ubuntu-trusty, -ubuntu-xenial
14:34:32 <haleyb> maybe one is xenial another trusty^^
14:34:34 <amotoki> all three are labeled as gate-tempest-dsvm-full. that is the reason.
14:35:06 <ihrachys> amotoki: oh!
14:35:18 <amotoki> really tricky..
14:35:34 <ihrachys> I guess we should split those on the dashboard
14:36:10 <ihrachys> I'll talk it with armax later, thanks for the idea on different distro flavour
14:36:40 <amotoki> https://git.openstack.org/cgit/openstack-infra/project-config/tree/grafana/neutron.yaml#n19 matches three results.
14:37:00 <ihrachys> so it's hard to tell right now anything reasonable based on that graph. I guess we'll need to fix it first and then recheck the trend.
14:37:03 <ihrachys> amotoki++
14:37:31 <ihrachys> speaking of gate, we continue collecting gate-failures https://bugs.launchpad.net/neutron/+bugs?field.tag=gate-failure
14:37:43 <ihrachys> not that we are very effective squashing those, but at least some got reported
14:38:44 <ihrachys> if you have cycles to use for common good, please take one from the list and squash it
14:38:47 <ihrachys> ok, let's move forward in the agenda
14:38:50 <ihrachys> #topic Docs
14:39:04 <ihrachys> several things
14:39:28 <ihrachys> first I can't get bored reminding about https://bugs.launchpad.net/neutron/+bugs?field.tag=doc and the need to get those fixed in due course
14:40:06 <ihrachys> second, there is api-ref initiative rolling in scope of neutron-lib where we capture the state of neutron api
14:40:14 <ihrachys> #link https://review.openstack.org/#/q/status:open+project:openstack/neutron-lib+branch:master+topic:bp/neutron-in-tree-api-ref
14:40:28 <ihrachys> seems like this link captures a significant number of patches related to the effort.
14:41:02 <ihrachys> would be nice to see people reviewing those, especially where you have domain expertise in particular piece of the picture
14:41:35 <ihrachys> other than that... I don't see Sam-I-Am so unless someone can give an update from docs team...
14:42:17 <ihrachys> I guess we'll move on then
14:42:21 <amotoki> sorry for reviewing api-ref patches slowly... but I am looking them steadly.
14:42:28 <ihrachys> #topic Transition to OSC
14:42:31 <ihrachys> rtheis: howdy
14:42:35 <rtheis> hi
14:42:45 <rtheis> osc 3.3.0 is out: http://docs.openstack.org/releasenotes/python-openstackclient/unreleased.html
14:42:55 <rtheis> a lot of enhancements and fixes
14:43:17 <ihrachys> rtheis: woot. where do we stand on the path to deprecate neutronclient? :)
14:43:56 <rtheis> We have a lot in the review queue now and think we can do this in ocata
14:44:27 <rtheis> We also need to handle the sdk 1.0 refactor: https://blueprints.launchpad.net/python-openstackclient/+spec/network-command-sdk-support
14:44:32 <amotoki> it also depends on osc plugin migrations of stadium projects too.
14:45:17 <ihrachys> amotoki: I guess their willingness to take the load can be part of stadium discussion :)
14:45:27 <johnsom> I had a question about OSC that went unanswered in the neutron channel.  I don't see an option to specify a security group when creating a port via OSC.  Is that WIP or ?
14:45:46 <rtheis> https://review.openstack.org/#/c/355797/
14:45:54 <rtheis> johnsom: ^^^
14:45:59 <ajo> amotoki, do we need any api-ref patches for QoS or is that merged?
14:46:15 <johnsom> Thanks!
14:46:26 <amotoki> ajo: checking..
14:46:37 <ihrachys> ajo: amotoki: let's check it offline
14:46:46 <ihrachys> #topic Neutron-lib
14:47:00 <ihrachys> HenryG: any worthy updates, apart from api-ref maybe?
14:47:07 <ajo> amotoki, ack, probaby I need to bring this up in the qos meeting
14:47:13 <ajo> let's check it online
14:47:14 <ajo> offline
14:47:15 <hoangcx> johnsom, Yes. I am taking care about that
14:47:16 <ajo> sorry :)
14:48:22 <ihrachys> ok, let's move on, I guess HenryG is off
14:48:25 <ihrachys> #topic On Demand Agenda
14:48:48 <ihrachys> there are no new topics added to the wiki page, so unless you bring something up right away, I will call it a day.
14:48:49 <ihrachys> 3...
14:49:00 <ihrachys> 2...
14:49:09 <ihrachys> 1...
14:49:17 <ihrachys> BOOOOM
14:49:20 <russellb> hi
14:49:21 <hichihara> :)
14:49:21 <russellb> one quick note
14:49:34 <ihrachys> russellb: ok let's pretend it did not happen. wassup
14:49:37 <russellb> there will be an OVN launch party at the Barcelona summit, if you're interested in an invite, just PM me
14:49:38 <russellb> that is all.
14:50:05 <ihrachys> ok, party announcements are welcome any time ;)
14:50:11 <russellb> ha
14:50:13 <ihrachys> russellb: thanks for the invite!
14:50:16 <russellb> of course
14:50:22 <russellb> thanks to vmware for throwing a party
14:50:33 <ihrachys> ok, we are done for today.
14:50:47 <hichihara> +1
14:50:52 <dasm> thanks
14:50:53 <electrocucaracha> thanks ihrachys
14:50:55 <ihrachys> thanks again folks for joining, and remember, this cycle is for all the boring things, so plan accordingly
14:50:58 <ihrachys> ciao!
14:51:01 <ihrachys> #endmeeting