08:12:26 <notifatafek> #startmeeting vitrage
08:12:27 <openstack> Meeting started Wed Feb 22 08:12:26 2017 UTC and is due to finish in 60 minutes.  The chair is notifatafek. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:12:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:12:31 <openstack> The meeting name has been set to 'vitrage'
08:12:39 <notifatafek> Today Ifat won't be present, due to a well deserved family vacation, so we will have to do without her
08:13:39 <notifatafek> Hi everyone
08:13:46 <eyalb> \o
08:14:05 <notifatafek> Today's agenda :
08:14:11 <notifatafek> * Status and updates
08:14:25 <nadav> hi
08:14:43 <elisha_r> hi. sorry I'm late
08:14:43 <notifatafek> Hi Nadav.
08:14:51 <notifatafek> Hi Elisha
08:16:09 <notifatafek> So, I'll start an update from danoffek
08:17:32 <notifatafek> Vitrage ID development is almost done. He's fixing remaining tests and woking on last use cases. Afterwards he will push for first review. Hopefully by the end of the week.
08:17:49 <notifatafek> That's it. Any other updates ?
08:18:16 <notifatafek> #topic Status and Updates
08:19:26 <elisha_r> so I'll update for anna
08:20:02 <elisha_r> Anna is working on adding another notifier in Vitrage, that will generate SNMPv2 Traps
08:20:10 <elisha_r> for deduced alarms that Vitrage generates
08:20:47 <elisha_r> Basically, for each alarm that is raised and for each that is disabled, a relevant trap will be generated.
08:21:17 <elisha_r> Since SNMP OIDs are specific to the system you use and the MIBs you have, the configuration of these traps is up to the user
08:21:41 <elisha_r> There will be documentation pushed as part of the feature that details how this can be configured
08:21:54 <elisha_r> and all this should be done by the next IRC meeting, if all goes as planned
08:22:01 <elisha_r> that's it for me
08:22:08 <elisha_r> (well, actually, for anna :) )
08:22:16 <notifatafek> Is it @elisha_r is it going to be manual OID configuration ? Is it going to be something generic ?
08:22:54 <notifatafek> If I was Ifat, I'd say "great work Anna !"
08:24:10 <elisha_r> the OID structure will be defined in a YAML file which defines the OID structure, both for the trap ID and for the content of the trap. Each user will have to add their own list of specific OIDs for the different alarms they raise using vitrage templates
08:25:25 <notifatafek> @elisha_r can it be defined in the Scenarios / actions Template definition when configuring the alarm action itself?
08:27:44 <elisha_r> not at the moment. though that is an interesting idea which we could consider as a next phase. The main reason why we would not do this is that it means that the OIDs for all they alarms are spread throughout multiple vitrage templates instead of being in a centralized location. This distribution will make it more likely to have mistakes, OID overlap etc
08:28:14 <elisha_r> Also it will cause duplication of information, and changing the OID of an alarm will require surveying all the vitrage templates
08:28:23 <elisha_r> so for now we're going for a central location
08:28:34 <notifatafek> @eilsha_r Understood. Thanks for the update,
08:28:57 <elisha_r> sure. anything for you, notifatafek
08:29:23 <notifatafek> So, if there are no other update, I think we can close this meeting for today,
08:29:32 <elisha_r> yup
08:29:54 <notifatafek> Thanks everybody, continue to contribute to make Vitrage better.
08:30:03 <elisha_r> bye
08:30:07 <eyalb> bye
08:30:13 <nadav> bye
08:30:16 <notifatafek> Bye
08:30:20 <notifatafek> #endmeeting