08:00:37 #startmeeting vitrage 08:00:38 Meeting started Wed May 17 08:00:37 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:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:43 The meeting name has been set to 'vitrage' 08:00:53 Hi :-) 08:01:02 Hi 08:01:05 Hi Everyone! 08:01:18 Hi! 08:01:20 Hello 08:04:30 #topic Boston Summit recap 08:04:43 I think that the Boston summit was very successful for Vitrage. IMO, the most important activities were the hands-on lab and the ongoing demos in Nokia’s booth. 08:05:14 A list of our sessions: 08:05:20 #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18067/get-hands-on-with-vitrage-the-fault-management-service-for-root-cause-analysis-and-deduced-alarms 08:05:29 #link https://www.openstack.org/videos/boston-2017/beyond-automation-taking-vitrage-into-the-realm-of-machine-learning 08:05:41 #link https://www.openstack.org/videos/boston-2017/intel-collectd-and-vitrage-integration-an-eventful-demo 08:05:47 \o/ 08:05:53 #link https://www.openstack.org/videos/boston-2017/collectd-and-vitrage-integration-an-eventful-presentation 08:05:58 #link https://www.openstack.org/videos/boston-2017/the-vitrage-story-from-nothing-to-the-big-tent 08:06:05 #link https://www.openstack.org/videos/boston-2017/advanced-use-cases-for-root-cause-analysis 08:06:11 #link https://www.openstack.org/videos/boston-2017/project-update-vitrage 08:06:18 #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18799/vitrage-usability-and-new-insights-where-do-we-go-next 08:06:24 I’ll send a summit recap email in the coming days. 08:06:37 Wonderful 08:07:34 #topic Status and Updates 08:07:45 Not much on my side. I’m spending most of my time responding to emails that I missed… 08:08:27 Other than that, I guess you noticed the interesting discussions on our mailing list, about monitoring Nova heartbeat and pushing the alarms to Vitrage 08:08:49 That’s it for me. Anyone else wants to update? 08:09:04 A quick update 08:09:39 there is a small problem in the gate at the moment. Hopefully will be fixed today. 08:10:27 Anyone else? 08:10:40 I will 08:10:54 Proposed the change of entity equivalent during summit 08:11:05 A bit messed up today during rebasing. 08:11:38 Since the patches have dependency, I would suggest to review them in time order 08:11:59 But it would be good to look at all of them to have a complete understanding. 08:12:18 OK. You mean by the time you first submitted each patch? 08:12:35 Yes, by the submit time 08:12:45 Ok, I’ll do it today 08:12:52 Document -> loading -> refactoring -> building 08:12:59 In this order 08:12:59 Did you finish the coding, or is anything left? 08:13:13 Nothing left on my side 08:13:31 Great 08:13:37 And sorry again for the delay in our reviews 08:13:38 The refactoring is submit for building scenario dynamically 08:14:01 I’m not so familiar with the scenario loading. What do you mean by that? 08:14:10 Loading equivalence 08:14:26 Makes sense 08:14:36 That one was simple and safe to merge. No affect on current function 08:15:24 OK 08:15:32 Anything else? 08:15:58 That's it 08:16:32 Thanks. Anyone else wants to update? 08:18:31 Short meeting today :-) 08:19:15 Bye, see you next week 08:19:19 Bye 08:19:22 bye 08:19:28 bye :) 08:19:32 bye 08:19:46 #endmeeting