21:01:06 <johnthetubaguy> #startmeeting Nova
21:01:06 <openstack> Meeting started Thu Aug 27 21:01:06 2015 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:11 <openstack> The meeting name has been set to 'nova'
21:01:16 <dansmith> o/
21:01:18 <rlrossit> o/
21:01:20 <mriedem> hiya
21:01:23 <bauzas> \o
21:01:25 <n0ano> o/
21:01:38 <edleafe> o/
21:01:41 <melwitt> o/
21:01:45 <scottda> hi
21:02:10 <johnthetubaguy> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:02:17 <johnthetubaguy> #topic Release Status
21:02:30 <johnthetubaguy> #info September 1st to 3rd: Liberty-3 and the mega freeze
21:02:39 <johnthetubaguy> #link https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule
21:03:08 <johnthetubaguy> so next week we hit string freeze, dependency freeze, feature freeze, and all that jazz
21:03:36 <mriedem> and novaclient 2.27.0 release on 9/1
21:03:40 <bauzas> big question, fencing on Tues or Thur ?
21:03:41 <johnthetubaguy> #info mriedem is working on putting together a python-novaclient release on tuesday, let him know if there is something that must be in that
21:03:44 <mriedem> someone remind me early if i forget
21:04:03 <johnthetubaguy> bauzas: good question
21:04:11 <johnthetubaguy> bauzas: it generally depends on the gate
21:04:25 <johnthetubaguy> bauzas: we start tuesday, to ensure we release by thursday
21:04:33 <bauzas> we agree it's a soft deadline, just a l-3 tag ?
21:04:41 <johnthetubaguy> bauzas: this is a super hard one
21:04:58 <johnthetubaguy> our friends doing translations and docs need our help by sticking to the deadline
21:05:01 <dansmith> second-hardest of all
21:05:05 <bauzas> by 'soft' I meant about tagging or branching
21:05:13 <johnthetubaguy> oh, its tagging
21:05:17 <johnthetubaguy> we branch at RC
21:05:24 <johnthetubaguy> unless I missing something major
21:05:36 <bauzas> okay, was just checking
21:05:41 <johnthetubaguy> cools, its good to check
21:06:07 <johnthetubaguy> anyways, I am kinda winding a few things up already, you will have noticed a few cells ones get the the chop this afternoon
21:06:21 <johnthetubaguy> mostly stuff that was looking like a no hoper, in terms of merging
21:06:33 <dims> o/
21:06:40 <johnthetubaguy> I vote we talk in next weeks meeting about the exception process
21:06:46 <bauzas> +1
21:06:54 <johnthetubaguy> anyways, any more questions?
21:07:09 <johnthetubaguy> we can always cover those in Open
21:07:13 <johnthetubaguy> #topic Bugs
21:07:46 <johnthetubaguy> mriedem: I think you had some gate patches earlier, any more to cover here?
21:07:56 <mriedem> graph looks good on http://status.openstack.org/elastic-recheck/index.html#1487570
21:08:09 <mriedem> so i don't know of any critical nova-specific gate bugs right now
21:08:17 <johnthetubaguy> so at some point very soon, we need to start looking about for release blockers
21:08:32 <mriedem> looks like cells is impacted by https://bugs.launchpad.net/tempest/+bug/1489581
21:08:34 <openstack> Launchpad bug 1489581 in tempest "test_create_ebs_image_and_check_boot is race failing" [High,In progress] - Assigned to Andrey Pavlov (apavlov-e)
21:08:37 <bauzas> yup
21:08:39 <mriedem> as are most things
21:08:45 <mriedem> there is a patch up in tempest to fix that though
21:08:56 <mriedem> i added nova to that bug since it seems we could do some validation/wait logic in nova in that case
21:09:12 <mriedem> not high priority though
21:09:43 <mriedem> would be a good time for subteams to raise up high priority bugs for them before l-3
21:09:53 <mriedem> like, in the etherpad, not here
21:10:05 <johnthetubaguy> #link https://wiki.openstack.org/wiki/PTL_Guide#Special_actions_between_Feature_freeze_and_RC1
21:10:09 <johnthetubaguy> mriedem: very very good point
21:10:25 <johnthetubaguy> I vote we keep using this: https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
21:10:41 <bauzas> before l-3 seems a bit short, I was planning to focus on bugs during RC1
21:10:50 <mriedem> bauzas: rc1 is too late
21:10:50 <johnthetubaguy> #help please raise up high priority (possibly release blocking) bugs in the appropriate subteam in here: https://etherpad.openstack.org/p/liberty-nova-priorities-tracking
21:10:55 <mriedem> rc bugs are stopship
21:11:02 <dansmith> yeah
21:11:21 <johnthetubaguy> bauzas: this last cycle was bug fixing time, hence the kicking out of the blueprints really
21:12:04 <bauzas> okay, I thought FF was the best period for focusing on bugs, if not then l-3 ?
21:12:17 <johnthetubaguy> yeah **-3 is a great time for bugs
21:12:23 <dansmith> between L3 and RC1
21:12:32 <bauzas> dansmith: that ^
21:12:39 <dansmith> you said "during RC1"
21:12:42 <johnthetubaguy> yeah, bugs only for now
21:12:43 <bauzas> dansmith: when I say RC1, I mean the FF period
21:12:47 <johnthetubaguy> ah
21:12:49 <dansmith> which we interpreted as "between RC1 and RC2" I think
21:12:57 <johnthetubaguy> yeah
21:12:59 <johnthetubaguy> confusion
21:13:02 * bauzas has to learn more than just English
21:13:05 <johnthetubaguy> anyways bugs fixes now
21:13:15 <johnthetubaguy> go go bug fixes
21:13:24 <johnthetubaguy> ideally ones people care about
21:13:43 <johnthetubaguy> we should move on I guess
21:13:54 <johnthetubaguy> #topic Open Discussion
21:14:06 <johnthetubaguy> so I skipped stuck reviews and regular reminders
21:14:15 <johnthetubaguy> because there are none, and we covered the reminders already
21:14:19 <dansmith> yay
21:14:31 * dansmith cues the "wrap it up music"
21:14:35 <johnthetubaguy> I dumped some random stuff in here, but should be quick
21:14:40 <johnthetubaguy> dansmith: heh
21:14:47 <johnthetubaguy> so summit session slots
21:14:54 <johnthetubaguy> we have to submit our requests
21:15:10 <johnthetubaguy> I think we wanted the same as last time? if I remember the wrap up session correctly?
21:15:13 <mriedem> keep in mind that i think cinder was interested in a cross-project session
21:15:23 <mriedem> thingee: ^
21:15:39 <mriedem> friday meetup is always popular
21:15:42 <johnthetubaguy> mriedem: yeah, good point, I think we can do that like the neutron one, I should ask ttx about the scheduling on that
21:15:54 <johnthetubaguy> yeah, friday meet up is solid
21:15:55 <mriedem> thursday afternoon priorities
21:16:13 <mriedem> how do you plan on getting suggestions for topics and filtering that soonish?
21:16:21 <scottda> yes, cinder is interested in a cross-project session
21:16:32 <scottda> to discuss changes in Cinder-Nova API
21:16:33 <dansmith> I think the bar for those sessions is high
21:16:39 <johnthetubaguy> mriedem: I think thats later on
21:16:53 <johnthetubaguy> yeah, I think its more likely to be a nova sessions, thats tagged also as cinder
21:16:53 <mriedem> i'm just asking, i wont' be there so it doesn't really matter ot me
21:17:04 <johnthetubaguy> cross project told me, "more than two projects"
21:17:08 <johnthetubaguy> which was totally fair
21:17:09 <dansmith> yeah
21:17:10 <mriedem> orly
21:17:18 <johnthetubaguy> mriedem: :'(
21:17:21 <mriedem> i guess that makes sense
21:17:23 <sc68cal> we plan on having a cross project session for nova neutron
21:17:40 <sc68cal> even if to just recap work since Vancouver
21:17:44 <sc68cal> ?
21:17:51 <mriedem> was there progress since YVR?
21:17:57 * mriedem pokes
21:18:01 <johnthetubaguy> so we should back up a little
21:18:09 <johnthetubaguy> there are going to be tones of sessions
21:18:11 <dansmith> I think that getting another one for nova-neutron will probably be hard
21:18:16 <johnthetubaguy> the question is, room formats
21:18:28 <bauzas> fishbowls?
21:18:30 <johnthetubaguy> dansmith: yeah, they will not let us do another cross project on that
21:18:32 <johnthetubaguy> yeah
21:18:34 <dansmith> johnthetubaguy: sounds like "same as last time"
21:18:42 <johnthetubaguy> dansmith: yeah I am +1 that
21:18:45 <sc68cal> mriedem: yes there was :/
21:18:46 <mriedem> johnthetubaguy: who wont?
21:18:57 <dansmith> mriedem: they
21:18:59 <johnthetubaguy> mriedem: the cross project folks (TC?)
21:19:04 <mriedem> f them
21:19:27 <mriedem> are they actually working on the projects? if not, why do they have a say?
21:19:29 <anteaya> yeah it is a tc sub committee who decides cross project sessions, from those proposed
21:19:32 <johnthetubaguy> mriedem: I figure we just use one of our sessions, and invite our neutron folks to join, but we can work that out
21:19:39 <mriedem> sure
21:19:41 <mriedem> bend the rules
21:19:49 <mriedem> or friday meetup
21:19:51 <johnthetubaguy> mriedem: yeah, we can do what we like with "Nova" time
21:19:54 <dansmith> johnthetubaguy: if we need one, yeah
21:20:00 <anteaya> we can propose a cross project session and have a back up plan
21:20:04 <johnthetubaguy> dansmith: right, thats the other question
21:20:12 <johnthetubaguy> anteaya: yeah, that worked last time
21:20:16 <johnthetubaguy> anyways
21:20:18 <mriedem> cross project: nova + neutron + nfv + containers + ansible
21:20:19 <mriedem> done
21:20:22 <johnthetubaguy> we are good with no work rooms
21:20:38 * johnthetubaguy cuts and pastes the title from mriedem
21:20:50 <dansmith> TBH, I'm surprised we're even having this shindig, given that mriedem isn't coming
21:20:57 <anteaya> what?
21:20:59 <mriedem> i know
21:21:00 <mriedem> seriously
21:21:01 <tonyb> johnthetubaguy: I don't think we'll have anything we can meaningfully do in an hour
21:21:10 <tonyb> johnthetubaguy: so I'd say no workrooms
21:21:19 <johnthetubaguy> tonyb: I certainly lean that way
21:21:22 <dansmith> +1
21:21:27 <dansmith> leave those for the people that actually do work
21:21:38 <mriedem> workrooms != design sessions right?
21:21:49 <johnthetubaguy> I like the "make it really hard to use your laptop" rooms, it stimulates conversation
21:21:50 <mriedem> workroom == "hackathon"
21:21:51 <tonyb> mriedem: correct
21:21:57 <johnthetubaguy> it has tables
21:22:03 <johnthetubaguy> and new for this time, a LCD screen
21:22:08 <tonyb> mriedem: You get ~1hour to "knock something out"
21:22:13 <johnthetubaguy> sorry, I think it is "boardroom style"
21:22:21 <tonyb> mriedem: they work well but only for small tightly defined things
21:22:24 <johnthetubaguy> tonyb: it might actually be 45 mins, but thats splitting hairs
21:22:26 <tonyb> ie not nova :D
21:22:34 <mriedem> dansmith is going to lose it if we don't move on
21:22:40 <johnthetubaguy> yeah
21:22:43 <johnthetubaguy> me too
21:22:44 <tonyb> johnthetubaguy: I said ~(approx)1hour :)
21:22:45 * dansmith hovers over the play button
21:22:59 <johnthetubaguy> so I am voting same as next time
21:23:03 <johnthetubaguy> cool, lets see if that works
21:23:09 <johnthetubaguy> its a small venue
21:23:17 <johnthetubaguy> user survey
21:23:21 <johnthetubaguy> there is a new one
21:23:30 <johnthetubaguy> let me know if there are questions you want it that
21:23:42 <johnthetubaguy> and I can pass that along to foundation folks organising that
21:23:54 <johnthetubaguy> except I should have told them on tuesday, so make it quick
21:24:00 <johnthetubaguy> one more thing, just to annoy people
21:24:05 <johnthetubaguy> Product management working group
21:24:10 <johnthetubaguy> I am actually talking to them
21:24:15 <johnthetubaguy> we are getting a CPL
21:24:25 <mriedem> oh boy
21:24:26 <mriedem> suits
21:24:36 <johnthetubaguy> he seems nice though, he used to code
21:24:46 <dansmith> oh dear
21:24:47 <mriedem> fortran
21:24:49 <tonyb> CPL?
21:24:49 <johnthetubaguy> (if its the person I think it is)
21:24:52 <mriedem> for the space program
21:24:59 <johnthetubaguy> CPL = cross project liason
21:25:05 <tonyb> Ah
21:25:08 <johnthetubaguy> (apparently, although with better spelling)
21:25:11 <bauzas> what's the goal of that ?
21:25:19 <dansmith> to liase!
21:25:22 <dansmith> between projects!
21:25:24 <johnthetubaguy> bauzas: so I have one goal, they have another
21:25:25 <dansmith> 3. Profit!
21:25:27 <mriedem> bauzas: to tell you to prioritize NFV + containers + neutron + ansible
21:25:43 <johnthetubaguy> I want them to give folks more permission to work on priorities
21:25:59 <anteaya> folks more permission?
21:26:02 <johnthetubaguy> I am working with them to convince your product managers that you should fix the things that need fixing
21:26:02 <anteaya> what folks?
21:26:09 <anteaya> ah thanks
21:26:20 <bauzas> anteaya: having people helping peons like us
21:26:26 <johnthetubaguy> I hope to keep them busy thinking about that
21:26:27 <anteaya> I'm for that
21:26:41 <johnthetubaguy> so they don't dream up any crazy feature requests, but lets see how that goes
21:26:58 <johnthetubaguy> anyways, its a thing, I am hoping they will actually be able to help
21:27:21 <anteaya> they already what to add state features to comply with legal requirements for getting user data
21:27:37 <anteaya> it is on the large deployments etherpad from the ops meetup
21:27:44 * dansmith feels like we're done here
21:27:56 <tonyb> Can I ask about Juno?
21:27:59 <johnthetubaguy> yeah, so if you are interested in all that
21:28:06 <johnthetubaguy> then get in touch
21:28:14 <tonyb> dansmith: you can ignore me if you like I wont mind
21:28:15 <johnthetubaguy> tonyb: in a troll way, or a real way?
21:28:24 <tonyb> johnthetubaguy: a real way sorry
21:28:24 * alaski wanders in late
21:28:41 <johnthetubaguy> tonyb: OK, 2 mins
21:28:49 <tonyb> so devstack in juno is broken mriedem and I have been trying to fix it
21:28:58 <mriedem> tonyb: the swiftclient 2.3.2 release will be out today
21:28:59 <tonyb> it's slow going and is gettign bigger
21:29:08 <mriedem> tonyb: stable maint isn't just a nova problem
21:29:08 <tonyb> mriedem: \o/
21:29:32 <tonyb> mriedem: Sure but how much effort do we want to go to giebn juno will EOL in nov?
21:29:32 <johnthetubaguy> do we not run stable branch tests reguarly?
21:29:45 <mriedem> stable branch is tested in a nightly periodic job
21:29:47 <johnthetubaguy> like more often than when we get the odd patch
21:29:55 <mriedem> results are posted to the stable ML
21:29:57 <johnthetubaguy> mriedem: ah, does anyone watch that?
21:29:59 <tonyb> mriedem: it's goign to touch lots of projects if things keep going the way they are ....
21:30:00 <mriedem> it's up to humans to read those
21:30:05 <johnthetubaguy> ah, right
21:30:12 <mriedem> i don't know exactly when stable/juno is EOL
21:30:24 <mriedem> we just recently EOL'ed stable/icehouse, so i wouldn't think juno is EOL until sometime in mitaka
21:30:31 <dansmith> can we just wait until it is EOL? :)
21:30:36 <tonyb> mriedem: (early) Nov from the wiki
21:30:49 <dansmith> I can totally make excuses for two months
21:30:54 <mriedem> right, is there a problem?
21:30:58 <mriedem> a *new* problem?
21:31:07 <mriedem> stable will be kind of a mess until stable/liberty due to the reqs caps issue
21:31:17 <mtreinish> dansmith: running out the clock on stable is my normal attitude
21:31:22 <dansmith> +1
21:31:22 <mriedem> until then it's biz as usual with a handful of people maintaining it
21:31:23 <mtreinish> but there is someone who always complains about it
21:31:30 <mriedem> like me :)
21:31:33 <mtreinish> yep
21:31:36 <tonyb> mriedem: Nothing new just the fallout from the swiftclient thing
21:31:47 <mriedem> yeah, so that's fine
21:31:48 <johnthetubaguy> mriedem: you actually do both though right? I am cool with that
21:31:55 <johnthetubaguy> OK, cool
21:31:58 <johnthetubaguy> so we are done I think
21:31:59 <tonyb> mriedem: but with L3 coming up dhellmann is asking to pause on the stable releases and EOL etc
21:32:01 <mriedem> tonyb: just go back through the stable rant history in the ML
21:32:02 <mriedem> :)
21:32:16 <mriedem> i haven't seen requests to EOL early
21:32:21 * med_ hears about a swiftclient stable thing and quakes in his boots.
21:32:35 <mriedem> med_: purely for our gate testing
21:32:47 <mtreinish> mriedem: that's just because I haven't had to look at it in a month or 2
21:32:57 <tonyb> med_: https://bugs.launchpad.net/python-swiftclient/+bug/1486576
21:32:58 <openstack> Launchpad bug 1486576 in python-swiftclient "version 2.3.1 on stable/juno has uncapped futures which breaks dep resolution with capped taskflow" [Undecided,In progress] - Assigned to Matt Riedemann (mriedem)
21:32:58 <mriedem> anyway, we can take this offline
21:32:59 <mriedem> plus i'm leaving
21:33:03 <johnthetubaguy> talking of clocks...
21:33:11 <johnthetubaguy> mriedem: leaving?
21:33:13 <med_> mriedem, tonyb tx.
21:33:16 <mriedem> like, work
21:33:17 <mriedem> i'm leaving work
21:33:23 <mriedem> :)
21:33:29 <mriedem> not nova
21:33:32 <mriedem> not pulling a jogo
21:33:36 * dansmith smashes the button on the wrap-it-up music player
21:33:36 <tonyb> lol
21:33:38 <johnthetubaguy> lol
21:33:44 <johnthetubaguy> thanks all
21:33:46 <johnthetubaguy> enjoy the music
21:33:49 <johnthetubaguy> #endmeeting