15:00:11 #startmeeting heat 15:00:12 Meeting started Wed Jul 26 15:00:11 2017 UTC and is due to finish in 60 minutes. The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:13 #topic roll call 15:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:16 The meeting name has been set to 'heat' 15:01:06 hi 15:01:14 o/ 15:01:15 Hi team 15:01:22 o/ 15:01:40 o/ 15:02:11 #topic adding items to agenda 15:02:13 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-07-26_1500_UTC.29 15:03:40 #topic Feature freeze week 15:03:47 #link https://etherpad.openstack.org/p/pike-3-feature-freeze-review-list 15:04:30 So I make a list for BP relative patch that hope to get landed this week 15:04:58 So we can make feature freeze before this Friday 15:05:26 Any BP relative patch missing?:) 15:06:08 PS stack definition incloud all 11 remaining patch:) 15:06:15 why are the heat-templates patches in that list?;) 15:06:54 ramishra, good question, so heat-template not limit by feature freeze? 15:07:13 if we can get the first 8 of stack-definition then I'll be happy 15:07:21 the last 3 are just refactoring 15:07:45 zaneb, I think we can even make those FFE if that's required:) 15:08:01 ok 15:08:19 the first one is approved already 15:08:27 zaneb: we've 2 more days, we are merging on an average 4 patches of that series everyday;) 15:08:28 the BIG one is next 15:08:36 but it's not as scary as it looks 15:10:06 Also we might need some stable branch approve on heat-template and other repos 15:10:30 there's a stable branch for heat-templates? 15:10:39 I notice a global requirement for ocata in heat-template stay in list for long 15:10:54 or another project!? 15:10:59 checking 15:11:49 did I said heat-template? I mean python heatclient:) 15:11:52 https://review.openstack.org/#/c/443877/ 15:12:07 and it's going to land:) 15:12:17 so nevermind! 15:12:41 * zaneb did a bunch of heatclient reviews yesterday 15:13:43 And final ask is there any other BPs that we should land this week? 15:14:00 or is there any BPs in list that we should not land this cycle? 15:15:03 Okay! move on:) 15:15:05 #topic UI for Heat Template Creation (from kazsh) 15:15:17 kazsh, I think it's yours:) 15:15:27 yep, thanks ricolin :) 15:15:52 UI for Heat Template Creation, I guess some people were thinking to implement 15:16:03 like.. 15:16:04 https://blueprints.launchpad.net/heat/+spec/hot-generator-visualizer 15:16:23 Also found similar in horizon, https://blueprints.launchpad.net/horizon/+spec/heat-template-creator 15:16:55 Does any one work for this subject ? 15:17:02 somebody did this at one point but it was abandoned afaik 15:17:31 ok, recently I and my team are keen to make it easier for user to create hot 15:17:48 kazsh: https://github.com/rackerlabs/hotbuilder 15:18:24 kazsh: last commit is 2 years ago, but would be easier than starting from scratch 15:18:30 And developed drag & drop hot generator in Horizon, now this function is working in our cloud services. 15:18:51 thanks for your advice zaneb :) 15:19:02 FYI https://youtu.be/RrsXOR521uQ 15:19:23 kazsh: Is it a horizon plugin? 15:19:25 this is demo which our hot generator working in Horizon 15:19:33 not yet 15:19:45 ramishra 15:20:02 I'm planning to propose this to horizon 15:20:23 kazsh, yeah, that will be a very helpful feature, so you guys implement this on both heat and horizon, or just horizon will do? 15:20:25 but before that, would like to know is there any same activity happening or not 15:20:46 at this moment, only horizon 15:21:11 but I guess we need heat team's help, advices on this 15:21:19 kazsh, no one working on this AFAIK 15:21:41 ok, well there is no conflict 15:22:18 Does any one help me to reach out horizon team, do you know someone best whom I should consult this ? 15:23:27 I think it can be seprate repo like https://github.com/openstack/ironic-ui 15:23:42 If we want:) 15:23:47 ramishra, +1 15:24:04 that looks a plugin, nice +1 15:24:37 https://wiki.openstack.org/wiki/Horizon/Heat-UI 15:25:04 found Template Creator in the bottom 15:25:28 hopefully horizon team also will accept this suggestion 15:25:55 I think we need to pull out existing heat stuff from horizon first and then start adding the generator thing to it. 15:26:21 kazsh, If they don't accept you can help to create a heat-ui repo first and we can do it our self:) 15:26:26 I suggested it a few cycles back but there were no takers and not many to work on it 15:26:29 kazsh, like ramishra said:) 15:26:54 sounds nice :) 15:27:05 yeah, horizon team is really stretched and they're unlikely to want to take on new stuff in-tree 15:27:19 but this is certainly a good idea as a plugin 15:27:29 well, I have some colleagues who can work for this 15:27:56 sold! 15:28:26 decouple the heat portion from horizon code, & make it as a plugin 15:28:43 then..add this new template gen ui 15:28:59 zaneb, is there any deadline in cycle for create a new project? 15:29:37 I definitely wouldn't try to extract a plugin the week of feature-freeze ;) 15:29:56 ;) 15:30:02 zaneb, no!:) 15:30:33 I don't know of any specific guidance on that 15:33:16 I got approval to go the coming ptg from my boss, and just planing to attend horizon's room to talk about this.. 15:33:23 I think you can start on a personal repo like https://github.com/mkr1481/os-hot-gen 15:34:01 kazsh, nice we will have to adopt new feature in Queens, so might be greate to have some prepare and maybe code so we can take more discussion in PTG. 15:34:03 Though the os-hot-gen bp did not progress;) 15:34:19 yea I know I should have small start 15:34:34 ramishra 15:35:20 ricolin, yes we are preparing for those 15:35:53 Nice:) 15:36:18 looks better to make our code a small code as ramishra suggested 15:36:43 sorry a small plugin 15:36:55 in the separated repo 15:38:09 if you will help us in Denver to start have the new activity/project on this and to talk with horizon team, that would be highly appreciated, ricolin :) 15:38:29 kazsh, yes 15:38:37 kazsh, happy to 15:38:59 ricolin, thank you very much !! 15:39:08 kazsh, NP:) 15:39:31 kazsh, anything else on this topic?:) 15:40:20 no, let me keep consulting this with you guys going forward, thanks a lot for your kind advices everybody :) 15:40:51 NP, we're team:) 15:40:59 Move on 15:41:01 #topic Rolling upgrade discussion 15:41:32 kiennt ^^^ 15:41:32 Hi, me and rolling upgrade again 15:42:35 In couple days ago, ricolin told me about QA's answer and ramishra had a question about the gate job 15:43:03 Do you think we should merge patches about spec/docs first and move patch about gate job to next cycle? 15:43:43 ramishra: what's your opinion? 15:44:30 I don't think that's an issue i.e landing patches, we would not get the tag and can't claim it 15:45:36 ps the Q and A from me to Andrea in this link http://paste.openstack.org/show/616597/ 15:45:42 So if the objective is to land those patches, then we can land those, but we can't mark the bp complete 15:46:06 #link http://paste.openstack.org/show/616597/ 15:46:34 ricolin: I don't think QA would have the answer, the fact is we would not test it at the gate does not confirm to the governance requirement 15:47:15 May be ask TC about it rather than QA 15:48:33 Actually TC got no fixed answer for this, they think QA got the answer for what we should test on gate 15:49:58 Keeping aside TC/QA answers, if we think not testing at the gate is fine and we can get the tag without it, we should go for it 15:50:52 ramishra, I think the answer will be, we need test at gate:) 15:51:34 ramishra: How about your patch - Run heat api test after upgrade? 15:51:36 #link https://review.openstack.org/#/c/460542/ 15:52:21 that would not test rolling upgrade(mixed versions), it's just after any upgrade 15:54:04 ramishra: I see, but I can't find the way another projects setup gate for rolling upgrade? Do you know about it? 15:56:14 kiennt: As I said before I don't know how these projects have the tag. We've to by the governance requirement 15:56:32 s/by/go by 15:57:36 But as I said we can land the patches if we want, I would not block them;) but IMO, the bp would not be complete without the gate testing of the feature 15:59:03 ramishra: ok, thank you. So I think the best option is landing the patches, but still marks the bp incomplete until we have a gate job 15:59:16 the actual gate :) 15:59:44 kiennt, I can help to ask TC for tag before pike release, but will be reasonable to apply that with our gate test:) 16:00:56 ricolin: thank you very much 16:01:14 we run out of time, kiennt is there anything more you would like to discuss:) 16:01:35 ricolin: no, i think it is enough today 16:01:40 thank you all 16:01:44 kiennt, :) 16:01:52 #topic Open discussion 16:02:00 Any one need to raise anything?:) 16:02:08 5 16:02:11 4 16:02:13 3 16:02:15 2 16:02:16 1 16:02:19 1 16:02:21 1 16:02:31 okay, thanks all for join:) 16:02:32 #endmeeting