Re: [onap-discuss] VES RanMetrics Recommendation

2018-06-19 Thread GUPTA, ALOK
Michela:

We are still in the process of updating the spec. here is the fault domain with 
comments on MO.
1.1.1‘Fault’ Domain Datatypes
1.1.1.1Datatype: faultFields
The faultFields datatype consists of the following fields:
Field

Type

Required?

Description

alarmAdditional Information

hashMap

No

Additional alarm information (note: for SNMP mapping to VES, for hash key use 
OID of varbind, for value use incoming data for that varbind).

alarmCondition

string

Yes

Single word denoting the alarm condition/problem, such as a trap name.  Should 
not have white space (e.g., tpLgCgiNotInConfig, BfdSessionDown, linkDown, etc…)

alarmInterfaceA

string

No

Card, port, channel or interface name of the device generating the alarm. This 
could reflect Managed object. This could be Managed Object.

eventCategory

string

No

Event category, for example: ‘license’, ‘link’, ‘routing’, ‘security’, 
‘signaling’

eventSeverity

string

Yes

Event severity enumeration: ‘CRITICAL’, ‘MAJOR’, ‘MINOR’, ‘WARNING’, ‘NORMAL’. 
NORMAL is used to represent clear.

eventSourceType

string

Yes

Examples: ‘card’, ‘host’, ‘other’, ‘port’, ‘portThreshold’, ‘router’, 
‘slotThreshold’, ‘switch’, ‘virtualMachine’, ‘virtualNetworkFunction’. This 
could be Managed Object Class.

faultFieldsVersion

number

Yes

Version of the faultFields block

specificProblem

string

Yes

Description of the alarm or problem (e.g., ‘eNodeB 155197 in PLMN 310-410 with 
eNodeB name KYL05197 is lost’). 3GPP probable cause would be included in this 
field.

vfStatus

string

Yes

Virtual function status enumeration: ‘Active’, ‘Idle’, ‘Preparing to 
terminate’, ‘Ready to terminate’, ‘Requesting Termination’


Note: Alarm ID for 3GPP should be included (if applicable) in 
alarmAdditonalInformation as alarmId:value.

This information has been included in the excel sheet as well.


Regards,

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

From: Michela Bevilacqua 
Sent: Tuesday, June 19, 2018 12:16 AM
To: GUPTA, ALOK ; kp...@linuxfoundation.org; JI, LUSHENG 
; onap-discuss@lists.onap.org
Cc: Agron, Minerva (Nokia - US/Murray Hill) ; HYNES, 
GERARD W 
Subject: RE: VES RanMetrics Recommendation

HI Alok,
I´ve noticed fault sheet is not updated according to the  agreement reached 
last week during the DCAE meeting.
(i.e. MO and MO instance, 3GPP alarm id).
Are you going to send for review a final update version with VES 6.0 specs  ?
BR
Michela

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of GUPTA, ALOK
Sent: den 15 juni 2018 16:08
To: kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; JI, LUSHENG 
mailto:l...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Agron, Minerva (Nokia - US/Murray Hill) 
mailto:minerva.ag...@nokia.com>>; HYNES, GERARD W 
mailto:gh7...@att.com>>
Subject: [onap-discuss] VES RanMetrics Recommendation

Team:

Please find enclosed an updated ranMetrics Domain for your review and comments. 
This will be included in VES 6.0 Specs.

Please provide feedback by COB Wednesday June 20th, 2014


Regards,

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


-Original Appointment-
From: ONAP Meetings and Events 
mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com>>
Sent: Friday, June 15, 2018 2:03 AM
To: ONAP Meetings and Events; JI, LUSHENG; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Updated invitation: [dcaegen2] Weekly (updated Mar. 13, 
2018) @ Weekly from 6am to 7am on Thursday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)
When: Thursday, June 14, 2018 9:00 AM-10:00 AM America/New_York.
Where: 
https://zoom.us/j/824147956<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_824147956=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=qH2InY7N4f5LLNYo0h9O9HyIkFMcBw29KQjGs2Ah3v4=1mQB4gf965hIc8ROFoKm-46DORal8sS6YR4AffXx78s=>


This event has been changed.
more details 
»<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DdjcycGN2Ym9wdW9vbzRtdHA5MXVlMjRsMWsgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNjQ3YjliZmVjNWYzMDY1YjlmOTE5Yjk2NGZkOTlmZTAwNDEyYmI5YQ-26ctz-3DAmerica-252FLos-5FAngeles-26hl-3Den-26es-3D0=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=l8IPw00BO2wymKUILXPV64hYO5Q4RrwNWmEwo7zSFGg=Gu65QZD9JBb9Mcz2xq14YJDoVbwqB0U_cb467xEeL7Q=>
[dcaegen2] Weekly (updated Mar. 13, 2018)
When

Changed: Weekly from 6am to 7am on Thursday Pacific Time

Where

https://zoom.us/j/824147956<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_824147956=DwQFaQ=LF

Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) (onap-discuss@lists.onap.org)

2018-06-06 Thread GUPTA, ALOK
Bin:

We need SDC ptl on instruction on how and where vnf or vnfc artifact is stored 
in asdc and how it can be retrieved. I know there are groups who are placing 
the yaml artifacts in SDCI think it is on the SDC GUI. I will poke around 
and see if I can find exact steps. For policy gui, I would reach out to Pam 
Dragosh policy ptl.


Regards,

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

From: Yang, Bin 
Sent: Tuesday, June 5, 2018 8:33 PM
To: GUPTA, ALOK ; kp...@linuxfoundation.org; 
lxin...@vmware.com; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)

Hi Alok,

   Great to know that, could you share the pointers to guide me how 
to onboard a VES yaml?  And hence how to fill Policy manually via its GUI? 
Thanks

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: GUPTA, ALOK [mailto:ag1...@att.com]
Sent: Tuesday, June 05, 2018 8:57 PM
To: Yang, Bin; kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; 
lxin...@vmware.com<mailto:lxin...@vmware.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

Bin:

Yes we can onboard VEs yaml files in the sdc. The automation wrt Policy picking 
up the VES yaml to auto populate GUI, I don't belive has been done. So one 
willhave to look at ymal manually and fill the Policy and/or configuration GUI.


Regards,

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

From: Yang, Bin mailto:bin.y...@windriver.com>>
Sent: Monday, June 4, 2018 10:12 PM
To: GUPTA, ALOK mailto:ag1...@att.com>>; 
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; 
lxin...@vmware.com<mailto:lxin...@vmware.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

Hi Alok,

   Appreciate your share the slides again.

   A general question follows: the slide "VES On-Boarding Artifact 
Use" mentioned that vendors/service providers could on-board these VES Artifact 
to SDC for Policy/Close Loop Creation/design, so is there any demo to showcase 
how to do that?

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUPTA, ALOK
Sent: Tuesday, June 05, 2018 8:49 AM
To: kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; 
lxin...@vmware.com<mailto:lxin...@vmware.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

Team:

Please find enclosed presentation used today. Also enclosed is VES summary and 
eventId use cases.

Please feel free to call me if you have questions.


Regards,

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


-Original Appointment-
From: ONAP Meetings and Events 
mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com>>
Sent: Monday, April 23, 2018 8:55 AM
To: ONAP Meetings and Events; lxin...@vmware.com<mailto:lxin...@vmware.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated April 
23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)
When: Monday, June 4, 2018 5:00 PM-6:00 PM America/Los_Angeles.
Where: 
https://zoom.us/j/9057041886<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_9057041886=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=-Q4qYfTGvfr4V5SmgVb4Jwb9OhiyF6z9-yfiLGhZEMQ=y47_CrSGhEHSoaqYrTjOwEnFiWsx1q5C_c8lJekIoIA=>


more details 
><https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DNm9ob2gzY3U4N203cTdkb2Y5dTlobG1ibmsgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNDEyN2

Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) (onap-discuss@lists.onap.org)

2018-06-05 Thread GUPTA, ALOK
Srini:

Please see my responses below.


Regards,

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

From: Addepalli, Srinivasa R 
Sent: Tuesday, June 5, 2018 2:38 PM
To: GUPTA, ALOK ; kp...@linuxfoundation.org; 
lxin...@vmware.com; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)

Hi Alok,

Thank you for the great presentation yesterday at Multi-Cloud meeting.

I have few generic questions (beyond VES) at the ONAP level.

So far (Up to Beijing release),   VES is used by VNFs to send VM level 
statistics (CPU, Disk, Memory, virtual NIC usage).  Since ONAP maintains 
inventory of active VMs and has components for VNF LCM, these statistics can be 
used by closed loop policies to control the VNF LCM.
AG: Correct. One of the first things we do once we receive fault data is to 
enrich the event with both vertical and horizontal topology from A using 
soruceName. The topology helps is with the correlation do determine root cause 
devices/ We can then take closed loop action.
In the excel sheet you have showed,  looks like VES is being extended to 
physical infrastructure (At the NFVI-node level and at the VIM level). I see 
IPMI related statistics/event on per physical server basis and also statistics 
related to various Hardware component features (such as physical NIC, Huge 
pages and many more).
AG: We are expecting to collect metrics from infrastructure defined in the 
measurement domain. I think plan is to update Intel's collectD Pligin (in 
Barometer project) to support data collection and forward it to DCAE Collector.
At this time, ONAP does not have visibility into physical infrastructure and 
mapping of virtual inventory to physical inventory.  So, with current ONAP, it 
is not possible to get actionable insights from these infrastructure statistics 
to control VNF LCM.
AG. We can also update the enrichment microservice to fetch relevant data for 
sources other than A I think A is also planning to have infrastructure 
data (hw level) in future.

Questions/Commentary:

  *   Is the intention to augment ONAP inventory to add physical node inventory 
and mapping to virtual inventory? General concern is here that this may not be 
scalable.  In the "Edge automation project", we are thinking that each Edge 
will do collect the physical inventory level statistics (using 
CollectD-prometheus plugin), store it in timeseries DB (Prometheus Server), get 
the summary/aggregate data (based on some alogirthms/policies,) and send only 
the summarized data to ONAP-Central (VES format).  In that case, the 
information that goes to the ONAP-central is at the site level information, not 
at the physical server level.  What do you think about it?  Our intention is to 
define DM for aggregate data (that also includes aggregate policy information 
applied).
AG: My focus has been on data collection. I know Bryan Sullivan from AT 
)copied on the email) is looking at edge cloud consideration. From my 
perspective A may not keep all the inventory...but must support getting the 
inventory for appropriate data store. Also VES does support internal header 
file that can be expanded to support inventory data from Prometheus Server).

On VES Yaml:  Yesterday, you mentioned that there is a way to create "Closed 
loop policies" from VES Yaml file (currently manually, but in future 
automatically).  Can you provide links to following:

  *   Example VES yaml.
  *   Example closed loop control policies from the example VES yaml.
AG: I had included another presentation on VES which includes the complete DCAE 
architecture to process closed loop. We do have yaml files included on the last 
page and examples in the backup. I would recommend a discussion  with Pam 
Dragosh ptl for policy frame work in ONAP.

Thanks
Srini


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUPTA, ALOK
Sent: Monday, June 4, 2018 5:49 PM
To: kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; 
lxin...@vmware.com<mailto:lxin...@vmware.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

Team:

Please find enclosed presentation used today. Also enclosed is VES summary and 
eventId use cases.

Please feel free to call me if you have questions.


Regards,

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


-Original Appointment-
From: ONAP Meetings and Events 
mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com>>
Sent: Monday, April 23, 2018 

Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) (onap-discuss@lists.onap.org)

2018-06-05 Thread GUPTA, ALOK
Bin:

Yes we can onboard VEs yaml files in the sdc. The automation wrt Policy picking 
up the VES yaml to auto populate GUI, I don't belive has been done. So one 
willhave to look at ymal manually and fill the Policy and/or configuration GUI.


Regards,

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

From: Yang, Bin 
Sent: Monday, June 4, 2018 10:12 PM
To: GUPTA, ALOK ; kp...@linuxfoundation.org; 
lxin...@vmware.com; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org)

Hi Alok,

   Appreciate your share the slides again.

   A general question follows: the slide "VES On-Boarding Artifact 
Use" mentioned that vendors/service providers could on-board these VES Artifact 
to SDC for Policy/Close Loop Creation/design, so is there any demo to showcase 
how to do that?

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUPTA, ALOK
Sent: Tuesday, June 05, 2018 8:49 AM
To: kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; 
lxin...@vmware.com<mailto:lxin...@vmware.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated 
April 23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

Team:

Please find enclosed presentation used today. Also enclosed is VES summary and 
eventId use cases.

Please feel free to call me if you have questions.


Regards,

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


-Original Appointment-
From: ONAP Meetings and Events 
mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com>>
Sent: Monday, April 23, 2018 8:55 AM
To: ONAP Meetings and Events; lxin...@vmware.com<mailto:lxin...@vmware.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Invitation: [multicloud] Weekly Meeting (Updated April 
23, 2018) @ Weekly from 5pm to 6pm on Monday (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)
When: Monday, June 4, 2018 5:00 PM-6:00 PM America/Los_Angeles.
Where: 
https://zoom.us/j/9057041886<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_9057041886=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=-Q4qYfTGvfr4V5SmgVb4Jwb9OhiyF6z9-yfiLGhZEMQ=y47_CrSGhEHSoaqYrTjOwEnFiWsx1q5C_c8lJekIoIA=>


more details 
><https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DNm9ob2gzY3U4N203cTdkb2Y5dTlobG1ibmsgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNDEyN2I3YTllOTQwNWZjM2E3MjMwMDZkMWFhYTNjODZmYjg3ZDU2OA-26ctz-3DAmerica-252FLos-5FAngeles-26hl-3Den-26es-3D0=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=cJWfiBSQUESnMNQIhdmzS0YmmA9VUBvIsu1oe4fI0tU=Eb8yrcriI2tmZLLfLG4CYARxwn8CKCAQlWdt1i7kmUw=>
[multicloud] Weekly Meeting (Updated April 23, 2018)
When

Weekly from 5pm to 6pm on Monday Pacific Time

Where

https://zoom.us/j/9057041886<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_9057041886=DwQFaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=cJWfiBSQUESnMNQIhdmzS0YmmA9VUBvIsu1oe4fI0tU=W8GpL8naZNsbsKSrsk3nMJQ-rSjMdGDDPn6glv4ERG8=>
 
(map<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F9057041886-26sa-3DD-26usd-3D2-26usg-3DAFQjCNFv-5FA97BFH54Z6rs6I8VEHjZhjjRA=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=cJWfiBSQUESnMNQIhdmzS0YmmA9VUBvIsu1oe4fI0tU=7bGBhE9UHqpDi157ILOMTW12rsVupyJkw1hXomw0b-k=>)

Calendar

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>

Who

*

kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> - creator

*

lxin...@vmware.com<mailto:lxin...@vmware.com>

*

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>


IFrom PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/9057041886<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F9057041886-26sa-3DD-26usd-3D2-26usg-3DAFQjCNFv-5FA97BFH54Z6rs6I8VEHjZhjjRA=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=cJWfiBSQUESnMNQIhdmzS0YmmA9VUBvIsu1oe4fI0tU=7bGBhE9UHqpDi157ILOMTW12rsVupyJkw1hXomw0b-k=>

iPhone one-tap (US Toll): +16465588656,,9057041886# or +14086380968,,9057041886#

Telephone:
Dial: +1 646 558 8656 (US Toll) or

Re: [onap-discuss] Invitation: [dcaegen2] Weekly (updated Mar. 13, 2018) @ Weekly from 6am to 7am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 (PDT) (onap-discuss@lists.onap.org)

2018-05-31 Thread GUPTA, ALOK
3DdjcycGN2Ym9wdW9vbzRtdHA5MXVlMjRsMWsgbGppQHJlc2VhcmNoLmF0dC5jb20-26rst-3D3-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNjQ5ZDQyYjg1NmM4MmU0NjU5ZGJkMTM3YzczZmFmMjUwN2M0Yzk0Zg-26ctz-3DAmerica-252FLos-5FAngeles-26hl-3Den-26es-3D0=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8=AOYSFdWqXabMx-IJ-Qqqu-jKaixZZ5EoBqunGHySork=Qysgfq3FstdK2g4OQgOvvSgjE9m0qOhqz6Oc1EQP388=>
 - 
No<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DRESPOND-26eid-3DdjcycGN2Ym9wdW9vbzRtdHA5MXVlMjRsMWsgbGppQHJlc2VhcmNoLmF0dC5jb20-26rst-3D2-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNjQ5ZDQyYjg1NmM4MmU0NjU5ZGJkMTM3YzczZmFmMjUwN2M0Yzk0Zg-26ctz-3DAmerica-252FLos-5FAngeles-26hl-3Den-26es-3D0=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8=AOYSFdWqXabMx-IJ-Qqqu-jKaixZZ5EoBqunGHySork=7zcROn07BuOGdkOuJ4RKHb6fxRHi4caHGm6Ij2ga7s8=>
more options 
»<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DdjcycGN2Ym9wdW9vbzRtdHA5MXVlMjRsMWsgbGppQHJlc2VhcmNoLmF0dC5jb20-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNjQ5ZDQyYjg1NmM4MmU0NjU5ZGJkMTM3YzczZmFmMjUwN2M0Yzk0Zg-26ctz-3DAmerica-252FLos-5FAngeles-26hl-3Den-26es-3D0=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8=AOYSFdWqXabMx-IJ-Qqqu-jKaixZZ5EoBqunGHySork=vjqT1VpuyA2TGhTsBVuE4z-FFMxKqbdIsQWoKP846TM=>



From: "EGAN, ANDREW" mailto:ae3...@att.com>>
Date: Thursday, May 31, 2018 at 9:07 AM
To: ONAP Meetings and Events 
mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com>>,
 "ERICKSON, RICH" mailto:re2...@att.com>>, "DELAPLACE, FRED" 
mailto:fd7...@att.com>>, "JI, LUSHENG (LUSHENG)" 
mailto:l...@research.att.com>>, "CHEN, MIN" 
mailto:mc4...@att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "KELLY, KEN" 
mailto:kk1...@att.com>>
Subject: RE: [onap-discuss] Invitation: [dcaegen2] Weekly (updated Mar. 13, 
2018) @ Weekly from 6am to 7am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 
(PDT) (onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

I cannot connect, zoom just show connecting ☹

--Andy


-Original Appointment-
From: GUPTA, ALOK On Behalf Of ONAP Meetings and Events
Sent: Wednesday, May 30, 2018 3:21 PM
To: ONAP Meetings and Events; ERICKSON, RICH; DELAPLACE, FRED; JI, LUSHENG; 
CHEN, MIN; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
EGAN, ANDREW; KELLY, KEN
Subject: FW: [onap-discuss] Invitation: [dcaegen2] Weekly (updated Mar. 13, 
2018) @ Weekly from 6am to 7am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 
(PDT) (onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)
When: Thursday, May 31, 2018 9:00 AM-10:00 AM America/New_York.
Where: 
https://zoom.us/j/824147956<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_824147956=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=jOKuaqhyGKbhG6DJVSNxIpIx0qrLdEJZ187KCZBNzXw=OyrOhw6PqPh77S8Bt5yN7kZSNmasPmO0icIoGgJ5q7M=>


Team:

Please join tomorrow’s meeting. Erickson will review the VES 6.0 Feedback from 
9 to 9.30AM.

Alok

-Original Appointment-
From: ONAP Meetings and Events 
mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com>>
Sent: Tuesday, March 13, 2018 8:34 PM
To: 'ONAP Meetings and Events'; JI, LUSHENG; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Invitation: [dcaegen2] Weekly (updated Mar. 13, 2018) @ 
Weekly from 6am to 7am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)
When: Thursday, May 31, 2018 9:00 AM-10:00 AM America/New_York.
Where: 
https://zoom.us/j/824147956<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_824147956=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=jOKuaqhyGKbhG6DJVSNxIpIx0qrLdEJZ187KCZBNzXw=OyrOhw6PqPh77S8Bt5yN7kZSNmasPmO0icIoGgJ5q7M=>


more details 
»<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DdjcycGN2Ym9wdW9vbzRtdHA5MXVlMjRsMWsgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNjQ3YjliZmVjNWYzMDY1YjlmOTE5Yjk2NGZkOTlmZTAwNDEyYmI5YQ-26ctz-3DAmerica-252FLos-5FAngeles-26hl-3Den-26es-3D0=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=gqjmGWGHOW_Ih1EBQLb_0xIXluoVAA_hvBexb2lGJk8=lsHI8z6YZ6T8cMDAZM2USywlHcVBidJRal-N1QpvjwM=>
[dcaegen2] Weekly (updated Mar. 13, 2018)
When

Weekly from 6am to 7am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 

Re: [onap-discuss] VES 6.0 Specification for comments feedback

2018-05-14 Thread GUPTA, ALOK
Lingli:

We have VES 5.4.1 that is currently being used for Beijing release. VES 6.0 is 
targeted towards Casablanca. There are some significant performance 
improvement, so We will need to look at version number in header and domains to 
process events for extensible structure i.e. name/value, The domains except 
measurement are same as before. Measurement Metrics were enhanced to include 
infrastructure feedback from VMware and Intel.

We will be updating VES agents in ONAP and expect DCAE team to update the DCAE 
Collector.


Regards,

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

From: 邓灵莉 <denglin...@chinamobile.com>
Sent: Sunday, May 13, 2018 8:33 PM
To: GUPTA, ALOK <ag1...@att.com>
Cc: denghui (L) <denghu...@huawei.com>; Margaret Chiosi (A) 
<margaret.chio...@huawei.com>; Christopher Donley (Chris) 
<christopher.don...@huawei.com>; DRAGOSH, PAM <pdrag...@research.att.com>; 
onap-discuss@lists.onap.org; Xinhui Li <lxin...@vmware.com>; Hellmann, Gil 
<gil.hellm...@windriver.com>; HEKMAT, ARASH <arash.hek...@amdocs.com>; Sumit 
Verdi <sve...@vmware.com>; BLANDFORD, SCOTT <cb1...@att.com>; Andrew Philip 
<aphi...@microsoft.com>; Ethan Lynn <ethanly...@vmware.com>; MORALES RUVALCABA, 
VICTOR <victor.mora...@intel.com>; VUL, ALEXANDER <alex@intel.com>; 
Kanagaraj Manickam <kanagaraj.manic...@huawei.com>; Harwani, Robin 
<harwa...@amazon.com>; Tina Tsou <tina.t...@arm.com>; Avula, Niranjan B 
<niranjan.av...@verizonwireless.com>; fernando.olive...@verizon.com; Draznin, 
Sagiv <sagiv.draz...@verizonwireless.com>; SCAGGS, KEVIN <ks0...@att.com>; 
SKLYAR, IGOR <is8...@intl.att.com>; TOFIGH, TOM <mt3...@att.com>; Mark Scott 
<mark.sc...@ericsson.com>; MOSHENBERG, DAVID <dm6...@att.com>; RATH, 
CHRISTOPHER A <c...@research.att.com>; SULLIVAN, BRYAN L 
<bryan.sulli...@research.att.com>; GUPTA, ARUN <ag7...@att.com>; LU, TINGTING 
<tl2...@att.com>; JANA, RITTWIK <rj...@research.att.com>; POLSTON, STEVE 
<sp2...@att.com>; AGRAHARAM, SANJAY <sa2...@att.com>; Manish Kaushik 
<manish.kaus...@ericsson.com>; ZINNIKAS, MICHAEL J <mz2...@att.com>
Subject: Re: [onap-discuss] VES 6.0 Specification for comments feedback

Hi Alok,


Thanks for sharing this document.


It is great to see it is evolving.


I am curious about the maturity and applicability of these 
requirements/metrics. Are all the specifications aligned with ONAP Beijing 
implementation? Will it be published as part of Beijing documentation or a 
separate one?


Thanks,
Lingli

发自网易邮箱大师
On 05/12/2018 01:01, GUPTA, ALOK<mailto:ag1...@att.com> wrote:
Team:

Please find enclosed VES Listener Requirement 6.0 Draft and VES Registration 
requirement 2.0 Draft. The updates to the requirements include at a high level:

  *   Clarification to questions from previous requirements
  *   Enhanced measurement domain to support multi-vim metrics (contributions 
form VMWare and Intel)
  *   New Domains

 *   Notification,
 *   PNF-registration to support (contributed by Nokia)
I have included a presentation providing details on the changes. The respective 
documents are enclosed as embedded document at the last page of presentation.
We are also working with Nokia and Eriksson to enhance the requirements to 
capture Real Time Performance Monitoring (RTPM) and Bulk Metrics needed for 5G 
RAN and Mobile Core support. They will be published soon.

Please review the requirements and provide your feedback by COB 5/25/2018 and 
we will publish final version by end of the month. If you need to be review the 
changes, please let me know, either I can set up a meeting or attend one of 
your meetings. Please feel free to forward the requirements to others as needed.

Many thanks to contributors and special thanks to Rich Erickson, Min Chen, Fred 
Delaplace for getting the document ready in current form.

Please feel free to call or send email with your questions.


Regards,

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


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


[onap-discuss] Need Feedback: VES Additional Info structure

2018-01-16 Thread GUPTA, ALOK
DCAE ONAP TEAM Members:

We have a request for updating VES additonalInformation Structure in each 
Domain to  get rid of repeating name and value in the additional name. 
Following is an example of current implementation:
  "chronicThresholdCount": "3",
 "faultFields": {
"eventSourceType": "interface",
"alarmAdditionalInformation": [{
  "name": "DIR",
  "value": "tx"
}, {
  "name": "LOC",
  "value": "NEND"
}, {
  "name": "TYPE",
  "value": "communication"
}, {
  "name": "CKTID",
  "value": ""
}, {
  "name": "agingThreshold",
  "value": "300"
}, {
  "name": "objType",
  "value": "interface"
}, {
  "name": "alarmEntityOid",
  "value": "ORLDFLPC-0101050934 interface-eth-1/0/C1/1"
}],
"specificProblem": "lossOfSignal",
"alarmInterfaceA": "eth-1/0/C1/1",
"alarmCondition": "lossOfSignal",
"eventSeverity": "CRITICAL",
"faultFieldsVersion": 1,
"vfStatus": "Active"
 },
 "chronicInterval": "2"
  },

The modified structure would look like:
"chronicThresholdCount": "3",
 "faultFields": {
"eventSourceType": "interface",
"alarmAdditionalInformation": {
   "DIR":"tx",
   "LOC": "NEND",
   "TYPE": "communication",
   "CKTID": "",
   "agingThreshold": "300",
   "objType": "interface",
   "alarmEntityOid": "ORLDFLPC-0101050934 
interface-eth-1/0/C1/1"
},
"specificProblem": "lossOfSignal",
"alarmInterfaceA": "eth-1/0/C1/1",
"alarmCondition": "lossOfSignal",
"eventSeverity": "CRITICAL",
"faultFieldsVersion": 1,
"vfStatus": "Active"
 },
 "chronicInterval": "2"
  },

The rationale other than this being compact and reduces event processing time, 
for recommended changes are:


  1.  It inflates the message size by 16 bytes per name/value pair.  (So, 64 
entries in a message yields 1KB of waste.)


  1.  It forces message readers to iterate through an array doing string 
comparisons at O(n) rather than a typical hash lookup of O(log n). If a message 
writer drops 100 entries into that array, my high-speed event processing has to 
do 100 operations instead of 6. That's a 16x slowdown!  This matters quite a 
bit when dealing with 1000s of events per second.


  1.  We have event processing tools throughout our infrastructure that know 
how to pull named values from arbitrary JSON. For example, we have syntax like: 
${event.faultFields.alarmAdditionalInformation.alarmEntityOid}. Unfortunately, 
these tools are useless when data is in this 
array-of-objects-with-name-and-value-keys format. Our tools would have to be 
upgraded to support a name/value search like: 
${event.faultFields.alarmAdditionalInformation[name=alarmEntityOid].value}. 
This hardly seems worth doing - it'd be a bit difficult to implement and graft 
into our current syntax and in maybe 8 years of using JSON across a lot of 
services, I've never seen this construct.

We have two choices:


1.  We could replace the old name/value structure with new one, or

2.  We could support second structure in addition to first one to allow 
both for backward compatibility.

My personal preference is to replace and let collector convert 4.x and 5.x to 
the new structure. This impacts current downstream DCAE systems and I would 
like to get feedback on the change from ONAP team.

I would be discussing the issue during regularly scheduled DCAE team meeting.

Please advise.

Regards,

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

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


Re: [onap-discuss] 答复: [DCAE] DCAE questions from Usecase UI

2017-08-15 Thread GUPTA, ALOK
Tao:

Please see the youtube OPNFV demo on event flow. We had used influx-db and 
Grafana form open src to display them. I was suggesting you could use the 
similar solution as an interim solution while ONAP decides on the long term 
data store strategy.
The youtube demo can be found at: https://www.youtube.com/watch?v=Zoxcj4mwUwU


Regards,

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

From: shentao [mailto:shen...@chinamobile.com]
Sent: Tuesday, August 15, 2017 6:12 AM
To: JI, LUSHENG <l...@research.att.com>; GUPTA, ALOK <ag1...@att.com>; 
fu.guangr...@zte.com.cn; 'Yang Xu (Yang, Fixed Network)' <yang@huawei.com>; 
'Xinhui Li' <lxin...@vmware.com>
Cc: onap-discuss@lists.onap.org; 'Lingli' <denglin...@chinamobile.com>; 
don...@raisecom.com; zhang...@chinamobile.com
Subject: 答复: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Dear Lusheng and Alok

Thanks for your kindly help.
I think we were agreeing about alarm and performance show.
The following is the meeting minutes.

1. DCAE doesn't support complex APIs of querying alarm and performance data in 
R1. We'd like to discuss data storage with DCAE in R2.
2. Alarm and performance data of VNF/VIM will be push to Dmaap system and 
Usecase UI could get data by subscribing Dmaap APIs.
3. DCAE and Usecase UI will make further efforts to discuss how to get alarm 
and performance data via Dmaap.
4. Usecase UI will store alarm and performance data for present.
5. Alok would provide OPNFV demo about data storage and display to help Usecase 
UI team develop monitor function.


Best regards,
Tao

发件人: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
发送时间: 2017年8月14日 23:41
收件人: shentao; 'Lingli'
抄送: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
主题: Re: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Shentao,

I have accepted your meeting invite for 9-9:30PM Monday night (Beijing time 
9-9:30AM Tuesday morning).  But for some reason that response email was 
returned undelivered.
So let’s talk about it tonight (tomorrow morning).

Thanks,
Lusheng

From: shentao <shen...@chinamobile.com<mailto:shen...@chinamobile.com>>
Date: Monday, August 14, 2017 at 1:19 AM
To: "JI, LUSHENG (LUSHENG)" 
<l...@research.att.com<mailto:l...@research.att.com>>, 'Lingli' 
<denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Dear Lusheng

Look at your convenient time, I suggest that we organize one-on-one 
communication and confirmation as soon as possible.
The time suggested by me here is either:
1, your local time Monday morning 9am to 9:30am; or
2, your local time on Monday at 9pm to 9:30pm


Best regards,
Tao


发件人: shentao [mailto:shen...@chinamobile.com]
发送时间: 2017年8月14日 13:02
收件人: 'JI, LUSHENG (LUSHENG)'; 'Lingli'
抄送: 'onap-discuss@lists.onap.org'
主题: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi, Lusheng

Usecase UI is planning to provide alarm and performance display.
So I need the following APIs which would be supported by DCAE.

Plan A (best)
1. alarm API for querying alarms of VNFs and VIMs. And the API supports the 
conditional query according to time, type, vnf name and so on.
2. performance API for querying performance of VNFs and VIMs. And the API 
supports the conditional query according to time, type and so on.

Plan B
1. alarm API for querying alarms of VNFs and VIMs.
2. performance API for querying performance of VNFs and VIMs.

If you are convenient, I'd like to hold a zoom meeting on Monday (your time).


Best regards,
Tao


发件人: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
发送时间: 2017年8月14日 10:11
收件人: Lingli; shentao
抄送: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
主题: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Yes, we will need to set up a call to understand exactly what’s needed.
This was the first time this requirement was brought to our attention. There 
was no prior communication on this so we need to understand what support is 
needed.

Lusheng


From: Lingli <denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>>
Date: Sunday, August 13, 2017 at 7:04 PM
To: shentao <shen...@chinamobile.com<mailto:shen...@chinamobile.com>>
Cc: "JI, LUSHENG (LUSHENG)" 
<l...@research.att.com<mailto:l...@research.att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi Tao and Lusheng,

If I understand it correctly this issue is affecting M2 functional freeze for 
Usecase UI and VoLTE 

Re: [onap-discuss] [dcae] Google Protocol Buffer support for VES

2017-07-14 Thread GUPTA, ALOK
Manoj:

We are trying to go slow. We have not finalized on the protocol to use. We can 
certainly consider using GPB. I have forwarded your email to my architects for 
their input. I will keep you updated. BTW we also have a JAVA library 
completed. It will take some time to show up in ONAP gerrit (need to go through 
 the process),  but you can pick it up from our github: 
https://github.com/att/evel-library/files/1145800/VESJavaLibrary.tar.gz


Regards,

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

From: Manoj K Nair [mailto:manoj.k.n...@netcracker.com]
Sent: Friday, July 14, 2017 5:01 AM
To: GUPTA, ALOK <ag1...@att.com>
Cc: onap-discuss@lists.onap.org
Subject: [dcae] Google Protocol Buffer support for VES

Hi Alok,

We reviewed the VES specification you shared after the presentation in DCAE 
weekly meeting couple of weeks back.  We understand that currently VES supports 
a REST based interface with JSON payload to push telemetry data and events from 
the VNF to DCAE VES collector. For telemetry control an HTTP response channel 
is being used as per the test code link you published in the presentation.

Just wondering if GPB is considered as one of potential options for VES.  You 
have noted the use of Avro as one potential option as future enhancement. 
Wondering if GPB is also a potential option you are considering. Some of the 
advantages we see for GPB are.
•Uses binary formatting during serialization, which densily packs the 
payload (which is good for PM/telemetry data)
•Faster than the VES proposed JSON payload (which is good for events 
and alarms)
•Can define the structure (schema) of events/telemetry data in a 
protocol definition file (.proto) which is similar to the JSON schema that is 
available in OPNFV VES project
•Availability of code generators in multiple programming languages for 
encoding and decoding - Can generate code in C#, C++,  Java, Python, Go . 
Options in other languages available as well.

While we have noted the dynamic schema capabilities in Avro, one key advantage 
we see with GPB is the serialization code generation in multiple languages 
without limiting to the C language based library which is currently available 
and open source tool sets available for GPB. Moreover many network vendors and 
open source monitoring solutions (e.g. Prometheus, 
link<https://urldefense.proofpoint.com/v2/url?u=https-3A__prometheus.io_docs_instrumenting_exposition-5Fformats_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=XXhoW1oGu9w5ICuKXVTHEoj6jTy7JFzclXWnliVMEq4=-ZxUYr0a4WhAPcklP8EeMp8ah8uMFbczyPm-vlo9--0=>)
   support GPB already. We would be glad to share more information on the 
potential GPB usage if required.

Regards

Manoj
[cid:image002.png@01D2FC7C.E35B2030][https://www.netcracker.com/assets/img/netcracker-social-final.png]ƕ




The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] Using ceilometer to scale out VF module

2017-06-22 Thread GUPTA, ALOK
Oliver:

We do have TCA domain already defined and included in the current VES 
requirements document. The events would be sent to DCAE collector using REST 
API (please note username/password and FQDN would need to be configured in the 
Nagios sending the events and the info needs to be communicated to DCAE 
controller and collector receiving the events). The DCAE collector will place 
the events on DMaPP.

In addition we would need yaml on-boarding file so we can create policies and 
would need a clamp flow processing the event using the policies.

We don’t have examples for TCA domain, as we normally get raw performance data 
in the measurementforVnfScaling domain and then we have internal micro-service 
that generates TCAs.

We just presented a paper and demo at OPNFV that uses events from ONAP 
reference VNFs,  vFW and vLB and uses collectD Agent from Intel to get 
baremetal events in to DCAE collector. The link to demo is:  
https://www.youtube.com/watch?v=Zoxcj4mwUwU.

If people are interested in working the details within ONAP, I will be start SA 
discussion group soon and we can help answer question or work the details in 
the lab.


Regards,

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

From: SPATSCHECK, OLIVER
Sent: Thursday, June 22, 2017 9:47 AM
To: GUPTA, ALOK <ag1...@att.com>
Subject: Fwd: [onap-discuss] Using ceilometer to scale out VF module

Is that something you guys have looked into. Can you respond on onap-discuss if 
you did?

Thx

Oliver


Begin forwarded message:

From: Ethan Lynn <ethanly...@vmware.com<mailto:ethanly...@vmware.com>>
Subject: Re: [onap-discuss] Using ceilometer to scale out VF module
Date: June 22, 2017 at 9:45:18 AM EDT
To: "ROSE, DANIEL V" <dr6...@att.com<mailto:dr6...@att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>

Hi Daniel,
   Let’s say, if I write an agent that can receive ceilometer alarms and then 
transform to the format that ves can recognize, is it doable? If this is 
doable, is there any example that I can follow? I notice that there are some 
fields in ves like thresholdcrossingfields that might be  a good place to put 
ceilometer alarm datas, but I don’t find any example there.

On 22 Jun 2017, at 8:29 PM, ROSE, DANIEL V 
<dr6...@att.com<mailto:dr6...@att.com>> wrote:

You would need a listener added to dcae to receive these events. One may exist 
(check with someone in the dcae project) but we chose ves for release 1 as it 
allows the vnfs to send things that would: not be monitorable in the VIM (app 
health for example),are receivable if one does not have access to the vim (ie 
on rackspace) or if one does not run on openstack (ie azure).


Thanks,

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ethan Lynn
Sent: Wednesday, June 21, 2017 11:51 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Using ceilometer to scale out VF module

Hi,
   I’m wondering is there any workable solutions to integrate ceilometer’s 
alarm to scale out vDNS demo. I notice that for now we are using ves client to 
send measurementsForVfScalingFields to DCAE collector, and DCAE will trigger a 
policy action to scale out a new instance. But ceilometer already do the 
calculation and will send out an alarm when metrics exceed some level of 
threshold, is it possible to let ceilometer directly send an alarm to DCAE and 
then trigger a policy action?


Best Regards,
Ethan Lynn
ethanly...@vmware.com<mailto:ethanly...@vmware.com>
+86 010-59934270

___
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=9iyuArzgyekj47PZSPfIijI2cSHsUJtAlcTA0X_udNI=s0NZMbfOGadr8QlOYx7SW-KJKR5WGN5TeY_YyvjDqus=YYQIDnX2O5G5bFRrBWcqJcq1Jy4LakCXzsELqiv7H74=

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