12:00:10 #startmeeting heat 12:00:11 Meeting started Wed Feb 4 12:00:10 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:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:00:15 The meeting name has been set to 'heat' 12:00:29 o/ 12:01:18 skraynev, just us two 12:01:24 :-/ 12:01:31 :-/ 12:01:33 agree 12:01:42 shardy? 12:02:03 well we are going to cut kilo-2 in the next 12hours 12:02:25 o/ 12:02:27 afaik, pas-ha ills 12:02:31 \o/ 12:02:53 #topic Review action items from last meeting 12:02:59 asalkeld, I thought, that ot will be at the end of week 12:03:07 nope 12:03:23 so stevebaker had an action, which he did 12:03:33 (stirred the pot) 12:03:48 #topic Adding items to the agenda 12:04:12 yes. 12:04:23 discussion looks interesting 12:04:33 zaneb, i guess not worth talking about that config option - not enough people 12:04:45 and only one real opposite opinion from zaneb 12:04:45 ok 12:05:14 I see lifeless trying to ping me overnight 12:05:37 may be he wanted to change you opinion :) 12:05:38 I think SpamapS has a point, but tbh I'm not persuaded yet 12:05:55 zaneb, if that config is super short termed - that's ok 12:06:07 (development tool really) 12:06:29 it really depends on how long people have to wait for a stable convergences 12:06:30 yeah, I think I didn't do a very good job in the initial version of the spec of describing the purpose of it 12:06:51 and if they have to choose 12:07:01 IMO, there are two cool benefits: 1. using existing Jenkins job and 2. using both code paths without restarting srvice 12:07:03 hopefully they won't have to 12:07:05 *service 12:07:21 I think the goal should be turn it on early in Lizard and make sure the bugs are ironed out before the end 12:07:25 skraynev, somewhat agree, but that's our problem 12:07:45 shouldn't push that to the user, unless they really need that 12:07:49 but I know TripleO are trunk-chasing and may legitimately worry about that 12:07:52 asalkeld: sure 12:08:01 but there's nothing particularly special about this feature 12:08:25 i am not keep on making fake api options tho' 12:08:32 you could make that complaint about any patch. "what if it has a bug?" 12:08:51 well, you try it and see if you want to assume the risk 12:09:06 and if you don't then maybe chasing trunk is not for you 12:09:26 or tripelo could contribute some scenario tests? 12:10:09 anyways, lets move on 12:10:17 #topic kilo-2 12:10:22 I'll try to chat to lifeless, maybe he has a specific scenario in mind that would be persuasive 12:10:32 #link https://launchpad.net/heat/+milestone/kilo-2 12:10:37 TZs are a pain, as usual :/ 12:11:00 you are on the other side of NZ 12:11:28 looks like i'll have to push decouple-nested and stack-breakpoints 12:11:37 zaneb: need create one big code place for Heat team :) 12:11:58 zaneb: on Hawaii, I suppose 12:12:05 lol 12:12:16 sounds good 12:12:25 I expect taht would be popular ;) 12:12:34 i have claim to have coded on a beach in hawaii 12:12:43 (big island) 12:12:47 very relaxing 12:12:52 ))) 12:13:14 just imagine: you lay on beach and discuss convergence... 12:13:21 ttx you about? 12:13:55 #link https://blueprints.launchpad.net/heat/+spec/decouple-nested 12:14:00 #link https://blueprints.launchpad.net/heat/+spec/stack-breakpoint 12:14:07 moving to k3 ^ 12:14:20 both should land in a week 12:14:31 but not soon enough 12:15:04 zaneb, skraynev https://review.openstack.org/#/c/147463/ 12:15:14 that's the last bug for k2 ^ 12:15:32 #topic open discussion 12:16:10 asalkeld: I wonder if in that case we should just raise UpdateReplace 12:16:25 rather than putting in special case logic 12:16:36 zaneb, either does the job 12:16:49 both would be "special" 12:17:02 fair point 12:17:08 I'll review after this 12:17:12 cool 12:17:30 zaneb, if you have an issue with it can you move the bug to k3 please 12:18:14 sure, I will either +2 or propose a new patch 12:18:25 (and get it reviewed) 12:18:39 cool, thx 12:18:57 after 10pm here so no real time to do that 12:19:15 np 12:19:20 I will chase it 12:20:18 zaneb, skraynev can i end early? - you have anything more? 12:20:29 nothing for me 12:20:39 I don't have anything else 12:20:48 gotu: anything to discuss? 12:20:49 ok later guys 12:21:06 gotu, ... 12:21:37 ananta = gotu sorry for confusion :) 12:21:49 ;) 12:21:52 Device problem 12:22:26 what's up gotu? 12:22:30 Nothing much from my side 12:22:39 zaneb: i have added work items in the comment https://review.openstack.org/#/c/152304/2/specs/kilo/convergence-message-bus.rst 12:23:12 I will be reviewing the specs by this week 12:23:30 zaneb, since when is a async request not rpc? 12:23:59 anyways, confused me more 12:24:15 asalkeld: sorry. I was trying to create less confusion ;) 12:24:36 in openstack land notifications == something specila 12:24:57 more generically i'd agree with you 12:25:00 KanagarajM: ok, I can add those into the spec for the next patch set. but I think we are agreed on them anyway 12:25:20 asalkeld: right, I was speaking generically :) 12:26:01 zaneb: thanks. 12:26:16 ok, does everyone that has a convergence spec commited to getting that code in promptly? 12:26:28 * asalkeld hopes so 12:26:28 asalkeld: FYI https://en.wikipedia.org/wiki/Remote_procedure_call 12:27:01 yeah, there are other people who have volunteered in the past 12:27:23 so if anybody has too much on their plate, we can get other people to pick it up 12:28:00 ok, let's move to #heat 12:28:05 #endmeeting