14:00:12 <ricolin_> #startmeeting heat
14:00:13 <openstack> Meeting started Wed Jun 20 14:00:12 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:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:16 <openstack> The meeting name has been set to 'heat'
14:00:19 <ricolin_> #topic roll call
14:00:56 <ramishra> hi
14:01:03 <ricolin_> o/
14:01:11 <zaneb> o/
14:01:23 <strigazi> o/
14:01:52 <ricolin_> #topic adding items to agenda
14:01:54 <ricolin_> #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282018-06-20_1400_UTC.29
14:03:25 <ricolin_> #topic Auto healing: Heat integrated with Vitrage
14:03:33 <ricolin_> #link https://etherpad.openstack.org/p/self-healing-with-vitrage-mistral-heat
14:04:24 <ricolin_> So I'm start talking with Ifat about integrate Vitrage, Mistral and Heat
14:05:15 <ricolin_> would like to have guys help on review the plan
14:05:24 <ricolin_> I put it in Etherpad
14:05:31 <zaneb> interesting
14:06:19 <ricolin_> interesting in join?:)
14:07:00 <ricolin_> the flow from Vitrage looks like this
14:07:00 <ricolin_> A precreated monitor detect host/network failure and send a alarm to Vitrage -> Vitrage deduces that the instance is down (based on the topology and based on Vitrage templates [2]) -> Vitrage triggers Mistral to fix the instance -> application is recovered
14:07:25 <ricolin_> And we been discuss from Summit about use Heat to wrap all
14:07:28 <ramishra> isn't this similar to the auto-healing stuff we've other than the source of the alarm vitrage
14:08:22 <zaneb> ramishra: sounds like it
14:08:33 <ramishra> So we just have to do add the vitrage resources, no?
14:09:04 <ricolin_> ramishra, similar, but some different, Vitrage can get alarm from external monitor with reduce ability to it's a instance error(maybe)
14:09:08 <zaneb> sounds like we will get better alarms out of vitrage than we can get out of Aodh though
14:09:19 <ricolin_> ramishra, in my mind yes
14:10:08 <ricolin_> zaneb, yeah, we use too much Aodh in our template example:)
14:11:04 <ricolin_> Ifat probably will send a ML out to collect more idea on this topic and see what people looking forward to see from this
14:11:31 <ricolin_> if any idea, please help to adding to the etherpad
14:11:55 <ramishra> ricolin_: who's going to work on it? :)
14:12:16 <ricolin_> ramishra, me, if no other interest
14:12:35 <ricolin_> ramishra, Vitrage team will help on create spec for resource
14:12:47 <ramishra> ricolin_: ok, all yours;)
14:12:54 <ricolin_> ramishra, NO~~
14:13:07 <zaneb> lol
14:13:29 * ricolin_ record zaneb said `interesting`!!
14:14:09 <ricolin_> Since most of work are in Heat, I think Vitrage team will help as well
14:14:38 <ricolin_> let's see if the ML will get more guys interest on it
14:14:54 <ricolin_> move on
14:15:05 <ricolin_> #topic StarlingX
14:15:21 <zaneb> ricolin_: http://todayilearned.co.uk/2012/12/04/what-the-british-say-vs-what-they-really-mean/
14:15:26 <ricolin_> ndahiwade, around?
14:15:31 <ndahiwade> hi ricolin_
14:15:41 <ricolin_> ndahiwade, wow!
14:15:50 <ricolin_> ndahiwade, you make it:)
14:15:58 <ndahiwade> yes I did:)
14:16:25 <ricolin_> zaneb, d'oh!
14:16:34 <ndahiwade> I also asked dtroyer to join, maybe he can introduce the stx upstream effort here
14:17:15 <ndahiwade> dtroyer, ^^
14:17:35 <ricolin_> #link  https://storyboard.openstack.org/#!/board/84
14:18:07 <ricolin_> ndahiwade, I create a board to trace those tag with starlingX in heat group
14:18:16 <zaneb> does that board look empty for everyone or just me?
14:18:17 * dtroyer waves
14:18:17 <ricolin_> ndahiwade, so we can trace them all
14:18:22 <ndahiwade> ricolin_, perfect thanks:)
14:18:24 <ricolin_> hi dtroyer
14:18:30 <ramishra> zaneb: I'm with u:)
14:18:37 <dtroyer> Hi all
14:18:50 <ricolin_> wait
14:19:03 <zaneb> oh ho, it showed up
14:19:07 <dtroyer> We are just getting started setting up the upstream process, heat is one of the first
14:19:19 <zaneb> just takes like 1 minute to load!?
14:19:39 <dtroyer> I an still waiting on approval from WRS to publish the individual patch files that this work is going to be based on
14:19:49 <ramishra> I hate storyboard:/
14:19:49 <dtroyer> zaneb: yes, it feels really slow on queries
14:20:02 <zaneb> sounds like a missing index
14:20:26 <dtroyer> SB will be the source of truth for our work, with linkages into the patch files, Gerrit, LP if necessary, etc
14:20:35 <ricolin_> wasn't this slow earlier
14:20:51 <dtroyer> ricolin_: I first noticed it yesterday...
14:21:01 <ramishra> dtroyer: We're reviewing the patches as they come, Is there any other expectation?
14:21:42 <dtroyer> ramishra: no, our intention is to work with the projects using their normal processes
14:22:01 <dtroyer> In this case, the stories will be filed under heat, etc, and tagged with stx-upstream for tracking
14:22:07 <ricolin_> dtroyer, so in long term is stx-heat going to replaced by upstream heat?
14:22:17 <dtroyer> ricolin_: that is the goal, yes
14:22:51 <ramishra> dtroyer: sounds good, I've reviewed a few of them earlier.. Did not know they have something to with stx:)
14:23:12 <ramishra> normal bug fixes
14:23:13 <zaneb> dtroyer: I think that some of the custom resources might be better to just move into a separate repo
14:23:25 <dtroyer> ramishra: does that affect how you would consider it?  not that we want to hide anything, we don't, but just curious
14:23:25 <zaneb> but we can discuss that when we get to it
14:23:39 <ndahiwade> ramishra, I am putting stx_ topic names for those....
14:24:06 <dtroyer> zaneb: that is one of the things that we will look for project teams to help with, how best to deal with things that do not get merged but StarlingX consideres important
14:24:47 <ricolin_> I hear from ndahiwade about the concern of heat upstream is low-latency, if we can get more specific target(with a story to assign), I think we can start this from both way
14:24:52 <ricolin_> dtroyer, ^^^
14:25:18 <zaneb> dtroyer: yeah. I mean, Heat is designed to accept external plugins, so from my perspective those can just live out-of-tree and I wouldn't consider it a fork
14:25:34 <zaneb> I do know that there are some internal changes needed to support those plugins though
14:25:35 <dtroyer> network latency and throughput are what drove a lot of the changes that WRS made to upstream projects
14:25:55 <dtroyer> zaneb: cool, I wasn't sure, thanks
14:25:59 <zaneb> but the ones I've seen I'm fine with in principle (although we may go for a different implementation)
14:26:30 <dtroyer> and that is totally fine.  my only concern is with backward compatibility for existing Titanium users
14:27:01 <zaneb> (I'm thinking in particular about the option to delete newest instead of oldest first on scale down)
14:27:08 <dtroyer> resource names, etc will likely change, but I would like to not surprise users otherwise
14:28:32 <dtroyer> Are there other questions I can answer here?  (I may need to go in a few minutes…)
14:28:35 <ramishra> dtroyer: backward compatibility is a tricky question, IMO we would just treat them as new features if there is any but the best way we would like to implement it
14:29:21 <zaneb> ramishra: yeah, we'll have to consider it case-by-case
14:29:36 <dtroyer> ramishra: it is and I expect we will have a number of judgement calls.  WRS does tell us that a large percentage of their users already have stacks in production so I don't want to just dismiss that without thought
14:29:45 <zaneb> from what I've seen nothing looks insurmountable for Heat
14:30:19 <zaneb> although TBH I haven't bothered to look as deeply as I would if changes were in separate patches instead of one big blob
14:30:46 <dtroyer> zaneb: hopeflly I can show you those really soon.  :) none of them are actually that large
14:31:01 <dtroyer> I think we wound up with about 40 total
14:31:54 <ramishra> I agree with zaneb we would take calls on case-by-case basis
14:32:15 <ricolin_> dtroyer, 40 is reasonable, will be better to point out which of them are important for StarlingX
14:33:14 <dtroyer> ricolin_: WRS considers them all important :)  But yes, we will.  And ndahiwade has the list for the first batch to get things started
14:33:39 <ricolin_> ndahiwade, so you're going to work on this in these few weeks?
14:33:50 <ndahiwade> ricolin_, yes I will
14:34:10 <ndahiwade> I have a few small bug_fixes/changes upstream already
14:34:23 <ndahiwade> I will put in a few more soon
14:34:48 <zaneb> ndahiwade: if you don't mind me asking, what are Intel's long-term plans for you? will you stick around Heat and try to become a core reviewer, or is your mandate limited to getting these patches landed?
14:35:06 <dtroyer> I have asked him to start with a few to let us make sure the process is working before going too far down the list
14:35:27 <ramishra> ricolin_: Not sure, I would probably not have that affecting our decision making process (i.e what's important for StarlingX), though I've not yet fully understood the whole thing.
14:35:41 <ndahiwade> zaneb, For now it is to get these landed..
14:35:59 <zaneb> ok
14:36:07 <ricolin_> ndahiwade, super! let's continue to trace those this week, and maybe talk again next meeting so we know what exactly we're looking
14:36:23 <ndahiwade> ricolin_, sure thanks:)
14:36:27 <dtroyer> zaneb: I am asking our managers to encourage the folks doing this to also get involved in the projects mora than just these patches, it benefits everyone
14:36:43 <zaneb> ++
14:36:45 <ricolin_> ndahiwade, dtroyer and we can also help on onboarding people, we needs more cores:)
14:37:51 <ricolin_> ramishra, good point
14:38:24 <ricolin_> Okay, I think we can move on
14:38:26 <ricolin_> #topic Open discussion
14:38:36 <dtroyer> ok guys, I need to go, let me know if you have any other questions or concerns
14:38:36 <ricolin_> Any stuff to discuss?
14:38:39 <dtroyer> thanks!
14:38:45 <zaneb> thanks dtroyer
14:38:45 <ricolin_> dtroyer, thx!
14:38:48 <ndahiwade> thanks dtroyer :)
14:39:02 <zaneb> ndahiwade: welcome, btw :)
14:39:16 <ndahiwade> haha Thanks guys:)
14:39:53 <zaneb> always happy to have bug fixes
14:39:54 <ricolin_> ndahiwade, zaneb also in US too, so feel free to use irc to ping us:)
14:40:13 <ndahiwade> ricolin_, sure:)
14:40:14 <zaneb> doubly happy to have bug fixes that have been tested in production by real users
14:40:52 <ramishra> zaneb: I was wondering why they did not propose these bug fixes upstream earlier. No upstream first policy I suppose:)
14:40:54 <ricolin_> zaneb, that's what we needed the most
14:41:19 <zaneb> ramishra: yup :/
14:41:57 <ricolin_> Okay, anything else?
14:43:06 <ricolin_> If none, we can end the meeting now and let guys back to work, or back to sleep:)
14:43:19 <ramishra> ricolin_: thanks!
14:43:21 <zaneb> or both!
14:43:25 <zaneb> ;)
14:43:28 <ricolin_> lol
14:43:29 <ndahiwade> ricolin_, thanks again!
14:43:32 <ricolin_> thx all
14:43:35 <ricolin_> #endmeeting