09:00:28 #startmeeting vitrage 09:00:30 Meeting started Wed Mar 9 09:00:28 2016 UTC and is due to finish in 60 minutes. The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:33 The meeting name has been set to 'vitrage' 09:00:39 Hi everyone :-) 09:00:58 Hi all! 09:01:02 hi 09:01:17 hello! 09:01:23 Hi 09:01:30 hi all :) 09:05:09 #topic Current status 09:05:17 I'll start with aodh 09:05:37 Last week I finished writing the two aodh blueprints, for snapshot plugin and notifier. 09:05:45 I joined ceilometer IRC meeting and asked them to review it. They seemed interested, but didn’t review our blueprints yet 09:05:55 #link https://review.openstack.org/#/c/287686/2/specs/mitaka/synchronizer-aodh-get-all.rst 09:06:01 #link https://review.openstack.org/#/c/287861/2/specs/mitaka/aodh-notifier.rst 09:06:14 I started the implementation of aodh plugin. Basic implementation is working, but the alarms are still not connected to resources 09:06:25 First, Graph Notifier blueprint still requires some integration with the Evaluator, and will be closed soon. 09:07:10 Second, regarding Aodh-Notifier blueprint, i will share my design later on today 09:07:49 we had some advances with bus notifications, that will make it easier to implement 09:08:13 hi 09:08:41 idan_hefetz: cool 09:09:07 Ohad and I are preparing to the hackfest next week. And we are all working on preparing a demo 09:09:53 My part is of course to make sure nagios and aodh work 09:10:18 Other news: We got a comment to monasca blueprint from Roland Hochmuth, their PTL. They plan to implement something that will help us in the integration 09:10:24 #link https://review.openstack.org/#/c/253920/ 09:12:30 monasca told me that that they started working on a feature for periodic notification 09:12:38 which can be good for us 09:12:56 I also added a readme file for the vitrage client 09:13:00 thats all 09:13:16 eyalb: I saw it, thanks. already added a link to this page in our wiki 09:13:26 who wants to update next? 09:14:10 I will update, for me and elisha_r 09:14:46 we are at the very last stages of finishing the evaluator, end to end 09:15:52 should have the set_state and rca actions supported by the end of the day, and the raise_alarm as well, though without the support of the notifier which is still in development 09:16:32 we will also add several initial templates into the default vitrage deployment. 09:16:37 that's it for now. 09:17:41 lhartal: great!! 09:18:22 so you mean we will see the deduced alarms in vitrage tree, but not in external sources like aodh (since the notifier is not finished yet) 09:18:24 ? 09:21:15 yes - right now we will see the Vitrage alarms only in Vitrage graph. Also, as I wrote, The AODH notifier is in developing stage so in the mear future we will be able to see deduced alarms in AODH 09:21:44 but once you are done, we will see them in the UI, right? 09:22:33 yes, in the alarms screen. 09:22:43 this is great 09:22:54 who wants to update next? 09:23:24 I will update 09:23:47 I have finished to work on the states and they are working. 09:24:07 Now i am preparing 2 environments for the demo for OPNFV 09:24:43 Due to that I am working on the integration of all the parts in Vitrage 09:24:58 alexey_weyl: great, thanks 09:25:33 I will update for Alon 09:25:40 omer_etrog: maybe you can update? 09:25:57 :-) 09:26:32 He add new icons and colors according to the alert severity 09:27:36 We are supporting @alexey_weyl in the installation 09:28:40 and I`m done 09:28:55 omer_etrog: thanks 09:29:25 noam_bloom is not here today. I know that he finished the first part of plugins loading from conf file, but still has some work to do 09:29:41 any other updates anyone? 09:30:24 ok, moving on 09:30:29 #topic Review action items 09:30:40 1. ifat_afek update aodh blueprints 09:30:46 this is finally done :-) 09:30:53 2. define what information that should appear in the alarms list 09:31:18 not done yet. we should do it once we see nagios alarms, aodh alarms and vitrage alarms together. hopefully today 09:31:26 #action define what information that should appear in the alarms list 09:31:41 3. eyalb_ copy vitrage API documentation to the developer guide 09:32:28 yes still need to do it 09:32:36 I did it for the cli 09:33:20 eyalb: ok, thanks. you also documented the api in the blueprints, which are still open because we hope to get external reviews 09:33:25 moving on 09:33:30 #topic Next Steps 09:34:40 I think that next week we should record a new demo with all the cool functionalities - deduced alarms, deduced states and rca 09:35:02 cool - can't wait to see it :) 09:35:49 #action record a demo with deduced alarms, deduced states and rca 09:35:55 anything else? 09:36:17 #topic Open Discussion 09:36:28 anything you want to discuss? 09:39:00 ok, so we're done 09:39:10 bye 09:39:15 Bye bye all 09:39:16 bye everyoen 09:39:17 bye 09:39:19 everyone 09:39:45 #endmeeting