20:04:35 #startmeeting heat 20:04:35 great 20:04:35 why do it happen? 20:04:35 ok, well let 20:04:35 ok, well let plough on 20:04:35 anyone around? 20:04:36 hi 20:04:36 hi 20:04:36 o/ 20:04:36 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda 20:04:36 not much on there today 20:04:36 hi all 20:04:36 o/ 20:04:36 #topic Adding items to the agenda 20:04:41 Meeting started Wed Apr 8 20:04:34 2015 UTC and is due to finish in 60 minutes. The chair is asalkeld. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:04:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:04:44 The meeting name has been set to 'heat' 20:04:48 Meeting ended Wed Apr 8 20:04:35 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 20:04:49 Minutes: http://eavesdrop.openstack.org/meetings/heat/2015/heat.2015-04-08-20.04.html 20:04:51 Minutes (text): http://eavesdrop.openstack.org/meetings/heat/2015/heat.2015-04-08-20.04.txt 20:04:52 Log: http://eavesdrop.openstack.org/meetings/heat/2015/heat.2015-04-08-20.04.log.html 20:04:54 Meeting started Wed Apr 8 20:04:35 2015 UTC and is due to finish in 60 minutes. The chair is asalkeld. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:04:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:04:57 The meeting name has been set to 'heat' 20:05:00 he awake! 20:05:06 woohoo, the bot is back ;-) 20:05:09 dang, that's slow 20:05:14 \o 20:05:26 hi stevebaker 20:05:37 #topic Any critical bugs (rc2 potential) 20:05:38 Hi 20:05:41 stevebaker: makes bot alive!!! 20:05:43 :) 20:05:52 you're welcome 20:06:21 #link https://bugs.launchpad.net/heat/+bugs?field.tag=kilo-rc-potential 20:07:00 if there are any critical bugs we need to backport them 20:07:08 (to kilo) 20:07:21 i don't see anything yet 20:07:24 asalkeld: can we just backport anything which is Fix Committed? 20:07:39 shrug, I guess 20:09:24 I just joined the meeting... this bug kind of affect heat's ability to autoscale.. what do you guys think? https://bugs.launchpad.net/ceilometer/+bug/1421584 20:09:26 Launchpad bug 1421584 in Ceilometer "cpu_util volume won't report right for cpu over commit case" [Medium,Triaged] - Assigned to Ilya Tyaptin (ityaptin) 20:09:52 hi all 20:09:58 hi prazumovsky 20:10:02 looking msly 20:10:55 so are ceilometer going to fix that? 20:12:34 shardy: have you any important bugs to fix from tripelO? 20:13:09 asalkeld: Nothing specific to heat atm AFAIK 20:13:13 ok 20:13:22 asalkeld: I'm not sure if anyone is assigned or going to implement a new meter in ceilometer, but heat currently uses cpu_util from ceilometer to do its autoscaling and it's not going to work 20:13:55 msly: it sounds like it is not a heat bug though, we can only consume the metrics we're given 20:14:30 #topic open discussion 20:14:55 should we have a meeting next week? asalkeld is away and I'll be asleep 20:15:17 stevebaker: you could do it at this time? 20:15:32 or ask someone in the EU to do it? 20:15:48 (or cancel) 20:15:54 asalkeld: I can do it if you decide not to cancel 20:16:03 ok thanks shardy 20:16:19 happy to skip a week tho, if there's nothing on the agenda 20:16:39 I think that pas-ha and me be here too :) 20:17:05 so there are 3 cores in meeting ;) 20:17:08 nice, we do have a quiet time for a week or 2 20:17:21 until summit planning kicks in 20:17:35 #link https://etherpad.openstack.org/p/heat-reviews 20:17:48 mostly handy links ^ 20:18:29 and zaneb 20:18:41 speaking of reviews, stevebaker you had soms suggestions re review prioritization, care to share any more details on how we might go about that? 20:18:43 ohai 20:19:14 zaneb: aloha 20:19:56 zaneb: you see that discussion about messaging the user on the ml? 20:19:58 swift has a version of https://etherpad.openstack.org/p/heat-reviews which is manually curated, so reviewers have a priority of what to review next. I wonder if we should try something like that, as long as someone volunteers to curate (like the PTL) 20:20:05 asalkeld: yes, I did 20:20:27 everything via notifications 20:20:30 :-O 20:20:48 stevebaker: Ok, yeah an etherpad with priorities per milestone would certainly be a good start 20:20:48 that's not a terrible idea 20:21:06 if it means there's one central implementation of how those get exposed to the user 20:21:21 stevebaker: or something semi automatic 20:21:24 it would help getting the convergence changes landing in the best order 20:21:33 we do have priorities in the bug 20:21:41 stevebaker: +1 20:21:50 or tags 20:22:08 manual list sounds tedious 20:22:26 (to keep up to date) 20:23:18 should we consider some way of scrubbing (via WIP?) old inactive reviews? 20:23:24 asalkeld: if it is too automatic then it might end up being just another gerrit dashboard with uncoordinated reviews 20:23:37 I for one still thing it's a shame we abandoned auto-abandon.. 20:23:49 i like auto abandon 20:24:08 else you get lots of old cruft 20:24:10 someone could just go through and manual-abandon with a nice message 20:24:46 that too 20:25:07 just found out this morning, heat is no longer a default enabled service on devstack :( https://review.openstack.org/#/c/169709/ 20:25:11 also maybe auto-abandon is a per-project decision. I'm not sure 20:25:29 msly: that is mostly for the gate 20:25:50 msly: that's the "big tent" for you :\ 20:25:58 so tempest doesn't install heat when it doesn't need it 20:26:09 tho' not sure that saves much time 20:26:40 the commit message says its to save memory, seems reasonable. 20:26:56 stevebaker: start testing out the manual review board if you want 20:27:01 asalkeld: but I was surprised too (spend half day by thinking where I am wrong with devstack) 20:27:03 stevebaker: yeah, to be fair, heat is a pretty bad memory hog under some circumstances 20:27:18 asalkeld: the gate has its own service enablement, so that is unrelated 20:27:44 seems like if the problem is in the gate it should be fixed in the gate, not for everybody in devstack 20:28:02 its nothing to do with the gate 20:28:15 changing defaults is always fun for users 20:29:09 well i have nothing else, we can end early if you guys want 20:29:10 it would be aimed for people developing locally in a vm 20:29:52 stevebaker: do you mean heat standalone? 20:30:13 skraynev_: just peolpe that don't want heat 20:30:19 has anybody met failed to start heat-api on stack.sh run? 20:30:21 skraynev: he means anyone who runs devstack in a VM 20:30:26 skraynev_: no, selecting a default service list which works in 4G of RAM 20:31:23 stevebaker, yeah, on 4G RAM heat + Neutron + swift + Ceilo + others is already sloppy 20:32:16 any new topics ... 20:32:21 stevebaker: got it. agree default which eat all your resource is terrible 20:32:30 *resources 20:32:40 default services doesn't even include swift. It sucks that we're not default anymore but this seems reasonable 20:32:55 pas-ha: and do not forget tempest ;) and sahara 20:33:27 #endmeeting