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