08:00:13 #startmeeting heat 08:00:14 Meeting started Wed Nov 30 08:00:13 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:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:17 The meeting name has been set to 'heat' 08:00:22 #topic roll call 08:01:15 o/ 08:02:22 ricolin: hmm it seems no one is around for the meeting other than we both. 08:02:36 hi 08:02:43 I am here 08:02:45 :) 08:02:49 ramishra: three of us! 08:03:00 tiantian: thanks for joining:) 08:03:09 so it would be quick then 08:03:15 * Qiming is virtually here ... 08:03:28 #topic adding items to agenda 08:03:38 https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282016-11-30_0800_UTC.29 08:03:58 If anyone else has anything to discuss 08:04:40 #topic Clean up old patches 08:04:54 Not sure who added this. 08:05:00 I do:) 08:05:04 but we need to clean them. 08:05:18 there are plenty of patches with merge conflict. 08:05:26 some from the cores also;) 08:05:27 one thing I'm interested in is about Heat API v2 08:05:38 #link https://review.openstack.org/#/q/project:openstack/heat+branch:master+age:12weeks++status:open 08:05:57 This is the query with patches 12 weeks old. 08:06:00 true, Just think we have a lot of patch that did not working for least few monthes 08:06:49 Can we please abandon them or resubmit them. Else, we would be forced to abandon patches of others. 08:07:00 I can do that:) 08:07:16 Qiming: I think we've to postpone that when more people are around. 08:07:21 may be next week? 08:07:33 that is fine 08:07:51 but I really like to complain to the PTL before a bigger meeting 08:07:56 :D 08:08:10 or may be start a ML thread. 08:08:10 ramishra,hi 08:08:25 yeah, complains are always welcome. 08:08:26 Qiming. hi 08:08:34 sorry, I am late 08:08:37 hi, shizhihui_ 08:08:45 shizhihui_, skraynev hi 08:08:51 add that to the agenda 08:09:11 skraynev: np:) we don't have too many things to discuss. 08:09:24 skraynev: I need your help in the next topic though. 08:09:44 #topic Liberty EOL 08:09:54 #link http://lists.openstack.org/pipermail/openstack-dev/2016-November/107717.html 08:10:05 this is a mail for EOL tagging. 08:10:26 We've a few patches still with open status. 08:10:34 #link https://review.openstack.org/#/q/project:openstack/heat+branch:stable/liberty+status:open 08:10:46 I think we should just abandon them? 08:11:03 Liberty gate is broken too. 08:11:16 skraynev: you're the stable core, may be you can help? 08:11:45 not much you can do if the gate is broken 08:12:04 yeah, it would take lot of time to fix and land these patches. 08:12:13 ramishra: I tend to agree with abandon 08:12:17 don't think they worth it 08:12:19 Not sure if anyone has any objections. 08:12:45 As I remember I have seen several at least one -1 for each of these patches. 08:13:13 skraynev: I can't abandon it(don't have stable permissions), so you can help do that. 08:13:31 or may be zaneb, stevebaker, shardy. 08:13:31 It doesn't look like there is anything critical in there 08:14:00 therve: hi, yeah I agree, I wanted that requirement change to go in. 08:14:03 I think abandon will not be a big deal here 08:14:22 but there seems to be multiple things broken. 08:14:47 ramishra: could you tell me the best reason for explanation in message for abandon ? 08:15:08 skraynev: EOL tagging, gate broken? 08:15:48 ok. We abandon this patch due to EOL for liberty and broken gate state. :) 08:15:52 ramishra: thx 08:16:09 skraynev: thanks! 08:17:22 ok, anything else? 08:17:46 #topic open discussion 08:18:23 ramishra: abandonong is done! 08:18:26 so there will be a topic for Heat API v2 next week?:) 08:18:27 Qiming: I'll add the v2 api in the next meeting agenda. 08:18:33 *abandoning 08:18:45 ramishra, I agree that API V2 is gonna be a big thing to discuss around the team 08:18:57 Qiming, Why? 08:19:06 before that, I just want to raise some awareness about this 08:19:18 cool, we got at least one 'why' here, :) 08:19:52 one of the reasons is about conformance to API WG guidelines 08:20:18 Dang 08:20:25 I was feeling quite some pain when adding support to Heat "resources" to openstacksdk: e.g http://git.openstack.org/cgit/openstack/python-openstacksdk/tree/openstack/orchestration/v1/stack.py 08:20:26 If that's your number 1 priority... 08:21:38 previously, asakeld and I were on a blueprint for this: https://wiki.openstack.org/wiki/Heat/Blueprints/V2API 08:22:30 besides things mentioned in the wiki above 08:22:43 I'm also thinking about API micro-versioning 08:22:56 That was like 3 years ago and nothing happened :) 08:23:08 while discussing about API stuff, I have some gabbi test patches for review, if someone can find time to look at. 08:23:09 what I have seen is that we kept adding/removing fields to APIs 08:23:13 https://review.openstack.org/#/q/project:openstack/heat+branch:master+topic:gabbi 08:23:24 yes, therve, asakeld's fault, not mine, :) 08:23:46 Qiming, Well, it's not like you implemented the changes either 08:24:09 right, it was never on the agenda 08:24:23 We don't have many contributors nowadays, I feel we have more important things to focus on than moving some URLs around 08:24:28 But that's just me 08:25:03 okay, your opinions well received, :) 08:26:47 yeah, we may start working on some of these things. 08:28:10 ramishra, these changes, if we want to land them, should reside on a different endpoint 08:28:20 we cannot break existing users 08:28:55 Qiming: yeah 08:29:03 We mostly made a good job with that without a new API :) 08:29:35 not fully agree, therve 08:30:07 for example, because we have stack_name in the URI, we are not supporting unicode stack names very well 08:31:26 Hum okay, that's not what I was getting at 08:31:33 Anyway no need to talk about that now 08:32:18 ok, I'll add this and rolling upgrade to the topic next week. 08:32:28 yep, complaints ended, :) 08:32:40 Hopefully we would have more people around to discuss. 08:33:08 ok, anything else? 08:34:29 thank you all for joining. 08:34:36 thanks 08:34:38 #endmeeting heat