15:00:07 <ramishra> #startmeeting heat
15:00:07 <openstack> Meeting started Wed Dec  7 15:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is ramishra. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:12 <openstack> The meeting name has been set to 'heat'
15:00:15 <ramishra> #topic roll call
15:00:21 <zaneb> howdy
15:00:24 <therve> Yop
15:01:14 <cwolferh> o/
15:01:31 <ramishra> hey guys, thanks for joining.
15:02:46 <ramishra> Not sure if we have any more joining.
15:03:35 <ramishra> ok, let's move on:)
15:03:56 <ramishra> #topic adding items to agenda
15:04:07 <ramishra> #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-12-37_1500_UTC.29
15:05:00 <ramishra> #topic ocata-2 status
15:05:20 <ramishra> #link https://launchpad.net/heat/+milestone/ocata-2
15:05:58 <ramishra> milestone tagging is next week, too soon;)
15:06:38 <ramishra> I critical and 2 high priority bugs.
15:07:31 <zaneb> wow, this cycle is really going quick
15:07:37 <therve> ramishra, https://bugs.launchpad.net/heat/+bug/1578854 is still relevant?
15:07:37 <openstack> Launchpad bug 1578854 in heat "resource-list makes SQL calls for every resource which is a nested stack" [High,In progress] - Assigned to Steve Baker (steve-stevebaker)
15:07:55 <therve> There is no opened patches against it, I think we can close it
15:08:28 <ramishra> therve: yeah, I did not check that.
15:08:55 <ramishra> cwolferh: can we land all patches for bug 1524013?
15:08:55 <openstack> bug 1524013 in heat "Arbitrarily-large resource properties should be allowed in events" [Medium,In progress] https://launchpad.net/bugs/1524013 - Assigned to Crag Wolfe (cwolfe)
15:09:52 <cwolferh> ramishra, the patches should be fine. the only thing i'm uncertain of is this is not writing data to the old place (which would be easy to change)
15:10:20 <cwolferh> for the sake of a rolling upgrade
15:10:37 <ramishra> And there are some bugs, which are assigned to some but no patches.
15:10:46 <ramishra> I think we should reassign and fix them.
15:11:28 <ramishra> cwolferh: I'm wondering if we can get them reviewed in time for o-2.
15:11:46 <therve> I don't see anything critical though
15:12:41 <ramishra> ok, we can move them to o-3;)
15:12:50 <cwolferh> ramishra, also, i reordered them yesterday, so 2 more refactors before real changes
15:13:38 <therve> cwolferh, The first one in the queue is rough to review
15:13:46 <zaneb> time for me to review that series I guess
15:15:27 <ramishra> I think we'll try and review as many as we can:)
15:16:16 <therve> Yeah some patches are really stalled in there :/
15:16:37 <ramishra> I wanted to discuss about the rolling upgrade thing, that's the next topic.
15:16:42 <ramishra> should we move on?
15:16:46 <therve> Sure
15:16:56 <ramishra> #topic rolling upgrade
15:17:06 <ramishra> #link https://review.openstack.org/#/c/407989/
15:17:23 <ramishra> I pushed this draft spec today. more to discuss about it,
15:18:15 <ramishra> I'm not sure if anyone has seen the glance specs and reviews on this.
15:18:28 <ramishra> #link https://review.openstack.org/#/c/331740/
15:18:53 <ramishra> they have also recorded a good demo. #link https://www.youtube.com/watch?v=Z4iwJRlPqOw
15:19:00 <therve> I like that plan, but I've never deployed heat in production, so...
15:19:13 <ramishra> That's using triggers
15:19:19 <therve> It'd be nice to have Rackspace guys feedback on it
15:20:08 <ramishra> therve: yeah, I will add all cores to the review.
15:20:31 <ramishra> also any feed back on the glance approach for db migrations would also be good too.
15:21:04 <ramishra> db upgrades
15:21:58 <therve> I'd like to avoid triggers, but if it comes down to that, so be it
15:22:36 <ramishra> We will wait and see how it works for glance, before going that way;)
15:23:56 <zaneb> triggers make me very nervous
15:24:21 <therve> zaneb, +1000
15:24:30 <cwolferh> the only justification for that is if writing to the old and new place results in too much duplication
15:24:46 <cwolferh> like maybe the case with resource properties data
15:25:14 <cwolferh> though i would also prefer to avoid triggers
15:25:27 <ramishra> cwolferh: my only concern is over a period of time the db layer code may be unreadable if we start writing to both old and new location.
15:25:47 <ramishra> I don't like triggers though.
15:25:53 <zaneb> can we just migrate the properties data now and try not to screw up anything that big again? ;)
15:26:16 <cwolferh> sounds good to me :-)
15:27:05 <zaneb> ramishra: I was kinda hoping ovo would isolate the compat code so it didn't become unmanageable. it hasn't really turned out that way though :/
15:27:44 <cwolferh> ramishra, i don't think it is too terrible (we only read from one place but potentially write to 2), but i see your point
15:28:44 <ramishra> yeah, we can probably manage the db changes carefully, to avoid triggers.
15:29:16 <ramishra> Anyway, that's not in the plan for this cycle, triggers or not;)
15:30:04 <ramishra> If we can get the grenade tests setup, then we can probably ask for the tag:)
15:31:16 <ramishra> We don't have more topic to discuss today.
15:31:48 <ramishra> I had this topic for v2 api, we discussed it a little last meeting.
15:32:08 <ramishra> #topic Heat API V2
15:32:51 <ramishra> zaneb, cwolferh, you guys may put your opinion on this.
15:33:19 <ramishra> We thought that we don't have enough bandwidth to work on this in the last meeting.
15:33:29 <ramishra> and it's not super important.
15:33:30 * zaneb probably didn't read the minutes from last week
15:33:59 <ramishra> I think Qiming had some concerns with the v1 api
15:34:04 <zaneb> there's definitely a long list of ugly stuff we'd like to fix
15:34:15 <ramishra> though he does not seem to around.
15:34:33 <zaneb> otoh, moving to a new API version is painful, as proven by... just about every other OpenStack project at this point
15:34:56 <cwolferh> i also need to read back on that, v2 would be a nice clean slate... sounds like it ought to be uncontroversial :-)
15:35:10 <ramishra> zaneb: Are the current issues listed somewhere?
15:35:18 <zaneb> yes
15:35:23 <zaneb> definitely
15:35:30 <zaneb> somewhere.
15:35:36 <ramishra> :)
15:36:42 <zaneb> https://wiki.openstack.org/wiki/Heat/Blueprints/V2API
15:37:19 <zaneb> #link https://wiki.openstack.org/wiki/Heat/Blueprints/V2API
15:38:08 <ramishra> Ah, I think some guys are interested to start working on it.
15:38:36 <ramishra> Some of them are new contributors, may be someone can help create a spec and guide them?
15:38:52 <therve> I wished they worked on performance instead, but whatever :)
15:40:30 <ramishra> yeah, performance stuff is not for everyone;) limited experts:)
15:41:13 <ramishra> Anyway, I don't think there can be much done in this cycle.
15:41:59 <ramishra> ok, let's move on.
15:42:10 <ramishra> #topic open discussion
15:42:19 <ramishra> Anything else we want to discuss?
15:42:53 <cwolferh> already discussed the resource properties patches, if people review that that would be awesome :-)
15:43:12 <therve> Yeah review review reviews
15:43:28 <cwolferh> :-)
15:44:34 <ramishra> I also wanted some of the gabbi api test patches to be reviewed too.
15:45:11 <ramishra> ok, I think we are done. should we move back to heat?
15:45:17 <zaneb> reviews on https://review.openstack.org/#/c/395124/ would be great
15:45:21 <therve> zaneb, Should I create a spec for CustomResource?
15:45:26 <therve> Or whatever we called it
15:45:33 <zaneb> therve: yes, by all means
15:46:18 <therve> zaneb, That somehow brings back the discussion about Mistral::WorkflowExecution
15:47:22 <zaneb> I've thought a bit about Mistral::WorkflowExecution
15:47:38 <zaneb> I think I would be ok with it if it worked a bit like SoftwareComponent
15:48:06 <zaneb> i.e. you can specify an action for create, update, delete, and there's a way to trigger replacement
15:48:43 <zaneb> like CustomResource that doesn't mean people will use it properly. but at least they have a chance
15:48:50 * therve nods
15:50:04 <ramishra> therve, zaneb: I had registered this bp https://blueprints.launchpad.net/heat/+spec/implement-custom-resource
15:50:09 <ramishra> long time back
15:50:35 <ramishra> Somewhat inline with the AWS implementation.
15:50:39 <therve> Indeed :)
15:50:55 <therve> Replace marconi by zaqar and that's the idea
15:51:11 <zaneb> lol, that *is* a long time back :D
15:52:18 <ramishra> yeah, that time it was outrightly rejected;)
15:53:48 <zaneb> was it? by whom?
15:54:27 <ramishra> zaneb: I don't remember exactly. But, in some discussions I found not buyers for it.
15:54:36 <zaneb> tbh it was probably too early to be really useful back then. now all the other pieces are in place
15:54:36 <ramishra> no buyers
15:54:48 <ramishra> yeah, I agree
15:55:41 <therve> http://lists.openstack.org/pipermail/openstack-dev/2014-April/032609.html :)
15:56:12 <ramishra> therve: wow:)
15:57:21 <zaneb> happy to see that it turns out I have been consistent :)
15:58:48 <zaneb> oh, no I haven't
15:59:07 <zaneb> I said user hooks ought to be enough for anybody
15:59:27 <zaneb> they aren't
16:00:46 <zaneb> ramishra: time's up
16:00:53 <ramishra> I'm happy that we're back to it:) Though I knew very little heat that time to participate in a discussion.
16:00:56 <ramishra> yep
16:01:03 <ramishra> thanks all for joining.
16:01:09 <ramishra> #endmeeting heat