21:00:58 <mestery> #startmeeting networking
21:00:59 <openstack> Meeting started Mon Sep 15 21:00:58 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:03 <openstack> The meeting name has been set to 'networking'
21:01:13 <mestery> Welcome back to our rotating meeting schedule, today at 2100 UTC :)
21:01:18 <mestery> #link https://wiki.openstack.org/wiki/Network/Meetings Agenda
21:01:27 <mestery> I'm hoping we can keep today's agenda at 30 minutes, so no pressure. ;)
21:01:37 <mestery> Given where we're at in the release, lets see if we can do it.
21:01:44 <mestery> #Announcements
21:01:44 <gus> (hi)
21:01:56 <mestery> Juno-rc1 is out!
21:02:00 <mestery> Well sorry
21:02:01 <mestery> Not out,
21:02:06 <mestery> I mean, we're at feature freeze
21:02:09 <mestery> Which is less exciting I know
21:02:11 <mestery> #link https://launchpad.net/neutron/+milestone/juno-rc1
21:02:20 <mestery> We merged 10 of 11 BPs targeted there, so thanks to all the cores for help!
21:02:36 <mestery> Just a note for reviewers: We're at feature freeze now, as well as string and dependency freeze.
21:02:41 <mestery> So be cautious while reviewing
21:02:55 <mestery> Any questions on the freeze in effect?
21:03:01 * salv-orlando does not remember what string freeze is?
21:03:14 <mestery> #link https://wiki.openstack.org/wiki/StringFreeze
21:03:15 <kevinbenton> no more translated string changes
21:03:16 <mestery> salv-orlando: ^^^
21:03:18 <sc68cal> refresh my memory, does the freeze apply to bugs?
21:03:29 <salv-orlando> ah right the thing for giving i18n a chance to catch up
21:03:40 <enikanorov_> is string freeze a some new requirement?
21:03:47 <mestery> sc68cal: We'll be more and more restrictive going forward on bugs, yes
21:03:57 <mestery> enikanorov_: Not new, it's been there for at least one release so far
21:04:01 <salv-orlando> sc68cal: if that was frozen too than it would have been release time
21:04:24 * nati_ueno wondering minnesota get freezed
21:04:36 <sc68cal> ok, I'll wait for my section to discuss
21:04:38 <armax> so in other words: replace all log statements to debug and you’ll get your change merged?
21:04:39 <armax> :)
21:04:44 <mestery> One other quick announcement here: Looks like a freenode server was compromised, would be a good idea to change your freenode password
21:04:45 <mestery> #link https://blog.freenode.net/2014/09/server-issues-2/
21:04:51 <enikanorov_> armax: ha
21:05:01 <mestery> Any other announcements?
21:05:35 <mestery> #topic Bugs
21:05:38 <mestery> enikanorov_: Hi!
21:05:40 <enikanorov_> hi
21:05:56 <enikanorov_> so last week the severety of two bugs were set to critical:
21:05:58 * markmcclain joins late
21:06:03 <enikanorov_> https://bugs.launchpad.net/neutron/+bug/1357055
21:06:04 <uvirtbot> Launchpad bug 1357055 in nova "Race to delete shared subnet in Tempest neutron full jobs" [Critical,Confirmed]
21:06:33 <enikanorov_> this is actually some VM having dangling port after a test, so tests resources can't get deleted
21:06:42 <enikanorov_> this issue is being hit quite often
21:07:05 <enikanorov_> and another one is https://bugs.launchpad.net/neutron/+bug/1357476
21:07:07 <armax> there was another alongs the same lines
21:07:08 <uvirtbot> Launchpad bug 1357476 in nova "Timeout waiting for vif plugging callback for instance" [Critical,Confirmed]
21:07:20 <armax> the triaging I did revealed that was most likely a Nova issue
21:08:32 <enikanorov_> salv-orlando: do you have any more info on the latter one?
21:08:40 <mestery> enikanorov_: Thanks for sharing these, the first one has no one assigned. armax, do you ahve a link to the bug you triaged which looked similar?
21:08:56 <armax> mestery: I am looking for it bear with me
21:08:57 <mestery> Wondering if we could dupe them if they are the same
21:08:59 <mestery> armax: thanks!
21:09:42 <salv-orlando> enikanorov_: nope. I have not yet looked at it. The references devs for this kind of failures are arosen and dansmith
21:09:54 <enikanorov_> salv-orlando: good to know
21:10:22 <enikanorov_> another issue that i think worth fixing in rc is a bug with NoopFirewallDriver
21:10:23 <salv-orlando> they are the ‘owners’ of the vif plugging callbacks. However enikanorov_ bear in mind that this failure might also mean neutron fails to wire the VIF and then we have a regression in the OVS agent
21:10:30 <enikanorov_> let me find the link
21:10:50 <armax> mestery: #link https://bugs.launchpad.net/neutron/+bug/1283599
21:10:51 <mestery> enikanorov_: IS this it? https://review.openstack.org/121645
21:10:52 <uvirtbot> Launchpad bug 1283599 in tempest "TestNetworkBasicOps occasionally fails to delete resources" [Undecided,Invalid]
21:10:56 <mestery> armax: thanks!
21:11:19 <enikanorov_> mestery: this one bug/1365806
21:11:24 <enikanorov_> oops
21:11:31 <enikanorov_> ttps://bugs.launchpad.net/neutron/+bug/1365806
21:11:50 <enikanorov_> the patch I submitted fixes just a minor trace in the ovs agent logs
21:11:57 <mestery> enikanorov_: Got it, thanks!
21:12:17 <enikanorov_> i think bug/1365806 has another fix to a slightly different issue.
21:12:24 <mestery> armax: Can you validate the bug you linked is a dup of what enikanorov_ posted above so we can get this into nova's hands for fixing if it is a nova issue?
21:12:38 <armax> mestery: yup
21:12:44 <armax> mestery: I’ll look into it
21:12:45 <mestery> armax: thank you!
21:12:59 <mestery> enikanorov_: can you elaborate?
21:13:07 <mestery> enikanorov_: around 1365806?
21:13:36 <enikanorov_> mestery: yes, so one issue is that even in case of NoopDriver agent pulls sec groups which could be avoided
21:14:06 <mestery> enikanorov_: OK
21:14:47 <enikanorov_> on other bugs team is dealing with them on daily basis
21:14:50 <enikanorov_> that's all from my side
21:15:04 <mestery> enikanorov_: Thank you for the update on the bugs!
21:15:24 <mestery> #topic Final Juno Client Release
21:15:34 <mestery> I'm planning to cut one more release of the client for Juno tomorrow.
21:15:46 <mestery> I was waiting for the L3 HA CLI patch to merge, and it did: https://review.openstack.org/#/c/108378/
21:15:52 <mestery> #link http://lists.openstack.org/pipermail/openstack-dev/2014-September/045487.html
21:16:02 <mestery> Per the discussion on the mailing list, all clients will be cut by the 18th this week.
21:16:08 <mestery> So if anyone has a client bug or patch, please speak up now!
21:16:38 <gus> https://review.openstack.org/#/c/113727/
21:16:43 * mestery looks
21:16:48 <gus> ^ minor, would be ok if not included.
21:17:03 <markmcclain> gus: I can help review that one
21:17:10 <mestery> gus: I think that one looks ok, will review post meeting unless other cores beat me to it
21:17:14 <mestery> gus: thanks for bringing it up!
21:17:45 <mestery> OK moving on from the client ...
21:17:49 <mestery> #topic Kilo Design Summit Etherpad
21:17:54 <mestery> #link http://lists.openstack.org/pipermail/openstack-dev/2014-September/045844.html
21:17:57 <ZZelle_> mestery, https://review.openstack.org/121014 also ... currently neutronclient uses invalid headers
21:18:02 <mestery> #undo
21:18:03 <openstack> Removing item from minutes: <ircmeeting.items.Link object at 0x1e7f450>
21:18:07 <mestery> #undo
21:18:08 <openstack> Removing item from minutes: <ircmeeting.items.Topic object at 0x1eb22d0>
21:18:12 <mestery> ZZelle_: looking
21:18:34 <mestery> ZZelle_: I think armax has previously reviewed that one, it would be good to get that one in too.
21:18:41 <mestery> markmcclain: If you want another one to review ^^^
21:19:05 <markmcclain> mestery: I'll take a look
21:19:13 <mestery> markmcclain:  thanks!
21:19:21 * mestery waits a minute for other client bugs to pop up
21:19:59 <mestery> #topic Kilo Design Summit Etherpad
21:20:05 <mestery> #link http://lists.openstack.org/pipermail/openstack-dev/2014-September/045844.html
21:20:16 <mestery> Per that email, we are moving away from the submission tool
21:20:21 <mestery> towards collaborate etheprads for summit planning
21:20:32 <mestery> #link https://etherpad.openstack.org/p/kilo-neutron-summit-topics
21:20:45 <mestery> That one is the neutron deisng summit pad
21:20:46 <mestery> #link https://wiki.openstack.org/wiki/Summit/Planning
21:20:51 <mestery> That one is for all projects collected together
21:20:59 <mestery> So, if you ahve a summit idea, please propose it on the etherpad
21:21:07 <mestery> And we'll work to setup the summit sessions.
21:21:13 * mestery waits for it ...
21:21:26 <Sukhdev> mestery: I added one item to the etherpad
21:21:34 <mestery> Sukhdev: thanks, excellent!
21:22:05 <anteaya> let's have a reminder to folks to use the feature in the top right corner and enter your name, thank you
21:22:13 <mestery> anteaya: That's a very good point!
21:22:22 <mestery> Also, keep in mind we will only have 2 days for design summit talks this time.
21:22:25 <mestery> One half day less
21:22:39 <mestery> So, we have to focus on things which are important for the broader community and which need face to face time for discussions
21:22:45 <kevinbenton> mestery: it’s a good thing all of these seem like easy short topics ;-)
21:22:47 <emagana> mestery: Should we add our name in front of the proposed sessions?
21:22:51 <mestery> kevinbenton: Ha!
21:23:07 <mestery> emagana: That's fine for now, if you add something, please feel free to add yoru name
21:23:16 <emagana> mestery: or just the name of the session!
21:23:20 <salv-orlando> was ever any decision regarding sessione lenght taken?
21:23:21 <emagana> mestery: got it!
21:23:35 <mestery> salv-orlando: Yes, we are free to have thigns overflow the 40 minute slot
21:23:42 <mestery> Basically, we get to plan things how we want them as a community
21:23:50 <salv-orlando> mestery: very well.
21:23:54 <mestery> salv-orlando: Sound ok?
21:24:00 <banix> why just two days in a 5-day conference… Seems too short
21:24:20 <mestery> banix: One day is cross-project, and Friday is reserved as well for smaller gatherings and discussions.
21:24:28 <mestery> banix: Plus, we have more projects now which require space
21:24:36 <mestery> And the Paris location is smaller than Atlanta
21:24:41 <mestery> So, less space as well
21:25:02 * salv-orlando reminds himself that the summit is for beers first
21:25:10 <salv-orlando> well, it’s going to be wine this time
21:25:14 * mestery isn't sure what salv-orlando has against hard liquor ...
21:25:29 <mestery> salv-orlando: :P
21:25:30 <banix> mestery: ok thanks.
21:25:34 <mestery> banix: Sure!
21:25:39 <markmcclain> banix: also consider 6 mos is a really short span… when we had more times often we discussed things that ended up being 3+ cycles later before we impl
21:25:47 <mestery> markmcclain: ++
21:26:01 <banix> i see
21:26:32 <Sukhdev> mestery: Do we know which days is design summit?
21:26:40 <anteaya> the last 4
21:26:45 <salv-orlando> markmcclain: that’s correct. Indeed I’d rather spend all our summit time on 5/6 sticky items we must immediately address rahter than discussion forward looking ideas which are best fleshed out on the ml first
21:26:46 <mestery> anteaya: thanks
21:26:48 <anteaya> tuesday to friday
21:27:07 <Sukhdev> anteaya: I ment for Neutron design sessions?
21:27:09 <anteaya> tues is cross project, wed and thurs design sesseions per program friday pods
21:27:13 <mlavalle> salv-orlando: +1
21:27:15 <anteaya> wed and thurs
21:27:31 <mestery> #info Neutron sessions will be on Wednesday and Thursday
21:27:33 <Sukhdev> anteaya: thanks
21:27:35 <anteaya> np
21:27:36 <mestery> #info Cross-project track is Tuesday
21:27:45 <mestery> #info Friday is for program pods
21:27:48 <mestery> anteaya: thanks for the info!
21:27:50 <anteaya> np
21:28:01 <mestery> Any other questions on how we'll plan the design summit this time?
21:28:20 <markmcclain> salv-orlando: agreed… I think focus will help us for planning
21:28:38 <banix> salv-orlando: yes, makes sense. then we have to be very selective in picking the sessions topics.
21:28:38 <salv-orlando> mestery: yes can we throw shoes to everybody thinks a summit session is a talk?
21:28:56 <anteaya> folks know about the third party cross project etherpad: https://etherpad.openstack.org/p/kilo-third-party-items ?
21:28:58 <marun_afk> salv-orlando: only shoes?
21:29:02 <mestery> salv-orlando: Absolutely! In fact though, hopefully this community planning will relieve us from those.
21:29:17 <mestery> #link https://etherpad.openstack.org/p/kilo-third-party-items
21:29:51 <Sukhdev> anteaya: Thanks for sharing
21:29:55 <anteaya> np
21:30:10 <mestery> OK, moving on ...
21:30:11 <mestery> #topic Docs
21:30:12 <anteaya> items there will be discussed at the third party meetings
21:30:15 <mestery> emagana: Hi!
21:30:18 <emagana> mestery: here!
21:30:25 <mestery> emagana: We've reached the point of the release where we all need to help with docs. :)
21:30:32 <emagana> mestery: Just updated the wiki.. in order to keep this meeting short
21:30:46 <mestery> emagana: that's awesome on both fronts ;)
21:31:23 <emagana> mestery: correct, do you want me to expand on the activities/
21:31:25 <emagana> ?
21:31:36 <mestery> emagana: I think we're good unless you have something urgent, thanks!
21:32:00 <mestery> #topic Open Discussion
21:32:05 <mestery> In the interest of keeping this short ...
21:32:15 <mestery> Hopefully we're at the quietest point of the release now
21:32:20 * kevinbenton thinks mestery has somewhere to me…
21:32:26 <mestery> So in the interest of that as well, trying to keep this meeting short.
21:32:28 <kevinbenton> to be*
21:32:32 <mestery> kevinbenton: If only ;)
21:32:46 <enikanorov_> mestery: is the fate of lbaas decided? will it split?
21:33:28 <carl_baldwin> mestery: https://review.openstack.org/#/c/120603/ - to add the dvr experimental job to the check queue (non-voting).  I feel this is important, do others agree?
21:33:31 <banix> any new info on incubator and planning along that direction?
21:33:44 <mestery> enikanorov_: We're working with the team on that, and adding them into the incubator/feature branch proposal
21:33:55 <mestery> carl_baldwin: looking
21:34:09 <mestery> carl_baldwin: Agreed, in fact I have voted with my review there :)
21:34:21 <enikanorov_> mestery: i'm thinking about the future of already-integrated lbaas code (e.g. v1)
21:34:21 <carl_baldwin> mestery: Okay, I’ll ping infra again.
21:34:50 <dougwig__> enikanorov_: planned to be frozen/deprecated whenever v2 is in a usable state.
21:35:13 <mestery> enikanorov_: It depends on if we as a team decide to move all services into a seperate repository or not I guess.
21:35:14 <enikanorov_> it is frozen de facto right now...
21:35:35 <dougwig__> true.
21:35:37 <mestery> banix: I left off an incubator update for this week, but know that markmcclain and I have been talking with the LBaaS folks around their inclusion there.
21:35:43 <enikanorov_> well, ok, that was just my curiosity, i was not planning to argue :)
21:35:50 <sc68cal> IPv6 subteam has a small change for security groups that we need for IPv6 DHCP - https://review.openstack.org/#/c/103811/ - perhaps core reviewers could take a look?
21:35:56 <banix> mestery:  ok thanks
21:35:58 <mestery> sc68cal: looking
21:36:32 <sc68cal> mestery: thanks :)
21:36:42 <mestery> sc68cal: That one looks important, I've tagged it RC1
21:36:51 <sc68cal> mestery: perfect, thanks :)
21:37:13 <sc68cal> it nearly slipped my radar a couple times due to some issues with the gate, :)
21:37:46 <mestery> sc68cal: No doubt, thanks for bringing it up!
21:38:18 <mestery> OK, thanks everyone!
21:38:31 <mestery> Reminder: Next week's meeting is Tuesday at 1400UTC.
21:38:38 <mestery> We'll see you all there and in-channel!
21:38:39 <mestery> #endmeeting