08:00:30 #startmeeting heat 08:00:31 Meeting started Wed Oct 5 08:00:30 2016 UTC and is due to finish in 60 minutes. The chair is ramishra. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:34 The meeting name has been set to 'heat' 08:00:44 #topic roll call 08:00:49 o/ 08:01:08 o/ 08:01:22 hi! 08:01:37 hai 08:01:57 0/ 08:02:24 Heya 08:03:09 #topic adding items to agenda 08:03:19 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-10-05_0800_UTC.29 08:03:44 memory usage 08:05:10 stevebaker: added that one 08:05:19 so we have just 2 topics 08:05:40 #topic heat summit sessions 08:05:56 #link https://etherpad.openstack.org/p/ocata-heat-sessions 08:06:10 should we wait for more time for any more proposals 08:06:15 or finalize them 08:06:36 I've updated the etherpad with what we had in that. 08:06:57 stevebaker: any topics from you on the client stuff? 08:08:34 therve: I've added a specific session on large stacks to cater to the magnum team. 08:08:39 ramishra, +1 08:08:53 ramishra: could we finalise next week? I'm on leave until tomorrow 08:08:54 We'll talk tripleo as well presumably 08:09:09 stevebaker: sure 08:09:57 I've added a topic for validation improvements again, we can discuss about translation in that, if we want 08:10:21 Possibly, yeah. It may be worth another session though 08:10:27 We're missing one, too :) 08:10:56 though prazumovsky would not be around to participate. 08:11:32 It still worth having the discussion 08:12:27 we should start working on the validation improvements this cycle;) 08:12:57 therve: yeah I'll add that, if there is nothing form stevebaker, else we can club it with validation stuff. 08:13:04 OK 08:13:57 ok should we move on now? 08:14:11 #topic memory usage 08:14:59 I've been out of the loop for the past 10 days, but things are happening here https://bugs.launchpad.net/heat/+bug/1626675 08:15:01 Launchpad bug 1626675 in heat "Further memory usage issues with big stacks" [Critical,In progress] - Assigned to Zane Bitter (zaneb) 08:15:15 many of us are working on it. mostly therve and zaneb. therve, probably therve you can provide an update? 08:15:29 Sure 08:15:55 I think we spent a good chunk of time looking for a specific issue 08:16:00 But there doesn't seem to be one 08:16:10 I wonder if we could use __slots__ elsewhere, like Stack https://review.openstack.org/#/c/382068/ 08:16:10 Mostly a bunch of things adding up 08:16:34 slots may improve a bit, but it's minor 08:16:47 https://review.openstack.org/381588 is the latest that shaved about 10% for me 08:16:54 https://review.openstack.org/380542 is a good one too 08:17:43 I'll check https://review.openstack.org/382038 after the meeting 08:17:49 zaneb has few patches too 08:18:12 shardy wanted to do a server-less tripleo deployment 08:18:27 That would help testing a lot, as it takes about 30mins for me to check a patch 08:18:38 If we don't have servers that could be much faster 08:18:43 that would be great. 08:18:51 We need something that can fake a server, and signal data back 08:19:54 therve: a dedicated integration test against a fake nova driver methings 08:20:00 methinks 08:20:03 stevebaker, That's not enough 08:20:12 fake nova driver won't signal back 08:20:46 yes, the integration test signals back 08:21:38 Right, but I don't want integration test 08:21:52 I want to use "openstack overcloud deploy" 08:22:19 ah, and a standalone thing which signals 08:23:57 Yeah I don't really know yet 08:24:22 Something like TestResource but with the ability to signal data. Specified in a file maybe? 08:24:28 yeah, it could even be interactive 08:24:30 That could be a memory hit though 08:24:36 i'll have a think 08:25:37 so, we don't yet know how the memory consumption suddenly increased(in newton) for Tripleo as reported in the bug, right? 08:25:55 ramishra, I think there is not *a* reason 08:26:05 There are plenty of small reasons :) 08:26:18 One being simply that tripleo does more things 08:26:18 therve: all in newton:) 08:26:36 ramishra, One interesting test would be to check tripleo from early newton 08:26:40 To confirm that 08:27:05 its a bit tricky, heat and tripleo-heat-templates evolved in parallel 08:27:43 I mean, old tht ought to work on heat master though 08:27:45 yeah, zeneb was probably suggesting it might be the thts or some process consuming all memory after they increased it? 08:27:48 Unless we have a regression 08:28:28 yaql is definitely among the culprits 08:28:49 They had to increase its memory limit, but only to 100k AFAIU 08:30:39 yeah, I've seen that discussion too. 08:32:27 yeah, we'll continue looking for improvements. 08:32:51 should we move on or anyone has any more to discuss? 08:33:14 I'm good 08:33:37 I have nothing to add 08:33:45 #topic open discussion 08:34:45 btw, we got the stable:follows-policy patch merged https://review.openstack.org/#/c/379114/ 08:35:25 Now we have the tag for both heat and python-heatclient 08:35:41 Cool 08:36:04 +1 08:36:19 so we will get +1 here? 08:36:19 https://www.openstack.org/software/project-navigator/ 08:36:56 ricolin: I assume so, when the newton one is available/ 08:37:15 It is already there it seems 08:37:26 cool :) 08:39:52 yep, anything else? 08:39:54 we could probably have a crack at ops-sdk-support and asserts_support-rolling-upgrade in this cycle 08:40:35 stevebaker: zaneb has suggested a summit session to discuss what we can do get those. 08:40:39 I've added that one 08:40:44 +1 08:40:49 I think it's worth to discuss that 08:42:20 ok, anything else? 08:42:44 thanks all for joining 08:42:50 \o 08:42:51 #endmeeting heat