06:59:08 #startmeeting Heat 06:59:09 Meeting started Wed Oct 14 06:59:08 2015 UTC and is due to finish in 60 minutes. The chair is skraynev. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:59:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 06:59:12 The meeting name has been set to 'heat' 06:59:25 #topic rollcall 06:59:38 \o 06:59:43 o/ 06:59:43 o/ 06:59:44 hi 07:00:10 hi 07:00:28 hi 07:01:34 #topic Adding items to agenda 07:01:48 #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282015-10-14_0700_UTC.29 07:02:02 we have really short agenda for today 07:02:18 any additional topics? 07:02:19 hi 07:02:21 o/ 07:02:45 I've seen nothing to warrent an rc3 07:03:28 stevebaker: feel free to add, I thought, that it may be part of "Updates from meeting with release team" 07:04:05 stevebaker: I have not any specific info about it. 07:04:33 ah, we're on target for release then, thats all the news I have 07:04:43 #topic Updates from meeting with release team 07:05:00 yeah. I wanted to say something like that :) 07:05:04 I've retagged the remaining liberty-rc-potential with liberty-backport-potential 07:05:28 ttx mentioned during meeting, that we 2 days before release 07:06:05 stevebaker: thank you. I just recently started to use liberty-backport-potential 07:06:12 there was a new Kilo release today with *heaps* of fixes 07:07:01 https://launchpad.net/heat/kilo/2015.1.2 07:07:27 #info please use liberty-backport-potential tag instead of liberty-rc-potential for bugs which will be backported to Liberty 07:07:43 o/ 07:08:34 stevebaker: is it ok, that some bugs have Fix Committed status? 07:08:42 instead of Fix released 07:09:22 skraynev: hmm, I saw that. I'll chase up and see if they made it in the release 07:09:28 skraynev: not sure why that is 07:10:05 asalkeld: probably you don't want to release them ? :) 07:10:23 i don't set that, it's all automagical 07:10:47 * skraynev scratches his head 07:10:51 once the fix is merge it goes to fix commited 07:11:08 then when it is tagged , it gets set to released 07:11:37 asalkeld: I suspect the release manager has to run a script to make everything go to Fix Released. When I release things the 'script' is my clicky finger 07:11:38 asalkeld: I thought, that ttx did it manually 07:11:56 stevebaker: genearlly bugs that are FixCommitted means they are fixed in the master branch but were not published in any RC or milestone yet 07:12:16 I take all FixCommitted and turn them into FixReleased when I do a milestone 07:12:24 so there should not be leftovers 07:12:32 ttx https://launchpad.net/heat/kilo/2015.1.2 07:12:38 ttx: we're looking at the 3 FixCommited in the last kilo release https://launchpad.net/heat/kilo/2015.1.2 07:12:41 oh. That 07:12:47 ttx there are some there, and we are a bit confused about those 07:12:51 I don't handle that myself 07:13:01 so it's extremely possible that they miss things 07:13:07 k 07:13:25 ttx: thx. 07:13:49 one of the many reasons why we drop synchronized point releases with stable/liberty :) 07:14:01 I'll set them to Released once I've confirmed they're in stable/kilo 07:14:11 we should asking Doug, but habbits hard to change 07:14:50 stevebaker: ok. please fix it. 07:15:31 skraynev: is the session track sorted yet? 07:15:37 (for summit) 07:15:48 asalkeld: it's next topic in agenda 07:15:59 #topic Summit topics final revision 07:16:00 oops 07:16:09 #link https://etherpad.openstack.org/p/mitaka-heat-sessions 07:16:30 I have sorted them by time and slots, so please review it 07:16:47 I have some doubts about couple items 07:17:18 e.g. Convergence Phase 2 was moved to metup, because we had huge discussion about it before 07:17:49 so probably we may just take a look on specs 07:18:06 skraynev: if this was a fishbowl then the projector could be used to bikeshed the new commands: 12. Complete heat support in python-openstackclient 07:18:52 skraynev: maybe swap with 14.? 07:18:57 yes. it was my doubt 07:19:09 sure 07:19:15 skraynev: it looks mostly fine to me 07:19:57 stevebaker: updated 07:19:58 tho' if you are short of tracks this might not need a whole session "Do we need an ops tool to migrate stacks to/from convergence?" 07:20:37 could merge into the general convergence talks / or leave as-is 07:20:52 skraynev: 5. 15. and 13. are all user-facing features, so maybe one of them would be better in the fisbowl instead of 0. 07:20:53 asalkeld: I prefer second variant 07:20:57 skraynev: if you need to, we can combine 5 & 15 but I'm happy to leave them separate if we have enough time 07:21:33 stevebaker: if we do that I'd favor moving the parameters one 07:22:04 7 and 14 look somehow related - does it make sense to merge them? 07:22:04 stevebaker: not sure, that one fishbowl will be enough... 07:22:12 tho' it seems we have nicely filled our slots 07:22:37 so any merging will mean an empty slot? 07:22:50 asalkeld - yes 07:22:57 imho - ship it~ 07:23:18 were we going to have a convergence phase 2 session? or is that 8.? 07:23:20 tspatzier: I think, that 14 is mostly about Senlin and future refactoring RG, ASG 07:23:50 stevebaker: the friday session 07:23:51 tspatzier: 7 was aimed on potential problems on big scale 07:24:08 * stevebaker scrolls 07:24:09 skraynev, but still about scaling. maybe those should at least be adjacent sessions? 07:24:11 ahh 07:24:24 stevebaker: was moved to meetup 07:24:34 good call 07:24:49 tspatzier: FWIW I see those as separate, as it's more about working at scale than automated scaling 07:24:54 skraynev, can we move 14 around? I have a talk during 9:50am-10:30am Thursday morning 07:25:08 e.g TripleO faces the same issues mentioned in (7) but currently doesn't use ASG at all 07:25:22 shardy, ok, got it now ... this subtle difference of "scale" ;-) 07:25:31 Qiming: is it ok to move at 9.00 ? 07:25:51 skraynev, 9.00 sounds better, :) 07:26:39 tspatzier: 7 scale deployment, 14 scaling VMs in stack 07:27:04 skraynev, I'm bought into it :-) 07:27:14 Qiming: done 07:27:20 thx 07:28:00 tspatzier: playing around word "scale" :) 07:28:49 stevebaker: shardy: so what decide about 15 and 5 ? 07:29:21 empty slot we may feel by convergence phase 2 talks 07:29:27 skraynev, shardy: should we swap 5 and 0? 07:29:41 skraynev: I updated the title to remove the "scaling" word ;) 07:30:14 shardy: thx. looks better 07:30:16 lol 07:30:36 stevebaker: now I think - yes 07:31:02 skraynev: if you need the slot, I'm happy to combine 5 & 15 07:31:03 because convergence is not production ready (we wanted to finish it during M) 07:31:07 skraynev, shardy ug, I meant 15 and 0 07:31:14 they're somewhat related I guess 07:32:08 I don't really mind which 07:32:47 shardy: not sure that zaneb will be happy to see slot for Convergence Phase 2, but I think it will be useful (if you think, that will discuss everything in one slot) 07:33:36 skraynev: Ok that's fine 07:34:22 shardy: ok. I will merge 5 & 15, swap it with 0 and add (1) on empty slot 07:34:33 if we have a slot for phase 2 we can always continue any overflow on the meetup day 07:35:00 stevebaker indeed 07:36:40 shardy: oops 07:37:02 could you swap them yourself? 07:37:08 5 with 0 07:37:28 skraynev: sorry, I'm done, combined 5 & 15 07:37:41 shardy: ok, then I will continue 07:39:46 shardy, stevebaker, asalkeld, zaneb: please review final result 07:40:41 skraynev: lgtm 07:40:44 asalkeld: stevebaker: "Team review/triage session for specs" 9 was moved to meetup according comments 07:40:59 lgtm 07:41:08 I also agreem that it will be the best time for such talk 07:41:33 skraynev: looks good, thanks 07:41:38 #action skraynev will migrate all topics to sched.org 07:41:51 Good. Thank you for the help. 07:42:18 I will do it during today and tomorrow and will send email :) 07:42:40 #topic Open discussion 07:43:18 I forgot to mention about crossproject specs 07:43:35 They are in meetup section 07:43:53 #link https://review.openstack.org/#/c/214817/ 07:44:17 #link https://review.openstack.org/#/c/181393/ 07:44:25 I wanted to ask if anyone else has seen any racy behavior with either ResourceGroup or SoftwareDeploymentGroup lately 07:44:27 #link https://review.openstack.org/#/c/221163/ 07:44:42 I know there's been a bunch of changes, but I'm failing to reproduce https://bugs.launchpad.net/heat/+bug/1503694 07:44:42 Launchpad bug 1503694 in heat "A bad or out-of-range value was supplied:The Resource (0) could not be found in Stack" [High,Triaged] - Assigned to Steven Hardy (shardy) 07:45:09 In this scenario a RG of size 3 was created, but the first resource is missing 07:45:43 If anyone sees anything similar, please update the bug with how you reproduced :) 07:46:00 shardy: I have not met such issue 07:46:11 if will seen on gate will ping you 07:46:44 skraynev: thanks, I assume we've not got gate coverage of it it was more of a general cry for help :) 07:47:00 shardy: I've not seen any. There are some other issues, like https://bugs.launchpad.net/heat/+bug/1503180, but I've not seen them in the last week. 07:47:00 Launchpad bug 1503180 in heat "functional.test_autoscaling.AutoscalingGroupUpdatePolicyTest heat_integrationtests.common.exceptions.StackBuildErrorException" [Medium,Confirmed] - Assigned to Rabi Mishra (rabi) 07:47:47 ramishra: heh. we fix bugs without any specific fixes... 07:48:01 The above issue only happened twice and then I've not seen it. 07:48:09 ramishra: Yeah, I was thinking of the races you fixed, but I couldn't see how they could create the wrong number of resources 07:48:26 same for this one https://bugs.launchpad.net/heat/+bug/1503955 07:48:26 Launchpad bug 1503955 in heat "functional.test_validation.StackValidationTest.test_stack_validate_provider_references_parent_resource" [Medium,Confirmed] - Assigned to Rabi Mishra (rabi) 07:48:31 anyway, something to keep an eye out for - I'm going to attempt a stress test later & try to trigger it 07:49:00 sure, I'm having a watch too:) 07:50:30 #info if gate fails with similar issue like in https://bugs.launchpad.net/heat/+bug/1503694 https://bugs.launchpad.net/heat/+bug/1503180 https://bugs.launchpad.net/heat/+bug/1503955, please ping shardy or any core-reviewer 07:50:30 Launchpad bug 1503694 in heat "A bad or out-of-range value was supplied:The Resource (0) could not be found in Stack" [High,Triaged] - Assigned to Steven Hardy (shardy) 07:50:32 Launchpad bug 1503180 in heat "functional.test_autoscaling.AutoscalingGroupUpdatePolicyTest heat_integrationtests.common.exceptions.StackBuildErrorException" [Medium,Confirmed] - Assigned to Rabi Mishra (rabi) 07:50:33 Launchpad bug 1503955 in heat "functional.test_validation.StackValidationTest.test_stack_validate_provider_references_parent_resource" [Medium,Confirmed] - Assigned to Rabi Mishra (rabi) 07:51:16 one more thing 07:51:22 need to update https://etherpad.openstack.org/p/heat-reviews 07:51:26 #link https://etherpad.openstack.org/p/heat-reviews 07:51:56 looks like it obsolete 07:52:52 if there is nothing else, we may finish 07:53:27 +1 07:53:43 ok. thanks all ;) 07:53:47 #endmeeting