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

[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 (compared to 
currently done via heath-check query to VNF). We had discussed earlier if the 
events coming in can assume if VNF is ok, instead of heartbeat and team felt 
otherwise. Fault and syslog event frequency can vary (you may not receive event 
for hours. If VNF is running smoothly). With Metrics the interval can be long 
(5  mins...15mins)...thus a need for Heartbeat event.
The heartbeat is not from agent but for devices for which data is being send. 
In some cases the entity forwarding the data could determine the health and it 
can create and send a HB event. You said this very well in your email for the 
infrastructure scenario, we may need to proxy the heartbeats for hosts not 
running the agent.

Hope this helps.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com<mailto:ag1...@att.com>

From: SULLIVAN, BRYAN L
Sent: Monday, November 20, 2017 8:55 AM
To: GUPTA, ALOK 
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: [barometer] VES Heartbeats

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 (and what we use them for) 
in the VES design.

Beyond the VNF (presumably by integration of the ONAP VES library into the 
VNF), have you been assuming that the heartbeats represent the health of:

  *   The VES agent
  *   A host (real or virtual, whether running a VES agent or not) from which 
VES events are received

If the latter, we need to consider how the agent can proxy the heartbeats for 
hosts on which there is no agent running, e.g. the agent can keep a host-based 
flag that is set whenever a collectd event is picked up on the Kafka bus during 
the heartbeat period, and send a Heartbeat report for each host at the end of 
the period. But really in that case couldn't DCAE derive that information 
anyway from what it had received? So it calls into question the purpose of the 
heartbeat beyond the VNF itself (the obvious use case) - I just need to clarify 
it.

Thanks,
Bryan Sullivan | AT&T

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [releng] No project folders/yaml files for Models & VES

[GUPTA, ALOK]

Team:

I am working within AT&T to define the yaml onboarding for VES. I should have 
first draft to share with the team by end of this month.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aimee Ukasick
Sent: Monday, February 13, 2017 6:47 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [releng] No project folders/yaml files for Models 
& VES


Hi all - I would like to add the shellcheck call to Models and VES yaml files, 
but there aren't any folders and yaml files for those two projects.
Missing:
releng/jjb/models/models.yaml
releng/jjb/ves/ves.yaml

Can I just commit those files or does some sort of infra configuration have to 
be done in addition to committing those files? If yes, do I submit a ticket to 
opnfv-helpdesk for that?

Thanks in advance for your guidance.


Aimee Ukasick
AT&T Open Source
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor][VES][barometer] OVS link status notifications for OpenStack from collectd - Open Questions

[GUPTA, ALOK]

Maryam:



Please see my response below.





Regards,



Alok Gupta

732-420-7007

MT B2 3D30

ag1...@att.com



-Original Message-
From: SULLIVAN, BRYAN L
Sent: Tuesday, November 08, 2016 7:44 AM
To: GUPTA, ALOK 
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: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam

Sent: Tuesday, November 08, 2016 6:52 AM

To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>

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

opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Notice of intent to participate in OPNFV Danube release

[GUPTA, ALOK]

Team:

VES project intends to participate in the Danube release.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss