15:00:12 #startmeeting heat 15:00:12 Meeting started Wed Jan 4 15:00:12 2017 UTC and is due to finish in 60 minutes. The chair is ramishra. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:16 The meeting name has been set to 'heat' 15:00:21 #topic roll call 15:00:30 Heya 15:00:47 O/ 15:00:49 happy new year all 15:01:01 happy new year! 15:01:02 happy new year! 15:01:47 happy new year! 15:02:52 #topic adding items to agenda 15:02:59 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-01-04_1500_UTC.29 15:03:29 I've added a few topics, anything else we would like to discuss? 15:03:58 ramishra, Adding one about heat-agents 15:04:16 therve: yep 15:05:05 #topic gate failures 15:05:24 So the new year has not been good;) 15:05:40 failure rate is very high. 15:05:59 We had a barbican issue? 15:06:05 Then that cfn weird stuff 15:06:12 therve: yeah I fixed that 15:06:16 Anything else identified? 15:06:30 I noticed that we get slow nodes for the jobs. 15:06:45 and devstack build takes 30-40 mins 15:06:55 from the total 80 mins for the job. 15:07:35 I propose this https://review.openstack.org/#/c/414365/ 15:07:51 comment in that patch has the logstash query too. 15:08:49 To me it's mostly infra issue, tests with waitconditions fail mostly. 15:09:49 That sounds like a good workaround 15:10:04 One more issue I noticed today, raised a bug 1653990 15:10:05 bug 1653990 in heat "test_asg_scale_up_max_size fails with KeyError" [Undecided,New] https://launchpad.net/bugs/1653990 15:11:50 weird kind of failure. 15:12:30 Some kind of race with metadata maybe? 15:13:33 * zaneb groans 15:13:38 ;) 15:13:41 therve: it seems to me like the resource is in db but not in template. 15:13:55 not looked in detail though. 15:15:06 Any help to fix these is appreciated:) 15:16:24 ramishra, Ah probably just some transaction boundaries not handled properly 15:17:01 therve: yeah, possibly had never seen this before. 15:17:15 ok, lets move on 15:17:47 else we would only be discussing gate issues;) 15:17:57 #topic Status of Blueprints 15:18:29 #link https://launchpad.net/heat/+milestone/ocata-3 15:19:07 can we identify the bps we plan to land in ocata? We don't have much time. 15:19:27 None of them seem super important to me. 15:20:23 https://blueprints.launchpad.net/heat/+spec/custom-update-replace-for-failed-resources hope this can be landed in ocata 15:20:44 acturally it's simple 15:21:14 tiantian: ok 15:21:17 one or two patches have been merged already 15:21:28 thank you :) 15:22:08 I think we should define the Priority of undefined one and I feel free to land till next release if no high Priority there 15:22:23 it seems we would not be able to do much translation stuff. 15:22:28 Not seen any patches. 15:23:41 ok, I'll talk to the respective owners and change the target release accoridingly. 15:24:39 moving on... 15:24:46 #topic User survey question 15:25:00 #link http://lists.openstack.org/pipermail/openstack-dev/2017-January/109511.html 15:25:29 Yeah that's kind of tough 15:25:41 can we've some good adoption questions? I've not seen many replies to my mail;) 15:25:58 would be interesting to know if people are enabling convergence (phase 1) 15:26:20 although that'd *more* interesting in 6 months or a year from now 15:27:03 so I'm inclined to leave it out for now, because I can't think of anything we'd do differently at _this_ point based on the results 15:27:28 ramishra: how about put throughs here https://etherpad.openstack.org/p/ocata-heat-user-survey 15:27:40 ricolin: sure 15:27:56 actually we need one good/relevant question:) 15:28:31 #link https://etherpad.openstack.org/p/ocata-heat-user-survey 15:28:38 how often do you purge your stacks, with what parameters? :) 15:29:29 How do we decide the *one* question? 15:30:56 some projects are using voting/scoring system etc. We should not make it complicated;) 15:31:25 cwolferh: how many operators would even *know* the answer to that? ;) 15:32:19 ramishra, Some kind of rough estimate of stack size would be interesting 15:32:22 stack lifetime, too 15:33:48 therve: yeah 15:34:37 Someone would like to help finalize the question? we've few more days to decide. 15:35:30 ramishra: I can help:) 15:35:53 ricolin: great:) 15:36:27 zaneb, i'll just go with "not enough" :) 15:37:50 moving on.. 15:38:03 Let's put some random questions list in etherpad, I will help to finalize it (probility by voting) 15:38:03 #topic heat-agents repository 15:38:04 cwolferh: in an ideal world installers just do the Right Thing my default and 90% of operators never have to think about it. (I don't think we live in that world yet.) 15:38:25 s/my/by/ 15:38:38 therve: your topic:) 15:38:45 Yes! 15:38:54 So I started https://review.openstack.org/416244 15:39:08 To create the new repository out of heat-templates 15:39:36 https://github.com/therve/heat-agents is the source, I used some git filter-branch invocation to get the content 15:39:47 Plus one commit to fix the folder moves 15:40:14 Depending on when it's created I may have to catch up some commits manually later on 15:40:24 Reviewing that repo can be helpful 15:40:36 I hope we'll get infra feedback quickly afterwards 15:40:46 #link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107306.html 15:40:57 that's the ML thread on it. 15:40:58 It'd be nice if someone contacted the rdo package maintainer 15:41:23 good start:) 15:42:12 That's pretty much it, unless someone has questions :) 15:43:21 therve: are we going to able to keep the history after the move? 15:43:39 ramishra, Yeah that's the point of that github repo 15:43:49 ok great:) 15:44:06 therve: did I just hear you volunteer to be the rdo package maintainer? 15:44:21 ramishra, Actually, if you know how to improve the history that'd be great actually 15:44:21 :) 15:44:33 It contains empty files changes currently 15:44:47 zaneb, Seems like twisting my word quite heavily :) 15:45:58 therve: is it working? ;) 15:46:07 I don't think so 15:46:28 dang 15:46:43 therve: will `upstream: ` change after? 15:47:02 therve: I think stevebaker is the current maintainer for that 15:47:03 ricolin, It doesn't need to, from what I understand 15:47:17 I think someone is already maintaining the rdo packages(python-heat-agent*) as per stevebaker in that ML thread 15:47:25 ricolin, It's only used for initial import if we don't set that other keyword 15:47:46 therve: Okey, thx 15:47:55 hguemar and apevec seem to make the uploads 15:49:47 therve: anything else you want to add? 15:49:53 Nope 15:50:18 #topic open discussion 15:51:17 Should we try to write down some PTG schedule? 15:51:42 therve: yeah, I forgot that completely. Thanks for reminding. 15:52:54 Would be it design session like the earlier summits or some concrete use cases that we can work on there? 15:54:18 Will be great to strong cross project discussion 15:54:23 I think some teams are doing both. 15:55:04 Will create an etherpad and let's capture ideas first. 15:55:09 therve: if you run "git rebase 40e6c0874dc3877666a92c706079e7b74cc67601" on the heat-agents repo it'll delete all the merge commits 15:55:17 * zaneb discovered that just now 15:55:36 ramishra, I was thinking a bit of both? I'd like to do some real implementation if we can 15:55:45 zaneb, Does that remove commits with no files? 15:56:05 * zaneb looks 15:57:34 zaneb, Looks like a winner, thanks :) 15:57:35 therve: gonna say yes. I don't see any commits left with no files, except the first one, 40e6c0874dc3877666a92c706079e7b74cc67601, "Added .gitreview" 15:57:47 therve: speaking of which, we need to add a .gitreview :) 15:58:02 zaneb, It's there? 15:58:43 therve: oh, you added it in the last commit. great :) 15:59:07 there's probably a way to delete that first empty commit, but not sure what it is 15:59:28 ramishra, end meeting! 15:59:46 yep 15:59:49 btw +1 on "a bit of both" for the PTG 15:59:52 zaneb, Thanks that look much nicer 16:00:10 thanks all for joining 16:00:15 #endmeeting heat