08:00:21 #startmeeting heat 08:00:22 Meeting started Wed Jul 27 08:00:21 2016 UTC and is due to finish in 60 minutes. The chair is therve. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:27 The meeting name has been set to 'heat' 08:00:27 #topic Roll call 08:00:49 heya 08:00:58 o/ 08:02:10 ramishra, Around? 08:02:13 hi 08:02:17 hi 08:03:11 That'll be a quick one :) 08:03:20 #topic Adding items to agenda 08:03:28 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-07-27_0800_UTC.29 08:04:54 #topic Gate status 08:05:20 It seems relatively bad these past couple of days, but it doesn't look like our fault 08:05:52 Infra seems particularly slow 08:05:53 http://status.openstack.org/elastic-recheck/ 08:06:00 ramishra, Noticed anything? 08:06:29 stevebaker, Yeah not sure there is a bug in there per se 08:06:41 Nodes are just super super slow and we timeout a lot 08:06:48 Bug 1546431 may have gotten worse after ramishra's last change landed, but it may be completely unrelated 08:06:48 bug 1546431 in heat "Tests fails with SQL error 'Command Out of Sync'" [High,In progress] https://launchpad.net/bugs/1546431 - Assigned to Rabi Mishra (rabi) 08:07:06 stevebaker, Where have you seen it? 08:07:09 therve: I've seen a couple of fedora image download timeouts 08:07:25 Yeah... Still better than the previous download I think 08:07:27 therve: in the chart on http://status.openstack.org/elastic-recheck/ 08:07:31 And at least it fails fast :) 08:07:40 Are we on to the first topic? 08:07:46 Ah :/ 08:07:56 therve: we could get the fedora image cached on AFS 08:08:04 ramishra, The topic should be in the topic :) 08:10:14 stevebaker, I've seen that error somewhat related to infra performance, so hopefully that's just the link 08:10:54 therve: you mean the image download? 08:11:08 stevebaker, No the out of sync error 08:11:33 hmm, I guess a slow node could make the race more likely 08:11:57 I think so yeah 08:12:19 sorry guys, my network is terrible today. 08:12:37 Anyway there is not much we can do when a node takes 45 mins to setup 08:13:25 #topic N3 status 08:13:54 We're moving sloooowwwwwly 08:14:39 Please review more stuff :/ 08:15:12 therve: should we maintain priority reviews etherpad like we used to do in ealrier cycles? 08:15:26 #link https://launchpad.net/heat/+milestone/newton-3 08:15:38 ramishra, I'm not a giant fan, but maybe we'll have to do it 08:17:47 #topic Open discussion 08:18:33 I've started playing with gabbi today, and have it doing some basic stack operations 08:19:35 stevebaker, Is that... useful? 08:19:39 I'd like to propose that we write a full REST API test suite in gabbi. therve what do you think that would need to discuss? a blueprint? a wishlist bug? 08:20:37 therve: having decarative REST API tests will be nice I think. And I suspect it will be the easiest thing to get into tempest core for defcore 08:20:37 stevebaker, What's the point exactly? 08:20:54 I though using tempest was the best for defcore 08:22:05 therve: nobody maintains the REST API tests in tempest core, and they're incomplete so they're not a great start for defcore 08:22:13 I guess I have enough questions that he deserves a spec 08:22:27 Also, we should probably do that in the next cycle unless there is a real rush 08:22:49 no rush I think at this point, I'm just seeing if its feasible 08:23:15 stevebaker, Yeah but I wonder why rewriting stuff with another tool will make it maintenable 08:23:25 Instead of improving what's already there 08:24:06 testing REST APIs with declaritive yaml is *really* nice 08:24:42 it will likely show some issues with our api-ref because its so clear to see what is going on 08:25:40 Okay 08:26:07 Anything else? 08:28:16 Alright, thanks 08:28:19 #endmeeting