Maryam:
Please see my response below. Regards, Alok Gupta 732-420-7007 MT B2 3D30 [email protected] -----Original Message----- From: SULLIVAN, BRYAN L Sent: Tuesday, November 08, 2016 7:44 AM To: GUPTA, ALOK <[email protected]> Subject: FW: [opnfv-tech-discuss] [doctor][VES][barometer] OVS link status notifications for OpenStack from collectd - Open Questions Can you respond on the list? I'm unsure what the answer should be. Thanks, Bryan Sullivan | AT&T -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Tahhan, Maryam Sent: Tuesday, November 08, 2016 6:52 AM To: [email protected]<mailto:[email protected]> Subject: [opnfv-tech-discuss] [doctor][VES][barometer] OVS link status notifications for OpenStack from collectd - Open Questions Hi Folks For the OVS events collectd plugin we wrote as part of barometer, we are currently sending a notification message from collectd with a level that is set to WARNING for when the link status is detected to be down. AG Response: When an existing link is detected to be down, we should generate a Major Severity Fault event So this means that when the status changes from "Unknown" to "down" when a new interface is added a warning message will be generated. AG response: for New Interfaces we do not expect any new events. That will cause lot of noise...since they are not actionable events. So from a Doctor/VES perspective: 1. When do you expect to see a warning message vs an informational message? When the link status only changes from Up to down : AG Response: correct, send a Fault event with Major Severity. 2. Do you want to know when the status changes from unknown to down? AG Response: correct, send a Fault event with Major Severity. 3. Should we allow the notification severity to be configurable for link status? Or should we from a collectd point of view provide you with informational messages only and let you decide a severity? AG response: Please provide fault event with Major Severity BR Maryam _______________________________________________ opnfv-tech-discuss mailing list [email protected]<mailto:[email protected]> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
