Re: [opnfv-tech-discuss] [barometer] VES Heartbeats

2017-11-20 Thread SULLIVAN, BRYAN L (BRYAN L)
OK, here are some thoughts then to consider. * Collectd (or other monitoring frontend) on each host will probably be sending measurements at least every minute or more often (VNFs may have longer cycles but for bare metal hosts I imagine we would want measurements at least every minute).

Re: [opnfv-tech-discuss] [barometer] VES Heartbeats

2017-11-20 Thread GUPTA, ALOK
Bryan: Interesting question. It is similar to getting VNF events from an EMS or OAM vm. The reason and rationale for heartbeat event was to avoid sending pings/queries to the devices but having DCAE analytics capable of analyzing heartbeat and metrics to determine health status of the device

[opnfv-tech-discuss] [barometer] VES Heartbeats

2017-11-20 Thread SULLIVAN, BRYAN L (BRYAN L)
Alok, Thinking about the shared Agent (ves_app.py from Barometer) design, in which we don't need an agent running on each node, but can use a single agent running on the local cloud which aggregates VES events from the Kafka bus, it brings up the question of how heartbeats are supposed to work