14:00:50 <ricolin> #startmeeting heat
14:00:51 <openstack> Meeting started Wed Feb  7 14:00:50 2018 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:55 <openstack> The meeting name has been set to 'heat'
14:01:02 <ricolin> #topic roll call
14:01:26 <ramishra> hi
14:01:38 <kiennt26> hi o/
14:01:41 <ricolin> o/
14:01:47 <kazsh> o/
14:02:46 <zaneb> o/
14:02:47 <ricolin> #topic adding items to agenda
14:02:53 <ricolin> #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282018-02-07_1400_UTC.29
14:02:58 <ricolin> zaneb, morning!:)
14:03:12 <therve> Hey
14:03:34 <ricolin> therve, o/
14:04:59 <ricolin> #topic announce
14:05:43 <ricolin> I remove heat-template-plugin from release
14:06:02 <ricolin> due to the discussion from release team
14:06:06 <ricolin> #link https://review.openstack.org/#/c/530108/
14:06:33 <ricolin> appears they don't think it's necessary to release for any plugin
14:07:24 <ricolin> Also this week we will release rc1, let's discuss about the scope later
14:08:06 <zaneb> this week?!
14:08:15 <ramishra> ricolin: where is the discussion?
14:08:18 <zaneb> we have a _lot_ of open bugs :(
14:08:48 <ricolin> zaneb, supperise
14:08:56 <ricolin> ramishra, you mean the plugin?
14:09:13 <ramishra> yes, I mean tempest-plugins are expected to be branchless, but if a projects don't want that way then?
14:09:47 <ricolin> ramishra, sorry wrong link
14:09:48 <ricolin> https://review.openstack.org/#/c/540269/
14:09:50 <ricolin> #link https://review.openstack.org/#/c/540269/
14:10:23 <ricolin> and the discussion is at https://review.openstack.org/540569
14:10:53 <ramishra> can we bock it till after ptg discussion on the topic?
14:10:55 <ricolin> zaneb, s/supperise/surprise/
14:11:08 <ricolin> yes we can
14:11:28 <ricolin> workflow-1
14:11:39 <zaneb> ricolin: I knew what you meant :)
14:12:15 <ricolin> ramishra, it's not all settle down yet, so I guess we can raise a discussion or join any
14:12:21 <therve> ricolin, There is no point in making rc1 if we know that we have bugs to pass through though
14:12:28 <ramishra> ricolin: yes, thanks!
14:12:45 <ricolin> therve, agree
14:13:03 <ricolin> #topic Release rc1 this week
14:13:27 <ricolin> like therve said we still got some patches for bugs
14:13:38 <ricolin> #link https://etherpad.openstack.org/p/heat-queens-m3-target-patches
14:13:52 <ricolin> lots of them is in above etherpad
14:14:38 <ricolin> So what's the best plan for us to rc1?
14:14:58 <zaneb> review harder
14:15:01 <ricolin> therve, ramishra zaneb thought?
14:15:15 <ramishra> We talking about only the high priority ones right? 5/6 patches?
14:15:18 <ricolin> zaneb, agree
14:15:24 <ricolin> yes
14:15:45 <zaneb> I'd really like to get the bug 1731349 series in too
14:15:46 <openstack> bug 1731349 in OpenStack Heat "Nested stacks are still loaded into memory too often" [High,In progress] https://launchpad.net/bugs/1731349 - Assigned to Zane Bitter (zaneb)
14:16:05 <zaneb> because that will make a huge memory difference for TripleO, in the first release where they are enabling convergence
14:16:21 <zaneb> but at a minimum I think we need to get all the High-priority bugs in
14:16:27 <zaneb> which is not that many
14:16:28 <ricolin> Any other important bugs that not target in that etherpad?
14:17:23 <zaneb> although note that some of the patches in the bug 1731349 series fix other High-priority bugs
14:17:24 <openstack> bug 1731349 in OpenStack Heat "Nested stacks are still loaded into memory too often" [High,In progress] https://launchpad.net/bugs/1731349 - Assigned to Zane Bitter (zaneb)
14:17:44 <zaneb> I think most of those have merged though, they're nearer the beginning of the series
14:17:49 <zaneb> ricolin: I can go through the open bugs again today and update the list
14:18:13 <ricolin> zaneb, that will be great if you can help on that
14:18:15 <ramishra> IMO the test race bugs we should downgrade to medium
14:18:37 <ricolin> ramishra, which link
14:19:01 <zaneb> ramishra: fair enough
14:19:14 <zaneb> would be nice to not have that problem in the gate any more though
14:19:57 <ramishra> zaneb: I've not seen those at the gate for some time, infra is very slow now
14:20:14 <zaneb> heh
14:20:18 <ramishra> so we don't see race condition related issues;)
14:20:54 <zaneb> ok, moved bug 1745276 to Medium
14:20:55 <openstack> bug 1745276 in OpenStack Heat "test_create_update may failed sometimes raise Timeout error" [Medium,In progress] https://launchpad.net/bugs/1745276 - Assigned to zhurong (zhu-rong)
14:21:14 <zaneb> it was raised on 25 Jan though, so someone has been seeing it in the gate
14:21:30 <ricolin> we still have https://bugs.launchpad.net/heat/+bug/1737796 once a while
14:21:32 <openstack> Launchpad bug 1737796 in OpenStack Heat "test test_stack_update_with_conditions fail with new resource not found" [Medium,In progress] - Assigned to Rico Lin (rico-lin)
14:22:05 <zaneb> (also we all could have reviewed that in less time than we've spent talking about it's priority ;)
14:22:39 <ramishra> zaneb: looks like tested by user locally though
14:22:59 <ramishra> but yeah, we should also try close them
14:23:19 <zaneb> ricolin: I fear that may be a real bug. do you know of any logs available from a failure of that one?
14:23:23 <zaneb> ramishra: ah, ok
14:23:45 <ricolin> zaneb, which one you mean?
14:23:55 <ricolin> 1737796?
14:24:04 <zaneb> ricolin: bug 1737796
14:24:05 <openstack> bug 1737796 in OpenStack Heat "test test_stack_update_with_conditions fail with new resource not found" [Medium,In progress] https://launchpad.net/bugs/1737796 - Assigned to Rico Lin (rico-lin)
14:24:42 <ricolin> zaneb, I can try to find and paste from logstash
14:24:46 <zaneb> ricolin: I went looking for logs one time but the gate was borked and not uploading logs at the time
14:24:46 <ramishra> zaneb: Another one I've seen few times you would be interested in https://bugs.launchpad.net/heat/+bug/1747365
14:24:47 <openstack> Launchpad bug 1747365 in OpenStack Heat "Group resource update fails with KeyError" [Undecided,New]
14:25:18 <ricolin> zaneb, yeah, log system broken for a while broke for
14:25:19 <zaneb> ricolin: ah, yeah, I wonder if logstash is working now. it was not working when I tried a week or two ago
14:26:02 <zaneb> ramishra: oh, hadn't seen that. I will look into it
14:26:52 <ricolin> zaneb, here you go http://logs.openstack.org/36/539836/1/check/heat-functional-convg-mysql-lbaasv2-py35/aa0009e/job-output.txt#_2018-02-02_05_52_09_944261
14:27:54 <zaneb> ricolin: thanks, I'll have a poke around in those logs and see if I can learn anything
14:28:30 <ricolin> So what's the basic line for us to said we can release rc1?
14:28:52 <zaneb> ricolin: I'd say all High priority bugs closed
14:29:13 <ricolin> zaneb, and what should we do if it's not reach?:)
14:29:19 <zaneb> #link https://bugs.launchpad.net/heat/+milestone/queens-rc1
14:29:24 <ricolin> s/reach/reached/
14:29:27 <zaneb> ricolin: more reviews? ;)
14:30:10 <ricolin> zaneb, stop it!
14:30:21 <zaneb> we can re-triage the bugs as a group if we think some of them are not high priority
14:30:44 <zaneb> but there's no point releasing an RC if we don't have the high-priority fixes in it
14:30:57 <ricolin> zaneb, what you mean re-triage
14:31:00 <zaneb> because there will have to be another RC for sure if we do
14:31:12 <zaneb> ricolin: pick new priorities
14:31:19 <ricolin> okay
14:31:39 <ramishra> yeah, let's look at them again tomorrow and then see, I think we can land some high priority bugs and retriage the ones left;)
14:31:57 <zaneb> wfm
14:32:10 <ricolin> ramishra, hope so, but not sure if the gate is with us:)
14:32:42 <ramishra> ricolin: it's much better now than few weeks back, fingers crossed
14:32:53 <ricolin> ramishra, agree
14:32:56 <ricolin> Anyway, move on
14:33:13 <ricolin> #topic Queens goal review https://etherpad.openstack.org/p/heat-queens-ptg-conti-for-topics
14:33:28 <ricolin> So for what we target in Queens
14:33:45 <ricolin> #link https://etherpad.openstack.org/p/heat-queens-ptg-conti-for-topics
14:34:27 <ricolin> We still have a rolling upgrade patch
14:34:35 <ricolin> #link https://review.openstack.org/#/c/510400/60
14:34:35 <ramishra> we did whatever we could:)
14:34:37 <openstackgerrit> Merged openstack/heat master: Log when we bail out without checking a resource  https://review.openstack.org/533015
14:34:40 <openstackgerrit> Merged openstack/heat master: Fix hot_spec.rst in Template Guide  https://review.openstack.org/540347
14:34:58 <ricolin> not necessary to land in queens but if we can:)
14:35:06 <ricolin> ramishra, surly do!
14:35:24 <ricolin> For interop
14:35:41 <ricolin> I put a patch in interop
14:35:42 <ricolin> #link https://review.openstack.org/#/c/529836/
14:36:38 <ricolin> if I can finish two tempest id patch
14:36:40 <ricolin> https://review.openstack.org/#/q/topic:ci-test-framework+(status:open+OR+status:merged)
14:36:43 <ramishra> Isn't the debate is still going on where the interop tests would stay, tempest itself or projects/plugins?
14:36:43 <ricolin> #link https://review.openstack.org/#/q/topic:ci-test-framework+(status:open+OR+status:merged)
14:37:16 <ricolin> ramishra, yes it is
14:38:05 <ricolin> If we going to ask for those tests as interop tests the best way is to get them ready at very first place
14:38:33 <zaneb> just assume plugins for now
14:38:43 <zaneb> we can move/copy later
14:38:44 <ricolin> but still we can't guarantee those tests will work in mitaka or newton
14:38:46 <ramishra> yeah, not sure what kind of tests tempest would accept, so probably we should wait
14:39:01 <ricolin> ramishra, okay
14:39:53 <ricolin> though, interop team put that on us to decide what the test range should be
14:40:21 <ricolin> there do have a question in https://review.openstack.org/#/c/529836/
14:40:44 <ricolin> about is it needs to add version test
14:40:54 <ricolin> s/it/there/
14:41:22 <ricolin> ramishra, what you think?
14:43:12 <ramishra> ricolin: We've only one verson, not sure what version discovery would mean
14:43:12 <ricolin> For rest goal, seems all fine to me
14:44:24 <ricolin> ramishra, I guess protentially for future plan, and make it ready at once
14:44:46 <ricolin> ramishra, but TBH I'm not sure if we need that test
14:45:25 <ramishra> ricolin: I don't know. Not been following interop stuff closely to comment
14:46:00 <ricolin> do anyone have time to work on federation document?
14:46:40 <ricolin> Or I will put a releasenote out for now
14:47:12 <ricolin> just to make sure user aware that we actually works with federation
14:47:34 <ricolin> they just have to do those works:)
14:48:26 <ricolin> Okay that's all I have for queens goal
14:48:29 <ricolin> #topic PTG https://etherpad.openstack.org/p/heat-rocky-ptg
14:48:36 <ricolin> Now Rocky:)
14:48:52 <ricolin> #link https://etherpad.openstack.org/p/heat-rocky-ptg
14:49:28 <ricolin> There is two almost be there rocky cross project goals
14:49:41 <ricolin> and one of them is -1ed by zaneb
14:49:45 <ricolin> #link https://review.openstack.org/#/c/532361/
14:49:50 <zaneb> :)
14:50:34 <ricolin> here is another one https://review.openstack.org/#/c/534605
14:50:40 <ricolin> #link https://review.openstack.org/#/c/534605
14:51:18 <zaneb> I think we need to start on the mox one whether or not it is approved, because we have a lot of mox to clean up
14:51:28 <zaneb> and we know it will have to happen eventually
14:51:56 <ricolin> zaneb, agree
14:52:05 <zaneb> so we should start asap and not be rushing when it becomes a goal
14:52:25 <ramishra> yep, sooner the better:)
14:52:50 <ricolin> we can say no to it this cycle and raise it next one, so we will have two cycle to done those works:)
14:53:45 <zaneb> ricolin: Nova is going to take two cycles anyway, by the sounds of it
14:54:05 <ricolin> Also for propose in https://etherpad.openstack.org/p/heat-rocky-ptg
14:54:05 <zaneb> but we can't be behind them ;)
14:54:47 <ricolin> zaneb, how about we just rename mox to mox+ :)
14:56:01 <ramishra> Motivating people to work on that is difficult, as I've seen myself where in some patches I've tried to change those along with other changes (which would have made the review a little hard) and were rejected
14:56:15 <ricolin> will be great if topics can get moderators first, so if people're interesting on those topic please feel free to sign your name on
14:57:12 <zaneb> ramishra: it's much easier to review test changes if they're independent of code changes, because that way you know that the test changes aren't accidentally covering up code breakages
14:57:14 <ricolin> ramishra, agree, maybe make it a goal will make those work easier, but it's hard works for sure
14:57:47 <zaneb> also unit-test-only patches don't run the functional tests in the gate, which makes things a lot quicker :)
14:57:48 <ramishra> zaneb: yeah, but fixing the tests twice, you should be super motivated:)
14:59:07 <ramishra> but yeah having it as goal would help
14:59:15 <zaneb> ramishra: I hear you :) but imho more work up front to make less work for reviewers is worth it. fewer bugs and changes merge quicker
14:59:39 <zaneb> in theory, anyway ;)
14:59:43 <ricolin> ramishra, maybe we should share those tests for maybe six part and share!:)
15:00:12 <ricolin> anyway we can done that in PTG:)
15:01:27 <ricolin> For topics in PTG they all sounds great to me
15:02:48 <ricolin> but again we needs driver and moderators so please put your name on top if you like, it can be more them one I think
15:03:17 <ricolin> otherwise I will put myself for moderator(at least for PTG)
15:03:34 <ricolin> #topic Open discussion
15:03:37 <ricolin> What else?
15:04:34 <ricolin> Also I sign us out for Project update in Vancouver, if anyone interesting in join together please let me know
15:04:41 <ramishra> https://review.openstack.org/#/c/529480/, I want this to land, but it can be very fragile with octavia, so I've not pushed for it yet to be reviewed
15:05:49 <zaneb> ramishra: what's causing the fragility?
15:06:04 <ramishra> zaneb: amphora vms
15:06:32 <ramishra> with the condition of the infra, I'm sure it would fail at times
15:07:33 <ramishra> so I'm not sure, whether we should test it at the gate or not.
15:08:38 <ricolin> I feel this plan in magnum team is interesting, it's about auto healing approach in https://review.openstack.org/#/c/529897/
15:09:47 <ricolin> We're 9mins delay, anything else for all to note about
15:09:55 <kazsh> ricolin: I'm interesting in the project update in Vancouver, would like to explain the new dashboard along with you if possible.
15:10:28 <ricolin> kazsh, cool, I will remember that
15:10:37 <kazsh> ricolin: thx!
15:11:11 <ricolin> Okay, if that's all thanks all for join zaneb ramishra kazsh kiennt26 therve
15:11:13 <ricolin> #endmeeting