15:00:21 <ricolin> #startmeeting heat
15:00:25 <openstack> Meeting started Wed Feb 15 15:00:21 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:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:29 <openstack> The meeting name has been set to 'heat'
15:00:41 <ricolin> #topic roll call
15:01:03 <therve> o/
15:01:05 <zaneb> howdy o/
15:01:12 <ramishra> hi
15:01:22 <fengxia41103> hi everyone
15:01:28 <cwolferh> hello
15:02:20 <ricolin> #topic adding items to agenda
15:02:26 <ricolin> #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-02-08_1500_UTC.29
15:03:34 <therve> ricolin, Adding something...
15:03:51 <ricolin> therve: :)
15:04:14 <therve> So that you reload the page
15:04:21 <therve> (We should switch to an etherpad btw)
15:04:38 <zaneb> therve: heh, that's what I was going to add :)
15:04:44 <ricolin> manila cephs one
15:05:00 <ricolin> #topic taging heat-translate
15:05:23 <ricolin> is spzala around?
15:05:57 <zaneb> haven't seen him today or yesterday
15:06:15 <ricolin> amoralej is asking the tag plan for heat-translate project after release
15:06:51 <ricolin> Wonder who is the right person to make that plan?:)
15:07:18 <zaneb> ricolin: maybe email spzala, I think he is the right person to make that plan
15:07:44 <therve> Yeah, he's rarely on IRC AFAICT
15:08:44 <ricolin> sorry, connection break
15:09:15 <zaneb> ricolin: maybe email spzala, I think he is the right person to make that plan
15:09:23 <ricolin> Okey
15:09:29 <ricolin> I think so too
15:09:31 <ramishra> How is it released/tagged? I don't see it in the releases repo.
15:09:41 <shardy> hey all
15:10:09 <ricolin> ramishra: by git push i think?
15:10:19 <ricolin> shardy: hi!:)
15:10:36 <zaneb> therve: he is usually on irc, he pinged me on Monday but I was out & then he hasn't been around for a couple of days
15:10:49 <therve> Hum ok
15:11:33 <therve> zaneb, Oh I didn't know his nick :)
15:12:03 <ricolin> Will find him!
15:12:36 <ricolin> #topic Logo announcement
15:12:43 <ricolin> #link https://www.dropbox.com/sh/kon1k7707ob2mq2/AAAsGHWtln4y8uY9a5YiVMbaa?dl=0
15:13:06 <ricolin> We officially have a new logo
15:13:39 <ricolin> They said there will be stickers in PTG
15:13:48 <ricolin> feel free to use it!!
15:14:07 <zaneb> I guess we're gonna be stuck with the ALL CAPS crowd forever now :/
15:14:38 <zaneb> <3 the logo though
15:14:52 <fengxia41103> cool
15:14:59 <ricolin> zaneb: so true!
15:15:19 <ricolin> #topic https://review.openstack.org/#/c/434030/ ocata backport
15:15:39 <therve> So yeah a small change to the manila resource
15:15:59 <zaneb> ramishra: what is the status of the Ocata release?
15:16:21 <zaneb> are we still in RC?
15:16:25 <ramishra> zaneb: it's done
15:16:39 <therve> We're in rc1
15:16:51 <ramishra> We are not doing rc2
15:16:55 <ramishra> so it's final
15:17:21 <zaneb> can we change our mind?
15:17:21 <therve> OK so I guess this patch is out?
15:17:52 <zaneb> I tend to agree with tiantian that this should not go in after the release
15:17:58 <therve> ramishra, https://review.openstack.org/#/c/430056/ what about that one?
15:18:21 <zaneb> otoh this is a zero-risk change that I have no objection to going in *before* the release, even if it is arguably a feature
15:18:32 <shardy> IMO it's not a feature, but it is an interface change so probably can't be backported unless we're willing to do an RC2 before the GA
15:18:35 <ramishra> therve: That's normal backport to stable
15:18:45 <zaneb> shardy++
15:19:02 <shardy> personally I'd favor just tagging an RC2, particularly if there's anything else waiting around for backport
15:19:11 <therve> Hum
15:19:12 <zaneb> ditto
15:19:14 * shardy would say that though as TripleO needs it ;)
15:19:19 <therve> ramishra, https://review.openstack.org/#/c/431868/ got merged too
15:19:48 <therve> It's a bit weird to release ocata with changes in the pipeline. It feels releases are slightly cheaper that time than later on
15:20:30 <ramishra> therve: none of those changes are critical, I mean we can surely backport those biugs
15:20:46 <ramishra> therve: if we want rc2 we can do it though
15:21:04 <therve> ramishra, What's the argument against not doing it?
15:21:36 <zaneb> therve: you mean the argument *for* not doing it?
15:21:41 <ramishra> therve: I don't have one against, unless we agree that there is one for it
15:21:49 <therve> zaneb, Yes :)
15:22:48 <therve> I think it's worth doing, we can merge the 2 pending patches and make rc2
15:22:49 <zaneb> the argument for doing rc2 is that we have this Manila feature which is inaccessible to users, and if we don't do an rc2 then they'll have to wait until Pike to get it
15:22:52 <therve> That's very low risk
15:22:58 <shardy> To be clear, not backporting https://review.openstack.org/#/c/434030 does have a significant user impact if you care about using manila with ceph
15:23:08 <ramishra> zaneb: I don't see that as a feature though
15:23:16 <therve> zaneb, I think ramishra says that we can merge it in stable later on
15:24:07 <shardy> ramishra: I think the problem is we shouldn't really change constraints for a stable release
15:24:43 <ramishra> ok, then, if we all agree, I can do an rc2
15:24:56 <ricolin> rc2 sounds like the way to go, do we have any other patches also require to taget beside these two?
15:25:01 <zaneb> yes, we generally try to avoid creating interoperability problems between clouds running the same version of heat
15:26:07 <shardy> erm.. on an unrelated note, how do folks feel about landing https://review.openstack.org/#/c/434185/ to newton? :)
15:26:27 <zaneb> ramishra: just +2'd https://review.openstack.org/#/c/430056/1 - I'll let you approve
15:26:46 <shardy> If we can't do that I'll have to block a bugfix backport for TripleO, but it does very slightly relax the map_replace interface
15:27:18 <ramishra> zaneb: sure, let's land some of the ocata patches and I'll tag rc2 tomorrow
15:29:15 <therve> ricolin, We're good!
15:29:35 <ricolin> #topic federation and trusts
15:29:46 <lbragstad> o/
15:29:52 <ricolin> it's yours
15:30:10 <lbragstad> hi folks - i'm in the middle of scheduling sessions for the PTG next week
15:30:27 <lbragstad> curious if heat is still interested in a session on federation
15:30:41 <lbragstad> and if so - what times work best for your team?
15:31:29 <ramishra> lbragstad: we are definitely interested. Is this a cross-project session?
15:31:57 <lbragstad> ramishra well - I can schedule it in one of the cross-project rooms
15:32:09 <lbragstad> #link https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms
15:32:25 <ricolin> #link https://etherpad.openstack.org/p/heat-pike-ptg-sessions
15:32:34 <lbragstad> but I'll need to know how many contributors will be there from heat
15:32:35 <ricolin> I do have a draft schedule here
15:33:01 <ramishra> lbragstad: Tuesday would probably be good, we've heat sessions from Wed-Fri
15:33:16 <ricolin> we can do it in Morning of Wed-Fri
15:33:36 <lbragstad> ramishra we will only have a few contributors in town on Tuesday - most of us will be in transit then :(
15:34:09 <ricolin> just not 11-12 of Wed-Thu
15:34:31 <lbragstad> would right away at 9am on wednesday work?
15:34:33 <lbragstad> for an hour?
15:34:48 <therve> Nope
15:35:00 <lbragstad> thursday?
15:35:20 <lbragstad> 9:00 - 9:50 on thursday*
15:35:34 <therve> We linked our schedule FWIW :)
15:36:23 <ricolin> We do can move some inner session to make the room
15:37:07 <lbragstad> yeah - most of your morning look full, i'm not seeing much on wednesday afternoon?
15:37:09 <ricolin> will 9:00 - 9:50 on thursday* works for all?
15:37:12 <lbragstad> mornings*
15:37:57 <ramishra> ricolin: so you plan to move py3 support session to a different solt?
15:37:59 <ricolin> Let's do it than:)
15:38:09 <EmilienM> o/
15:38:30 <ricolin> yes, if we do trust session
15:38:43 <shardy> I'd like to be included in the session, so if we can avoid any of the TripleO sessions with my name assigned, that would be good:
15:38:46 <shardy> https://etherpad.openstack.org/p/tripleo-ptg-pike
15:39:40 <therve> OK let's do thursday morning
15:40:28 <ricolin> Ok
15:40:30 <lbragstad> how many heat/tripleo contributors do you expect to be there for that particular discussion?
15:40:36 <shardy> If EmilienM agrees we could possibly use some of the Heat-Mistral-TripleO session, provided we don't need the whole time to discuss Federation
15:41:00 <shardy> lbragstad: well primarily me because I worked on the initial trust integration for Heat, but am now more involved with TripleO
15:41:03 <EmilienM> that or create a new shared session
15:41:22 <shardy> lbragstad: but I'm sure other folks will be interested (including the Mistral folks, who also use trusts, or plan to, IIRC)
15:41:33 <shardy> EmilienM: yeah, that might be best if we can find a convenient time
15:41:38 <lbragstad> shardy good to know
15:42:40 <EmilienM> tbh, I'll let you decide what you like
15:42:48 <EmilienM> our agenda is pretty flexible and I haven't heard about much constraints yet
15:43:03 <shardy> ricolin: I can do the first session on Thursday, I can probably skip the performance profiles session if needed
15:43:10 <shardy> if that time works for everyone else
15:43:13 <EmilienM> so feel free to pick a slot on https://etherpad.openstack.org/p/tripleo-ptg-pike and create a new session with heat folks
15:43:28 <ricolin> shardy: nice:)
15:43:50 <lbragstad> I'll schedule a room for 9:00 - 9:50 on thursday in Savannah?
15:43:53 <EmilienM> shardy, ricolin, please look on Thursday, we have a free slot at 16:10 - 17:00
15:43:58 <ricolin> lbragstad: could you please kindly reserve the room?:)
15:44:23 <shardy> EmilienM: could we move the performance profiles one to there?
15:44:24 <ricolin> lbragstad: also a ML will be great:)
15:44:27 <lbragstad> We can use some of that time for federation and trusts, if we end early, heat/mistral/tripleo can use the room for additional discussions
15:44:33 <EmilienM> shardy: please do it
15:44:35 <shardy> then we have no conflict with this proposed heat/keystone session
15:44:46 <shardy> EmilienM: ack, will do, thanks!
15:44:52 <EmilienM> shardy: feel free to update the etherpad at your convenience
15:45:42 <ricolin> ok:)
15:45:50 <ricolin> #topic PTG Schedule discuss
15:45:53 <shardy> EmilienM: done
15:45:58 <shardy> lbragstad: sounds good, thanks!
15:46:00 <ricolin> keep scheduling!
15:46:20 <ricolin> #link https://etherpad.openstack.org/p/heat-pike-ptg-sessions
15:46:32 <ricolin> so we have three cross project settle
15:46:38 <lbragstad> shardy ricolin done - https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms I'll send a note out a little later today with some more information
15:47:16 <ricolin> heat feed back, openstack orchestration, and keystone one:)
15:47:26 <ricolin> lbragstad: thanks!!!
15:48:04 <ricolin> Any idea on the draft schedule in etherpad?
15:48:30 <ricolin> besides 23 morning?:)
15:49:14 <ricolin> Nice :)
15:49:40 <ricolin> I will update the schedule later
15:49:57 <ricolin> #topic Open discussion
15:51:00 <ricolin> I'm thinking maybe we should block the wait condition test for now till we fix it?
15:51:09 <shardy> thanks ricolin, lbragstad - I'll also pass details to the mistral team, as I think they will be interested
15:51:24 <lbragstad> shardy awesome
15:51:47 <ricolin> shardy: thx:)
15:52:41 <therve> ricolin, The signaling one?
15:52:45 <ramishra> ricolin: +1, that test does not do anything other than testing that broken functionality
15:52:48 <ricolin> therve: yes
15:54:12 <therve> 6% failure rate
15:54:16 <therve> (http://status.openstack.org/openstack-health/#/job/gate-heat-dsvm-functional-convg-mysql-lbaasv2-ubuntu-xenial)
15:54:20 <therve> A bit annoying indeed
15:54:29 <zaneb> ricolin: maybe just crank down the number of signallers, rather than disabling the whole test?
15:54:53 <ricolin> zaneb: okey, I can do it
15:55:17 <ricolin> and if it's not working we can discuss this again in PTG
15:55:46 <therve> #link http://status.openstack.org/openstack-health/#/test/heat_integrationtests.functional.test_os_wait_condition.OSWaitCondition.test_create_stack_with_multi_signal_waitcondition
15:55:54 <therve> A good URL to check over time
15:56:25 <therve> It got much worse the past month
15:57:09 <ramishra> the multiple signal 6 is misleading, actually the reason text for signal with id 5 is updated when the duplicate signal is received
15:59:26 <ricolin> Okey, Time's up. Let's move back to heat. We will definitely discuss this more in PTG...
15:59:38 <ramishra> I would think we can enable the test when it's fixed rather than changing the test, but if that can help reducing the failures...
15:59:42 <ricolin> Thanks guys for join!!
15:59:42 <shardy> see you next week everyone
15:59:49 <ricolin> #endmeeting