14:00:00 <jlibosva> #startmeeting networking
14:00:01 <openstack> Meeting started Tue Oct 10 14:00:00 2017 UTC and is due to finish in 60 minutes.  The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:04 <openstack> The meeting name has been set to 'networking'
14:00:08 <jlibosva> hi! \o/
14:00:17 <mlavalle> o/
14:00:20 <annp> hi
14:00:20 <haleyb> hi
14:00:29 <amotoki> hi
14:00:30 <jlibosva> #topic Announcements
14:00:38 <bcafarel> hello
14:00:40 <reedip_> o/
14:01:01 <davidsha> hi
14:01:07 <jlibosva> First thing - I noticed a new zuul v3 work is planned for tomorrow
14:01:24 <jlibosva> an outage is expected - more information at http://lists.openstack.org/pipermail/openstack-dev/2017-October/123337.html
14:01:27 * bcafarel crosses fingers
14:01:38 <jlibosva> scheduled time is 11 UTC tomorrow
14:02:06 <jlibosva> another great thing is happening tomorrow - which is abug triage sprint organized by mlavalle
14:02:17 <jlibosva> more information here
14:02:22 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2017-October/123000.html
14:02:53 <jlibosva> mlavalle: I see there were no replies on the thread - I assume it's still a thing
14:03:23 <mlavalle> yeah, all of those whoe saw it, let's pick a few bugs and triage them
14:03:42 <jlibosva> ack
14:03:44 <mlavalle> let's see how many we can knock out
14:04:03 <davidsha> +1
14:04:22 <jlibosva> next thing related to bug triaging - we changed bug deputy role from volunteering on meetings to a rotating role
14:04:26 <jlibosva> #link http://lists.openstack.org/pipermail/openstack-dev/2017-October/122983.html
14:04:44 <jlibosva> feel free to add your name at the wiki page if you'd like to help with bug triaging
14:05:06 <mlavalle> I want to thank all of those who volunteered
14:05:16 <jlibosva> that's all announcements from me. anybody has any other announcements to make?
14:05:34 <mlavalle> given the great response, each one of us will only be on duty a 3 times per year
14:05:52 <mlavalle> maybe a little more, but less than four for sure
14:06:12 <boden> FYI: supposedly we are moving back to zuul v3 tomorrow so we may have some things to work through with that… we can discuss more in the CI meeting later today
14:06:34 <mlavalle> boden: yeah, let's do that
14:07:01 <jlibosva> ok, thanks boden
14:07:16 <jlibosva> let's move on
14:07:18 <jlibosva> #topic Blueprints
14:08:14 <jlibosva> I think mlavalle made some cleaning in blueprints for Q and assigned up-to-date approvers, so thanks for doing that :)
14:08:28 <mlavalle> there is more to come
14:08:32 <jlibosva> #link https://blueprints.launchpad.net/neutron
14:08:39 <mlavalle> I hadn't made all the progress I wanted
14:08:55 <mlavalle> but making some progress so far
14:09:50 <jlibosva> mlavalle: are those pike BPs gonna be discussed with drivers?
14:10:21 <mlavalle> I need to continue the clean up
14:10:35 <mlavalle> I might bring some of them to the drivers meeting
14:10:43 <jlibosva> okie
14:10:53 <jlibosva> anybody has anything related to blueprints?
14:10:55 <mlavalle> I will try to have a clean slate by next week
14:11:17 <jlibosva> I'm looking at the release planning and the first milestone is set to next week
14:11:29 <jlibosva> 19 October 2017
14:11:36 <mlavalle> I think annp might want to highlight some of the logging pachsets
14:11:47 <mlavalle> that are targeted at Q-1
14:12:03 <jlibosva> I started reading the spec and I plan to dedicate more time to those patches
14:12:12 <mlavalle> if he is not around, hang on, I have the list
14:12:29 <annp> mlavalle, hi
14:12:56 <jlibosva> I was looking at https://review.openstack.org/#/q/topic:bug/1468366+(status:open+OR+status:merged) yesterday to get the status of where the BP stands
14:13:13 <annp> regarding logging patchsets: these patchs are ready for reviewing.
14:14:15 <mlavalle> The following are targeted for Q-1:
14:14:16 <annp> however, currently i didn't get more review from core :)
14:14:32 <mlavalle> #link https://review.openstack.org/396104
14:14:46 <mlavalle> #link  https://review.openstack.org/468265
14:14:59 <mlavalle> #link https://review.openstack.org/468281
14:15:18 <mlavalle> #link https://review.openstack.org/#/c/409819/
14:15:36 <mlavalle> jlibosva: so as far as logging let's focus on those four ^^^^
14:15:39 <mlavalle> this week
14:15:42 <jlibosva> mlavalle: ack, thanks
14:16:07 <amotoki> yeah, others are testing and devstack patches, so the above sounds reasonable
14:16:13 <annp> mlavalle, jlibosva: thanks.
14:16:27 <mlavalle> there are more patches in the logging series, but those are targeted for Q-2
14:16:51 <mlavalle> amotoki: hopefully you can help with the fourth one ;-)
14:17:27 <amotoki> mlavalle: sure. i hope i can review others too
14:17:39 <mlavalle> :-)
14:17:39 <jlibosva> anybody has any other blueprints that are scheduled to q1?
14:17:50 <annp> amotoki: thanks in advance.
14:18:18 <jlibosva> if not, we can jump to the next topic
14:18:24 <jlibosva> #topic Bugs
14:18:44 <jlibosva> mlavalle was the bug deputy last week
14:18:47 <mlavalle> so I was the bug deputy last week
14:18:51 <jlibosva> :)
14:19:03 <mlavalle> we don't have critical bugs as of now
14:19:19 <mlavalle> we had the big zuul v3 scare last Tuesday
14:19:45 <mlavalle> and then things fell back to normally gradually
14:20:11 <mlavalle> so we should be vigilant tomorrow, when they are switching it back again
14:20:37 <mlavalle> I spent time triaging new bugs. not much to highlight in this meeting
14:20:48 <jlibosva> ok, thanks mlavalle
14:20:53 <mlavalle> jlibosva: do you have anythng to highlight?
14:20:57 <jlibosva> nope
14:21:20 <jlibosva> just fyi, I'm the bug deputy for this week so I'll send a summary on Monday as I'm not gonna attend the US meeting next week
14:21:46 <jlibosva> I think we can move to docs topic
14:21:48 <jlibosva> #topic Docs
14:22:02 <jlibosva> mlavalle: you again :)
14:22:16 <mlavalle> jlibosva: no, that is boden
14:22:22 <jlibosva> oh, sorry
14:22:25 <mlavalle> and I know he's been busy
14:22:48 <boden> I’ve gone through all the doc and api-ref defects
14:23:01 <boden> there are a number of patches out there to fix a bunch of them
14:23:29 <boden> there’s also a small set (maybe 6) of “wishlist” doc defects… they are more enhancements so I probably won’t address them short term
14:24:01 <boden> a question: wasn’t someone going to make a list of the extensions to api-ref mapping to see which we are still missing?
14:24:12 <boden> I thought we discussed that at PTG
14:24:20 <amotoki> boden: it is me
14:24:31 <boden> amotoki: ok.. still on your TODO list?
14:24:33 <amotoki> sorry for late but i plan to make a list this week
14:24:42 <boden> no worries, just a friendly follow-up.. thanks!
14:24:54 <amotoki> thanks
14:25:03 <boden> there’s 1 doc patch that would be nice to merge, let me find it
14:25:27 <boden> https://review.openstack.org/#/c/505172
14:25:44 <boden> it fixes formatting with our install guide… seems like something we’d want to have documented properly
14:26:08 <boden> that’s it from me, unless there are comments
14:26:44 <mlavalle> boden: do you have any objections to merge the patch now?
14:27:09 <boden> mlavalle: nope… I think we may consider putting it in pike too
14:27:22 <mlavalle> boden: merging now
14:27:25 <boden> cool
14:27:34 <jlibosva> boden: thanks for updates
14:27:44 <jlibosva> anybody has anything else related to docs?
14:27:46 <mlavalle> done
14:28:24 <jlibosva> I guess not :)
14:28:30 <jlibosva> #topic OSC
14:28:34 <jlibosva> amotoki: hi :)
14:28:57 <amotoki> as we discussed in PTG, OSC main migration has completed
14:29:13 <amotoki> if there are some missing options or feature, feel free to file a bug to OSC
14:29:31 <amotoki> our current target is OSC plugin for advanced services
14:30:16 <amotoki> I haven't looked through neutronclient patches yet. will look through them by next week
14:30:32 <bcafarel> on python-neutronclient functional tests broke ~2 weeks ago so all osc recent reviews get -1
14:30:40 <amotoki> is there any patches or topic to raise?
14:31:00 <bcafarel> https://bugs.launchpad.net/python-neutronclient/+bug/1721553 (legacy CLI failing on keystone auth apparently)
14:31:01 <openstack> Launchpad bug 1721553 in python-neutronclient "Functional tests fail: Expecting to find domain in project / auth_url was not provided to the Neutron client" [Undecided,New]
14:31:35 <amotoki> bcafarel: will check it
14:31:51 <boden> in regards to the gap we have in OSC for resource attr extensions… I’m starting to get the feeling this might not happen in Queens, but more TBD if I can get anyone to respond about it :)
14:32:04 <bcafarel> thanks amotoki :) (sorry to add another one to your return todo list)
14:32:18 <amotoki> I see keystoneclient import is still used. it might be related. keystoneauth should be used.
14:33:32 <jlibosva> bcafarel: thanks for bringing this up
14:33:47 <jlibosva> amotoki: and thanks for the updates :)
14:33:54 <amotoki> boden: I think there are long term and short term solutions. is there any plan to move vendor-speciifc attr extension to the official one?
14:34:06 <amotoki> *in long term
14:34:42 <boden> amotoki no such plans ATM, I haven’t been able to get any response on the direction for OSC/SDK/etc.
14:35:36 <amotoki> in short term, we can keep neutron CLI. API-SIG folks do not like API extensions (for long term) as nova does and we need to discuss the direction including this point.
14:36:07 <boden> amotoki: ack
14:36:41 <mlavalle> is API-SIG cdent and company?
14:37:48 <amotoki> he is the API-SIG lead... micorversion folks think similar.
14:37:55 <mlavalle> ack
14:38:30 <amotoki> it is not an easy thing.... i know
14:38:39 <jlibosva> thanks guys, we shall move to the next topic I think
14:38:49 <amotoki> let's move on
14:38:49 <jlibosva> #topic neutron-lib
14:39:06 <jlibosva> boden: hi again :)
14:39:40 <boden> so there are 2 specs out for review that deal with decoupling db (we discussed a bit at PTG)… when folks get time
14:40:05 <boden> I’ve also been working on reviving a number of “consumption” patches in neutron and others
14:40:30 <boden> I’ve been updating all the impacted projects so that’s why I haven’t been sending ML notices.. so far so good, unless someone else has heard otherwise
14:40:50 <jlibosva> boden: do you have links handy to those specs?
14:41:03 <mlavalle> are those the ones we've been merging over the past few days?
14:41:27 <boden> for the specs: https://review.openstack.org/#/c/509564/  and https://review.openstack.org/#/c/473531/
14:41:42 <boden> mlavalle: yes, and there are still others in the queue
14:41:53 <mlavalle> I'll keep an eye on them
14:42:23 <boden> lots of work to be done in lib, but I won’t belabor details… neutron-lib business as usual :)
14:42:23 <jlibosva> thanks
14:42:42 <boden> nothing else critial to discuss ATM from me
14:43:12 <jlibosva> boden: thanks for updates
14:43:35 <jlibosva> unless nobody has anything to say to neutron-lib, we can move to open discussion
14:44:31 <jlibosva> #topic open discussion
14:44:39 <mlavalle> o/
14:44:41 <jlibosva> there is no topic on the wiki
14:44:54 <mlavalle> I have a topic I want to share with the team
14:45:09 <jlibosva> mlavalle: stage is yours :)
14:45:36 <mlavalle> Last week, we decided to have the Neutron drivers meeting in alternate times, like we do for this meeting
14:46:19 <mlavalle> up unitl now the meetings have been taking place at 2200UTC on Thursday
14:46:48 <mlavalle> we have decided to alternate that with 1400UTC on Thursday
14:46:59 <jlibosva> nice :)
14:47:05 <reedip_> that would be great mlavalle
14:47:13 <mlavalle> This week will be at this new time
14:47:13 <jlibosva> is also gonna be a bi-weekly?
14:47:17 <reedip_> Asia TZ can catch up then ...
14:47:26 <mlavalle> yeap, by-weekly alternation
14:47:59 <amotoki> mlavalle: is there any review to propose the change?
14:48:03 <mlavalle> with the new alternate time, we are targeting folks in the US East coast, Europe and the Middle Eastr
14:48:44 <mlavalle> and apparently also amotoki and yamamoto in Japan prefer this time
14:48:59 <mlavalle> amotoki: no, I will do it today
14:49:33 <amotoki> mlavalle: thanks. i just thought it makes everyone find the new meeting more easily
14:49:49 <mlavalle> amotoki: agree
14:49:56 <reedip_> amotoki +1
14:49:59 <jlibosva> +1
14:50:20 <jlibosva> we have 10 minutes, any other topic or we chose 10 minutes back?
14:50:30 <amotoki> Indian folks can join 1400UTC meeting :)
14:50:33 <davidsha> Can I put out an ask?
14:50:37 <hoangcx_> mlavalle: amotoki: Hi, I would like to know: Is there any plan to review about stadium inclusion for non-stadium projects in Queens?
14:51:01 <reedip_> Yes amotoki :)
14:51:13 <amotoki> there are two topics from davidsha and hoangcx_
14:51:19 <amotoki> davidsha: go ahead first
14:51:41 <mlavalle> hoangcx_: yes, if you have something to discuss on that, we can talk in the channel
14:51:50 <mlavalle> davidsha: go ahead
14:52:01 <davidsha> Neutron Classifier is working on it's service plugin atm and need people experienced with Oslo versioned objects for reviews, the patch isn't ready yet, but are there any volunteers?
14:52:15 <davidsha> patch is here: https://review.openstack.org/#/c/499571/
14:53:10 <mlavalle> the best person there is ihrachys
14:53:12 <jlibosva> davidsha: I think the best would be to loop ihrachys in
14:53:20 <bcafarel> :)
14:53:24 <mlavalle> I would ping him in the Neutron channel
14:53:33 <davidsha> mlavalle, jlibosva perfect I'll get in touch with him!
14:53:54 <mlavalle> hoangcx_: we have a few minutes here, go ahead
14:54:15 <hoangcx_> mlavalle: Thanks I will discuss about that later in the channel.
14:54:25 <mlavalle> cool
14:54:57 <amotoki> hoangcx_: is the topic about vpnaas inclusion?
14:55:00 <jlibosva> we have 5 mins left :)
14:55:25 <hoangcx_> amotoki: Yes. Let's discuss about it in neutron channel
14:55:51 <amotoki> my understanding is that l3 agent extension is the last point
14:56:10 <amotoki> and I think we can discuss it once it lands successfully
14:56:31 <amotoki> hoangcx_: ack
14:57:20 <jlibosva> any quick topic before we're at the top of the hour?
14:57:44 <jlibosva> ok, thanks everyone for joining and see you online :)
14:57:52 <jlibosva> #endmeeting