12:00:34 <asalkeld> #startmeeting heat
12:00:35 <openstack> Meeting started Wed Mar 18 12:00:34 2015 UTC and is due to finish in 60 minutes.  The chair is asalkeld. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:00:39 <openstack> The meeting name has been set to 'heat'
12:00:45 <asalkeld> ello
12:00:48 <shardy> o/
12:00:52 <tspatzier> Hi
12:01:05 <asalkeld> #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda
12:01:23 <asalkeld> #topic Adding items to the agenda
12:01:28 <zaneb> o/
12:01:30 <ryansb> \o
12:02:02 <asalkeld> zaneb: you didn't get much sleep?
12:02:09 <skraynev> o/
12:02:50 <asalkeld> we can also add topics at the end
12:03:13 <asalkeld> #topic reviews to do before FF
12:03:20 <asalkeld> #link https://etherpad.openstack.org/p/heat-kilo-releasenotes
12:03:30 <zaneb> asalkeld: worse than that, I forgot daylight savings started so I was up for this meeting an hour ago
12:03:44 <ryansb> at least I'm not the only one
12:03:45 <asalkeld> doh
12:03:49 <ryansb> dst is the worst
12:04:14 <zaneb> ryansb: I dunno, those 7am meetings were starting to grate
12:04:53 <asalkeld> i am struggling to get decouple-nested in as it just seems to tip the scales timewise
12:05:05 <asalkeld> (gate just times out)
12:05:11 <asalkeld> see how it goes
12:05:12 <shardy> asalkeld: should we have a section for deprecations?
12:05:28 <asalkeld> shardy: sure
12:05:37 <shardy> I think we've deprecated a few things, but I can't remember exactly what (CWLiteAlarm, HARestarter?)
12:05:45 <asalkeld> shardy: i copied in a template
12:06:03 <shardy> it'd be good to communicate eventual removal of all the historical *watch stuff
12:06:10 <skraynev> shardy: +1 for deprecation section
12:06:24 <asalkeld> shardy: we should be able to get some output from our support status
12:06:37 <asalkeld> if someone wants to help with that...
12:06:47 <asalkeld> i am not sure how to extract that
12:06:56 <skraynev> asalkeld:may it be done as a part of deprecation bp?
12:07:19 <asalkeld> skraynev: yeah - but that's a bit late for this time?
12:07:34 <zaneb> hopefully it shows up in the docs and you can just Ctrl-F for it?
12:07:50 <zaneb> otherwise we need to fix the docs generation ;)
12:08:19 <skraynev> zaneb, asalkeld: we may use already presented patch (on review) and just print in file all deprecation staff
12:08:31 <asalkeld> zaneb: yeah, one point is who is the consumer of the release notes
12:08:35 <skraynev> zaneb: ctrl+f works too
12:08:45 <asalkeld> operator or user
12:09:10 <asalkeld> if it's operator, then we don't really need to put template stuff in there
12:09:19 <asalkeld> (i would have thought)
12:09:33 <skraynev> asalkeld: I meant this one https://review.openstack.org/#/c/164677/
12:09:45 <ryansb> I think (at least some) users would once operators actually do the upgrade
12:09:46 <skraynev> it will show what you want with minimal changes
12:09:50 <skraynev> I suppose so
12:10:08 <asalkeld> ok skraynev
12:11:18 <asalkeld> anyways any help on the release notes is appreciated
12:11:37 <skraynev> asalkeld: any estimate for it?
12:11:49 <asalkeld> what do you mean?
12:12:01 <asalkeld> estimate on what?
12:12:04 <skraynev> is it possible to do during this week? or we should finish this list today?
12:12:17 <asalkeld> skraynev: no rush
12:12:27 <shardy> well it just needs to be done before the release presumably
12:12:35 <skraynev> oh. ok
12:12:45 <asalkeld> shardy: yeah rc1?
12:13:10 <skraynev> got it ;) just thought, that it should be "already " done
12:13:31 <shardy> asalkeld: Yeah, I guess having them somewhat finished by the first RC would be good
12:13:51 <asalkeld> so my topic and link got mixed up
12:14:00 <asalkeld> we seem to have done release notes
12:14:11 <asalkeld> now lets do FF
12:14:14 <asalkeld> #topic Last day before FF (highlight what needs to be done)
12:14:33 <asalkeld> #link https://etherpad.openstack.org/p/heat-kilo-3-reviews
12:14:52 <asalkeld> any last desperate review requests?
12:15:12 <asalkeld> or blueprints that people need help with?
12:15:21 <shardy> asalkeld: FYI I'm still working on the breakpo^W hooks ones
12:15:28 <asalkeld> ok
12:15:40 <shardy> it ended up needing INIT_COMPLETE persisted, fixing bug #1319813
12:15:41 <openstack> bug 1319813 in heat "no event recorded for INIT_* resources" [Medium,In progress] https://launchpad.net/bugs/1319813 - Assigned to Steven Hardy (shardy)
12:15:50 <shardy> that is proving harder than expected
12:16:04 <asalkeld> ok
12:16:14 <asalkeld> there is always FF exceptions
12:16:22 <shardy> we may end up needing a FFE, but the feature patch is well reviewed, so I'll keep pushing on it
12:16:30 <asalkeld> not sure how much time that buys you tho'
12:16:30 <inc0_> shardy, anything I can help you with?
12:17:14 <asalkeld> well i have a meeting with ttx in one day, to finalize this stuff
12:17:26 <asalkeld> if we need a FFE, let me know
12:17:28 <zaneb> shardy: yeah, I'm available to help on that if you need
12:17:29 <shardy> inc0_: I'm not sure tbh, I'm kinda down the rabbit hole trying to fix problems atm, more eyes may help if I don't get it sorted soon
12:17:52 <inc0_> shardy, let me know
12:17:58 <shardy> zaneb, inc0: thanks - I may ping you later today
12:17:59 <zaneb> shardy: is it actually a problem, or do we just need to change the test?
12:18:22 <shardy> zaneb: it's actually a problem, because the point in time when Resource._store() gets called is significant
12:18:36 <shardy> because that's the only point when we resolve and store resource metadata
12:19:06 <asalkeld> shardy: maybe we need a light weight version of _store
12:19:24 <asalkeld> that doesn't do and metadata
12:19:34 <asalkeld> that doesn't do any metadata resolving
12:19:51 <shardy> asalkeld: Actually I've gone the other way, I'm re-combined store into _store_or_update, so we can make the state-machine which exists on storing clearer
12:20:18 <shardy> then we just add the metadata when the update going into CREATE_IN_PROGRESS happens
12:20:26 <shardy> but that's not the only problem unfortunately
12:20:56 <shardy> storing pre-create means anywhere doing if self.id assertions behaves differently
12:21:19 <asalkeld> oo, that sounds "fun"
12:21:22 <shardy> and InstanceGroups break in a weird way, the group member resources aren't stored at all
12:21:22 <zaneb> yikes
12:21:46 <shardy> basically I've been playing whack-a-mole with these three issues and breaking functional tests for the last day or so :\
12:21:48 <zaneb> on the bright side, we need this for convergence
12:22:00 <zaneb> so probably good to get it sorted now I guess
12:22:06 <shardy> Yeah, I figured this needs to be done so I'll stick with it
12:22:22 <shardy> more eyes may help, I'll beat the patches I have into shape first then we can discuss later
12:22:24 <asalkeld> if someone is looking for some work: https://bugs.launchpad.net/heat/+bug/1433555
12:22:25 <openstack> Launchpad bug 1433555 in heat "functional tests are taking too long and cause false failures" [High,Triaged]
12:22:53 <asalkeld> ok moving on
12:22:57 <asalkeld> #topic Any urgent bugs needed before rc1
12:23:19 <asalkeld> if know of any important bugs please target to rc1
12:23:27 <asalkeld> (new'ish milestone)
12:23:42 <skraynev> asalkeld: can I take this one bug for our team?
12:23:43 <asalkeld> #link https://launchpad.net/heat/+milestone/kilo-rc1
12:23:54 <asalkeld> skraynev: ok
12:24:30 <asalkeld> #topic open discussion
12:24:40 <asalkeld> <free for all>
12:25:18 <asalkeld> #link https://wiki.openstack.org/wiki/Kilo_Release_Schedule
12:25:25 <asalkeld> April 9 is rc1
12:25:43 <asalkeld> afaik
12:26:56 <asalkeld> we can end early and go work/bed as needed?
12:27:14 <asalkeld> bed time for me:-O
12:27:34 <asalkeld> last chance ...
12:27:37 <pas-ha> :) sure, I've nothing urgent to discuss
12:27:46 <asalkeld> #endmeeting