08:00:20 <ifat_afek> #startmeeting vitrage
08:00:21 <openstack> Meeting started Wed Dec 20 08:00:20 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:24 <openstack> The meeting name has been set to 'vitrage'
08:00:29 <ifat_afek> Hi :-)
08:00:41 <Liat> :-)
08:04:48 <ifat_afek> dwj: Hi, it seems like it’s just us today… we are only two people from Nokia (there is a holiday in Israel so many people are on vacation)
08:05:15 <ifat_afek> Do you have anythink you want to discuss? I prepared a meeting agenda, but I’m not sure if we should hold the meeting at all
08:05:29 <dwj> Yujunz also here. :)
08:05:39 <yujunz> hi
08:05:42 <ifat_afek> yujunz: Hi! so now we are four people :-)
08:06:02 <ifat_afek> So I’ll start
08:06:33 <ifat_afek> #topic Status and Updates
08:07:06 <ifat_afek> My updated: I am still working on the execute-mistral refactoring… I was on vacation in the beginning of this week, but I really hope to push my change today
08:07:36 <ifat_afek> My change will include: support for per-version validation and loading of the templates + refactoring of the execute-mistral syntax
08:07:49 <ifat_afek> Most of the change is around the version support
08:08:02 <ifat_afek> That’s it for me
08:08:21 <yujunz> My updates.
08:08:29 <yujunz> Draft a blueprint about suspect alarm
08:08:39 <yujunz> #link https://review.openstack.org/#/c/519250/
08:08:50 <yujunz> And fixed some document building issues.
08:09:30 <ifat_afek> I’ve seen the suspect alarm blueprint. I still want to think over about the suspect state and how to represent it. And I’d like eyalb and idan_hefetz to review it as well, but they are on vacation
08:10:08 <ifat_afek> And thanks for the document fixes. Are they all related to the latest doc-build change?
08:10:41 <yujunz> The latest two are addressing the new build job
08:11:11 <yujunz> To keep the local build job consistent with openstack infra
08:11:15 <ifat_afek> Great, thanks. I actually didn’t understand that there was a need for us to do anything
08:12:20 <yujunz> No, we don't need to do it to make the build job work. It just help when the build job fails and you want to troubleshoot it locally.
08:12:35 <ifat_afek> That’s also a good idea :-)
08:13:32 <yujunz> The other two are encountered by myself while drafting the suspect alarm blueprint.
08:13:34 <yujunz> So I spent a few minutes to fix them.
08:13:58 <ifat_afek> Thanks
08:14:10 <yujunz> Next I will validate the proactive fault model against some common use cases.
08:14:27 <ifat_afek> Sounds good. Will it belong to one of the blueprints?
08:15:21 <yujunz> Hard to decide where to put them. Maybe the outcome would be a design document in vitrage/docs, not a blueprint in vitrage-specs
08:15:49 <ifat_afek> That could also work. We have a few of those already
08:16:05 <yujunz> That's all from me
08:16:41 <dwj> My update: I start to do the task: support Vitrage in Apex(TripleO),  and I send email to apex team to ask the progress/plan as they have an assignee to take over the integration task in April, but no response yet.
08:17:03 <dwj> In parallel, I start to learn how to integrate with TripleO. So complex,maybe we need to add some modification in several repos.such as: puppet-triplo, tripleo-heat-template, tripleo-puppet-elements and so on
08:18:01 <dwj> I haven't clear up the whole workflow......
08:18:19 <ifat_afek> Thanks for taking these tasks. Are they related to one another? I somehow understood that we could do the TripleO first and then Apex should be easy. But I’m not sure that I understood correctly
08:18:49 <ifat_afek> And I don’t think that there is someone else in our team that knows more about these installations
08:19:24 <dwj> Yes, Apex use the repos from TripleO, so we need to do the TripleO first
08:20:33 <ifat_afek> Note that we already have Vitrage rpms in RDO. I’m not sure if it’s related, but maybe…
08:20:53 <dwj> Yes, it's related.
08:21:08 <ifat_afek> Ok, seems like by now you know a lot more than me about this issue :-)
08:21:19 <dwj> As we have Vitrage rpms in RDO, we can start to do the deploy.
08:21:51 <dwj> Not so much. :)
08:21:54 <ifat_afek> And that’s a lot of work?
08:23:26 <dwj> Seems like that because I don't familiar with TripleO. - _ -
08:24:10 <ifat_afek> Ok. Let us know if you need any help. Unfortunately none of us is familiar with TripleO
08:24:56 <dwj> OK, thanks~
08:25:11 <ifat_afek> Any other updates by anyone?
08:27:28 <ifat_afek> #topic Queens releaes
08:27:38 <ifat_afek> #topic Queens Release
08:27:50 <ifat_afek> A reminder about the Queens release timeframe:
08:28:05 <ifat_afek> The release deadline for python-vitrageclient: January 25
08:28:18 <ifat_afek> This week is also declared as the “feature freeze”, although we are not committed to it (as we are following the cycle-with-intermediary release model).
08:28:26 <ifat_afek> The release candidate deadline is February 5-9
08:28:50 <ifat_afek> Here is the etherpad with our roadmap:
08:28:55 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-ptg-queens
08:29:19 <ifat_afek> A few updates in the etherpad:
08:29:43 <ifat_afek> (Must) Move tempests tests to a separate repository - in progress by chandankumar
08:30:39 <ifat_afek> (Must) Support Networkx 2.0 - I need to email openstack-dev and check if it really is a must. Depends whether they plan to chagne networkx version in the global requirements
08:31:15 <ifat_afek> (Very Important) Make sure all existing tests run in the gate - I believe this is done, but need to check with idan_hefetz
08:31:42 <ifat_afek> (Very important) Configurable notifications API  - the task has moved to nivo, and it’s in progress
08:32:31 <ifat_afek> (Very Important) HA - Muhamad Najjar already implemented the event persistor, and he is now working on persisting the graph snapshots
08:32:37 <ifat_afek> So it’s also in progress
08:33:04 <ifat_afek> (Medium) Template CRUD
08:33:11 <ifat_afek> nice progress by idan_kinory
08:34:03 <ifat_afek> And latest news - the Congress PTL, Eric Kao, emailed me regarding the Vitrage-Congress integration. He seems to be interested in pushing this forward
08:34:15 <ifat_afek> That’s it on my side, I’ll now update the etherpad itself
08:34:46 <yujunz> I have updated the etherpad. Put a brief record in IRC as well
08:35:06 <yujunz> [pending] Template simplification
08:35:06 <yujunz> [in progress] Suspect status
08:35:08 <yujunz> [not started] Diagnostic action
08:35:32 <yujunz> [pending] Equivalence and aggregation
08:36:06 <yujunz> So we get started with suspect status
08:36:33 <yujunz> The two pending items has already a draft blueprint
08:36:45 <yujunz> Will update after we validate the common use cases
08:36:57 <yujunz> That's it on my side.
08:38:18 <ifat_afek> Ok. So I think that for Nokia’s task we are in good state. The only thing that I’m not 100% sure about is the HA. But I believe it can be done for Queens.
08:39:24 <ifat_afek> Another issue related to the release: the TC introduced the concept of “release highlights”.
08:39:32 <ifat_afek> In every version that we release we should write, in addition to the release notes, some short highlights about the version.
08:39:39 <ifat_afek> I plan to check what other teams are writing and then we should decide about our own highlights.
08:39:44 <ifat_afek> #link http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html
08:40:21 <yujunz> #info Cycle highlights: Journalists, product manager, and others
08:40:25 <yujunz> Is it about this?
08:40:53 <ifat_afek> Could be… where did you copy it from?
08:41:15 <yujunz> From your link :-)
08:41:22 <ifat_afek> The idea is that “PTLs will not be asked over and over again about the cycle highlights”
08:41:29 <ifat_afek> :-)
08:41:47 <ifat_afek> I don’t fully understand what’s the difference betewwn the highlights and the release notes
08:41:54 <ifat_afek> So I’m waiting to see what others are doing
08:42:04 <yujunz> #info Release notes:    End user and deployer documentatio
08:42:09 <yujunz> The audience is a bit different
08:42:19 <yujunz> Highlights is more for marketing
08:42:41 <ifat_afek> So we need to consult a marketing person about the content ;-)
08:44:21 <ifat_afek> Last issue: I believe that most IRC meetings will be canceled next week due to the holidays. In Israel we are working as usual, so we can either hold the meeting or cancel it like anyone else. What do you say?
08:45:32 <yujunz> We have a team building next Wednesday
08:45:40 <ifat_afek> What does it mean?
08:45:43 <yujunz> dwj and me won't be available for the meeting
08:45:56 <ifat_afek> Ok, so let’s cancel it. I’ll send an email about it
08:47:14 <ifat_afek> #topic Open Discussion
08:47:21 <ifat_afek> Anything else?
08:47:44 <yujunz> Is the PTG schedule settled?
08:48:15 <ifat_afek> I didn’t even prepare an etherpad yet, because it’s only in February… I can create one so people can start writing their ideas
08:49:32 <yujunz> And people? How many from vitrage team plan to attend?
08:49:36 <ifat_afek> Ok, so here is the link:
08:49:43 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-ptg-rocky
08:49:52 <ifat_afek> It’s still empty, I’ll write a few lines
08:50:12 <ifat_afek> From Nokia it seems like only Yuval Adar will travel to Dublin, and the rest of us will join remotely
08:50:40 <yujunz> OK, I see. Thanks.
08:50:44 <ifat_afek> We’ll adjust the schedule so it will match Shaghai time as much as possible. Israel time is similar so that’s not an issue
08:51:11 <ifat_afek> I asked for a room for 3 days, so we’ll have 3 mornings for meetings with Shanghai. I’m not sure if we need 3 full days
08:53:08 <ifat_afek> Any other issue?
08:53:13 <yujunz> Nope
08:53:27 <dwj> No
08:53:39 <ifat_afek> Ok, bye then :-)
08:53:47 <dwj> bye~
08:53:49 <yujunz> bye
08:54:02 <ifat_afek> #endmeeting