15:00:19 #startmeeting heat 15:00:25 Meeting started Wed May 11 15:00:19 2016 UTC and is due to finish in 60 minutes. The chair is therve. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:29 The meeting name has been set to 'heat' 15:00:34 #topic Roll call 15:00:37 bye 15:00:47 Hey heat people 15:00:50 hi 15:00:54 hey everyone 15:01:09 o/ 15:01:11 Hi! 15:01:35 howdy 15:01:57 hi 15:02:14 o/ 15:02:34 Alright :) 15:02:43 #topic Adding items to agenda 15:02:53 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-05-11_1500_UTC.29 15:02:57 Feel free! 15:03:13 #topic Grenade failures 15:03:18 Okay, so 15:03:28 We're still getting floating ip failures AFAICT 15:03:32 I saw a patch get merged for that 15:03:40 I thought the neutron-vpnaas patch would fix it 15:03:45 But it seems that it didn't 15:03:57 yeah, it did not fix the issue 15:04:30 :( 15:04:32 ramishra, Do you understand why it should have? :) 15:04:50 It's not like floating ip and vpnaas seem related 15:05:21 Also, it's intermittent 15:05:28 therve: yeah, I did look at issue last week 15:05:39 hmm, the patch does say Partial-Bug 15:05:53 therve: not sure why the neutron guys thought vpnaas was the problem 15:06:05 however, I thought they know more:) 15:06:12 Heh 15:06:24 I did try to persuade the tempest team to disable the test 15:06:24 Should I just harass neutron people then? 15:06:27 kevinbenton: ping re bug 1579235 15:06:28 bug 1579235 in neutron "FloatingIP is at status: ACTIVE. failed to reach status: DOWN" [High,In progress] https://launchpad.net/bugs/1579235 - Assigned to Kevin Benton (kevinbenton) 15:06:39 without luck:( 15:06:48 therve: kevinbenton said "their job is running vpnaas agent and its clobbering stuff" 15:07:29 Does the grenade job runs against all master release? 15:07:41 Maybe it needs a mitaka backport or something? 15:07:48 intermittent failure is an understatement 15:07:56 it fails 3 out of 4 times 15:07:59 Right 15:08:12 Not all the time is intriguing though 15:08:19 therve: that's a good point, it's probably the mitaka agent that needs to be stopped 15:08:42 therve: i think it was partly a hunch because the time when our gate failures began coincided with https://github.com/openstack-dev/devstack/commit/602a455746461167e211cf19a39349e32df9e08a 15:09:40 ah, so it shouldn't be broken in mitaka? 15:09:50 jasond, Hum. Can we make a revert and then check if the gate works in heat? 15:10:39 therve: it's worth a try 15:10:41 Ah 15:10:43 zaneb, https://review.openstack.org/313792 15:10:50 o/ 15:10:56 o/ 15:11:06 Hum wait it merged today 15:11:47 Okay, I'll see if we need a mitaka backport. Any other idea? 15:12:24 kevinbenton said "i think generally something is screwing up the l3 agent" ... "i think jasond is just getting a side effect of the floating IP status not getting updated because of it" "something is killing the namespace i think" 15:12:38 :/ 15:12:47 That's a lot of guessing 15:12:56 yeah 15:13:09 leave a comment on the bug letting Neutron folks know it isn't fixed 15:13:17 zaneb: ok 15:13:33 and see if they have other ideas 15:13:34 yes, I can see errors with iptable-save in the l3-agent logs 15:13:45 plus prod them relentlessly 15:14:09 zaneb: :) they were pretty responsive 15:14:31 jasond: great :) 15:14:51 OK. Let's try to continue to fix that :) 15:14:53 Moving on 15:15:06 #topic Discuss the patch https://review.openstack.org/#/c/308238/ 15:15:08 Hi all, sorry I am late :) 15:15:16 Bug #1571976 15:15:18 bug 1571976 in python-heatclient "openstack stack output show stack1 output1 reports inconsistent result formats" [Low,In progress] https://launchpad.net/bugs/1571976 - Assigned to Di XiaoLi (dixiaobj) 15:15:18 Let's see 15:16:01 for bug #1571976 openstack stack output show command output format is not consistent across multiple options when --all is used the field list is not consistent. 15:16:18 I think I agree with skrainev, we can't change the output arbitrarily 15:16:21 so, want to discuss wether this patch https://review.openstack.org/#/c/308238/ will break the compatibility or break user's scripts or something else? 15:17:02 okay 15:17:04 It's a bit too bad because it looks awful, but we have to live with it for now 15:17:10 Others? 15:17:42 probibly add some more doc for now 15:18:15 ricolin, How so? 15:18:35 My suggestions were in comments 15:18:41 some 15:18:47 yes 15:19:15 add more comments around to make sure we keep in notice for this 15:19:31 we already have different output in some heat and openstack commands 15:19:56 for example `heat output-list` and `openstack stack output list` 15:20:02 but don't think we should change it right away 15:20:49 duvarenkov_, The issue is not to make it different, the issue is to change what's already in a released version 15:20:53 duvarenkov_: but havent we already released on the OSC plugin? if we were going to use that as a backward compat explanation, it seems like we missed that chance 15:21:38 So I think we agree on not to do that 15:21:48 The solution is a bit harder to find 15:23:20 Moving on 15:23:27 #topic Open discussion 15:24:19 ya, so 15:24:34 i just got an email that the zuul config changed and you should start seeing a job about the api-ref generation appearing 15:24:53 I played a bit with osprofiler in Heat. It's pretty cool, but not sure I'll be able to do much with it. 15:24:55 i'll send out an email to the list too, but i'll keep an eye on the job too 15:25:02 jdob, Hope you didn't break the gate :) 15:25:28 no, I added an entirely new gate job that can be broken 15:25:36 It's non-voting? 15:25:43 should be voting 15:25:56 well, lemme rephrase 15:26:05 it follows the same model as the api-ref jobs do for other projects 15:26:20 i assumed that was voting, but truth be told, I dont know for sure 15:26:41 its bascially a template in project-config that I was able to reference 15:26:48 We'll see :) 15:27:03 jdob, Is the publishing part taken care of just after? 15:27:09 yes, that should all be magic 15:27:41 (I know it inspires all sorts of faith in me as a coder that I'm relying on magic) 15:28:18 And we already got a fix for some api doc, so that's awesome 15:28:53 ya, following this, I'd like to spend some time on the docs themselves 15:29:00 reviewing/polishing/etc 15:29:32 jdob, So to be clear it should push to http://developer.openstack.org/api-ref-orchestration-v1.html automatically? 15:29:32 was just waiting on the gate job and have some other stuff on my plate 15:29:39 thats my understanding, yes 15:29:58 nice 15:30:06 and its all in tree, which is nice 15:30:13 Somewhat annoyed we have http://docs.openstack.org/developer/ and http://developer.openstack.org/ 15:30:16 But anyway :) 15:30:21 cool 15:31:01 * jdob registers openstackdocs.org and docsopenstack.org 15:33:02 Anything else? 15:33:05 therve: those are different - the second one is for those who develop against OpenStack 15:33:21 first is for those who are developing the OpenStack :) 15:34:05 pas-ha, Well there is something wrong then, because it's not true 15:34:19 We have "user" doc in the first one 15:35:13 long-standing problem 15:35:37 we have docs that are for end-users but which describe templates rather than APIs 15:35:44 and there's no category for that :( 15:36:51 Yeah it's a bit weird 15:37:00 Anything else? 15:37:01 zaneb: they can not meet each other... docs and users.. docs and operators.. 15:37:09 arguably heat templates are their own type of user interface and deserve equal billing with the CLI and API 15:37:25 but I don't think we've tried to make that argument 15:38:02 therve: not from me. ;) 15:38:23 Alright. Thanks all! 15:38:26 #endmeeting