>On Wed, Jun 07, 2017 at 05:14:58PM +0100, Bhanuprakash Bodireddy wrote: >> This commit adds new ovsdb column "keepalive". It shows the overall >> datapath status and the health of the cores running datapath threads. >> >> Signed-off-by: Bhanuprakash Bodireddy >> <[email protected]> > >I'm a little uncomfortable with having OVS report that it's nonfunctional. If >it's >dead, then from my point of view the most natural response would be to call >abort(), to let the monitoring process restart it and presumably fix the >problem. What's the guiding philosophy here?
Hello Ben, In some scenarios its correct to let the monitoring process instantly restart the OvS in case of failures. However, as part of OPNFV Barometer project, key KPI statistics are exposed to monitor the health of computes. This includes CPU, Memory, Cache utilization, Link status, packet statistics, Networking MIBS etc. vSwitch health is most important and the same is exposed with KA patches to monitoring apps like collectd, which internally relays the information to OpenStack service Ceilometer. As you are aware Ceilometer only collects the events and metering data and isn't entitled to take any decisions. In case of vSwitch issue, based on the criticality of the failure and also considering other KPIs from compute, fault management services like 'Doctor' can take actions to migrate the VNFs to other compute and further mark the compute node as offline so that nova wont schedule VMs on this problematic compute. - Bhanuprakash. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
