Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

[HU, BIN]

Hi Lingli,

Thank you for your review and questions.

VES team (led by Alok Gupta) has been working with Modeling team (Andrew Mayer 
etc), and VES model is already aligned with the ONAP Telemetry model. So the 
team is specifically looking for the feedback of specific metrics applicable to 
MultiVIM.

The team got feedback from VMWare and Intel, and has been working on the high 
level metrics we would need to support MultiVIM project. We are in the process 
of finalizing the details of metrics. The plan is to finalize the requirements 
by end of the month and send them out for review.

The current ask was to include MultiVIM metrics within the defined block of 
measurementForVfscaling and the team is in the process of finalizing it.

Hope this helps.
Thanks
Bin

From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Thursday, March 22, 2018 9:16 PM
To: HU, BIN ; onap-discuss@lists.onap.org
Cc: 'zhang ab' ; 'Ke Liang' ; 
'Hellmann, Gil' ; 'Andrew Philip' 
; denghu...@huawei.com; 'Rittwik Jana' 

Subject: RE: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM 
Metrics for VES Requirement

Hi Bin,

Sorry for the late response on this thread.

I have the following questions and would appreciate your clarifications if 
possible:
1, Is it intended for R2 implementation?
2, Is it calling for feedback on metrics or feedback on data/information model?

From the content you shared, although it is entitled as “Multi-Cloud Data 
Model”, the “Next Steps”listed on Page 12 as follows, which confuses me with 
the intention of the last call, are we evaluating the VES metrics from Pages 
5-10 or a data model/schema which I cannot find from the current slides deck? 
Is there anything else I could refer to for clarification?

In either case, I suppose it would be great to sync it to modeling group before 
committing any changes that might impact ONAP Data/Information Model.

[cid:image001.jpg@01D3C277.9916A050]

Thanks,
Lingli


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of HU, BIN
Sent: 2018年3月15日 3:15
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: zhang ab mailto:zhanganb...@chinamobile.com>>; 
Ke Liang mailto:lia...@vmware.com>>; Hellmann, Gil 
mailto:gil.hellm...@windriver.com>>; Andrew Philip 
mailto:aphi...@microsoft.com>>
Subject: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics 
for VES Requirement

Hello my fellow colleagues in MultiVIM project,

Following our great discussion on February 26th, and follow up email on Feb 
27th for feedback of MultiVIM metrics in VES requirement, this is the last call 
for feedback.

Please provide any feedback in terms of MultiVIM metrics for VES Requirement. 
VES team intends to publish official requirement next week.

Because this is the last call for feedback, and prior communication has been 
made for reasonable times. Lacking of feedback means that MultiVIM project team 
agrees to official VES requirement that will be published next week.

Thank you everyone.
Bin

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 GUPTA, ALOK
Sent: Tuesday, February 27, 2018 10:07 AM
To: aasm...@redhat.com<mailto:aasm...@redhat.com>; 
bj@intel.com<mailto:bj@intel.com>; 
tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>; 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; 
scott.mansfi...@ericsson.com<mailto:scott.mansfi...@ericsson.com>; 
mario.rodrig...@arm.com<mailto:mario.rodrig...@arm.com>; 
aput...@redhat.com<mailto:aput...@redhat.com>; 
calin.gher...@intel.com<mailto:calin.gher...@intel.com>; SULLIVAN, BRYAN L 
mailto:bryan.sulli...@research.att.com>>; 
romanx.korynkev...@intel.com<mailto:romanx.korynkev...@intel.com>; 
manish.ja...@cavium.com<mailto:manish.ja...@cavium.com>; 
pavan.gu...@calsoftinc.com<mailto:pavan.gu...@calsoftinc.com>; 
damien.po...@intel.com<mailto:damien.po...@intel.com>; 
kand...@us.ibm.com<mailto:kand...@us.ibm.com>; 
wesley.campb...@intel.com<mailto:wesley.campb...@intel.com>; Javier Arauz 
mailto:j.javier.ar...@gmail.com>>; 
ning@intel.com<mailto:ning@intel.com>; 
ab...@redhat.com<mailto:ab...@redhat.com>; 
tarasx.chor...@intel.com<mailto:tarasx.chor...@intel.com>; 
ola.liljed...@arm.com<mailto:ola.liljed...@arm.com>; 
raghuveer.re...@intel.com<mailto:raghuveer.re...@intel.com>; 
yangya...@chinamobile.com<mailto:yangya...@chinamobile.com>; 
serkant.ulude...@argela.com.tr<mailto:serkant.ulude...@argela.com.tr>; 
krishna.j.mur...@intel.com<mailto:krishna.j.mur...@intel.com>; 
opnfv-tech-disc...@lists.opnfv.org<

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

[MAYER, ANDREW J]

All,

I recommend that we start by updating the MonitoringParameterDesc Class into 
the clean version of the VNF Descriptor Design Time model.
Please see: https://wiki.onap.org/display/DW/Class%3A+MonitoringParameterDesc
We reviewed these proposed updates on both the Modeling Sub-Committee as well 
as the VNF SDK Modeling calls.

This gives the VNF Descriptor a way to provide the definition of Event Types 
and Metric Types that are essential for VES.

Best Regards,
Andy

Andy Mayer, Ph.D. | PMTS, D2.0 Integration | AT&T Labs | Phone: +1 (732) 
420-9945 | am8...@att.com

From: HU, BIN
Sent: Friday, March 23, 2018 10:40 AM
To: Lingli Deng ; onap-discuss@lists.onap.org
Cc: 'zhang ab' ; 'Ke Liang' ; 
'Hellmann, Gil' ; 'Andrew Philip' 
; denghu...@huawei.com; 'Rittwik Jana' 
; GUPTA, ALOK ; SULLIVAN, BRYAN L 
; MAYER, ANDREW J 
Subject: RE: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM 
Metrics for VES Requirement

Hi Lingli,

Thank you for your review and questions.

VES team (led by Alok Gupta) has been working with Modeling team (Andrew Mayer 
etc), and VES model is already aligned with the ONAP Telemetry model. So the 
team is specifically looking for the feedback of specific metrics applicable to 
MultiVIM.

The team got feedback from VMWare and Intel, and has been working on the high 
level metrics we would need to support MultiVIM project. We are in the process 
of finalizing the details of metrics. The plan is to finalize the requirements 
by end of the month and send them out for review.

The current ask was to include MultiVIM metrics within the defined block of 
measurementForVfscaling and the team is in the process of finalizing it.

Hope this helps.
Thanks
Bin

From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Thursday, March 22, 2018 9:16 PM
To: HU, BIN mailto:bh5...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: 'zhang ab' 
mailto:zhanganb...@chinamobile.com>>; 'Ke Liang' 
mailto:lia...@vmware.com>>; 'Hellmann, Gil' 
mailto:gil.hellm...@windriver.com>>; 'Andrew 
Philip' mailto:aphi...@microsoft.com>>; 
denghu...@huawei.com<mailto:denghu...@huawei.com>; 'Rittwik Jana' 
mailto:rittwik.j...@gmail.com>>
Subject: RE: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM 
Metrics for VES Requirement

Hi Bin,

Sorry for the late response on this thread.

I have the following questions and would appreciate your clarifications if 
possible:
1, Is it intended for R2 implementation?
2, Is it calling for feedback on metrics or feedback on data/information model?

From the content you shared, although it is entitled as “Multi-Cloud Data 
Model”, the “Next Steps”listed on Page 12 as follows, which confuses me with 
the intention of the last call, are we evaluating the VES metrics from Pages 
5-10 or a data model/schema which I cannot find from the current slides deck? 
Is there anything else I could refer to for clarification?

In either case, I suppose it would be great to sync it to modeling group before 
committing any changes that might impact ONAP Data/Information Model.

[cid:image001.jpg@01D3C277.9916A050]

Thanks,
Lingli


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
mailto:onap-discuss-boun...@lists.onap.org>>
 On Behalf Of HU, BIN
Sent: 2018年3月15日 3:15
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: zhang ab mailto:zhanganb...@chinamobile.com>>; 
Ke Liang mailto:lia...@vmware.com>>; Hellmann, Gil 
mailto:gil.hellm...@windriver.com>>; Andrew Philip 
mailto:aphi...@microsoft.com>>
Subject: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics 
for VES Requirement

Hello my fellow colleagues in MultiVIM project,

Following our great discussion on February 26th, and follow up email on Feb 
27th for feedback of MultiVIM metrics in VES requirement, this is the last call 
for feedback.

Please provide any feedback in terms of MultiVIM metrics for VES Requirement. 
VES team intends to publish official requirement next week.

Because this is the last call for feedback, and prior communication has been 
made for reasonable times. Lacking of feedback means that MultiVIM project team 
agrees to official VES requirement that will be published next week.

Thank you everyone.
Bin

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 GUPTA, ALOK
Sent: Tuesday, February 27, 2018 10:07 AM
To: aasm...@redhat.com<mailto:aasm...@redhat.com>; 
bj@intel.com<mailto:bj@intel.com>; 
tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>; 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; 
scott.mansfi...@ericsson

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

[Lingli Deng]

Hi Bin,

 

Sorry for the late response on this thread.

 

I have the following questions and would appreciate your clarifications if
possible:

1, Is it intended for R2 implementation?

2, Is it calling for feedback on metrics or feedback on data/information
model?

 

>From the content you shared, although it is entitled as “Multi-Cloud Data
Model”, the “Next Steps”listed on Page 12 as follows, which confuses me
with the intention of the last call, are we evaluating the VES metrics from
Pages 5-10 or a data model/schema which I cannot find from the current
slides deck? Is there anything else I could refer to for clarification?

 

In either case, I suppose it would be great to sync it to modeling group
before committing any changes that might impact ONAP Data/Information Model.


 



 

Thanks,

Lingli

 

 

From: onap-discuss-boun...@lists.onap.org
 On Behalf Of HU, BIN
Sent: 2018年3月15日 3:15
To: onap-discuss@lists.onap.org
Cc: zhang ab ; Ke Liang ;
Hellmann, Gil ; Andrew Philip

Subject: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM
Metrics for VES Requirement

 

Hello my fellow colleagues in MultiVIM project,

 

Following our great discussion on February 26th, and follow up email on Feb
27th for feedback of MultiVIM metrics in VES requirement, this is the last
call for feedback.

 

Please provide any feedback in terms of MultiVIM metrics for VES
Requirement. VES team intends to publish official requirement next week.

 

Because this is the last call for feedback, and prior communication has been
made for reasonable times. Lacking of feedback means that MultiVIM project
team agrees to official VES requirement that will be published next week.

 

Thank you everyone.

Bin

 

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 GUPTA, ALOK
Sent: Tuesday, February 27, 2018 10:07 AM
To: aasm...@redhat.com <mailto:aasm...@redhat.com> ; bj@intel.com
<mailto:bj@intel.com> ; tony.b.mcma...@intel.com
<mailto:tony.b.mcma...@intel.com> ; emma.l.fo...@intel.com
<mailto:emma.l.fo...@intel.com> ; scott.mansfi...@ericsson.com
<mailto:scott.mansfi...@ericsson.com> ; mario.rodrig...@arm.com
<mailto:mario.rodrig...@arm.com> ; aput...@redhat.com
<mailto:aput...@redhat.com> ; calin.gher...@intel.com
<mailto:calin.gher...@intel.com> ; SULLIVAN, BRYAN L
mailto:bryan.sulli...@research.att.com> >;
romanx.korynkev...@intel.com <mailto:romanx.korynkev...@intel.com> ; manish.
ja...@cavium.com <mailto:manish.ja...@cavium.com> ;
pavan.gu...@calsoftinc.com <mailto:pavan.gu...@calsoftinc.com> ;
damien.po...@intel.com <mailto:damien.po...@intel.com> ; kand...@us.ibm.com
<mailto:kand...@us.ibm.com> ; wesley.campb...@intel.com
<mailto:wesley.campb...@intel.com> ; Javier Arauz mailto:j.javier.ar...@gmail.com> >; ning@intel.com
<mailto:ning@intel.com> ; ab...@redhat.com <mailto:ab...@redhat.com> ;
tarasx.chor...@intel.com <mailto:tarasx.chor...@intel.com> ;
ola.liljed...@arm.com <mailto:ola.liljed...@arm.com> ;
raghuveer.re...@intel.com <mailto:raghuveer.re...@intel.com> ;
yangya...@chinamobile.com <mailto:yangya...@chinamobile.com> ;
serkant.ulude...@argela.com.tr <mailto:serkant.ulude...@argela.com.tr> ;
krishna.j.mur...@intel.com <mailto:krishna.j.mur...@intel.com> ;
opnfv-tech-disc...@lists.opnfv.org
<mailto:opnfv-tech-disc...@lists.opnfv.org> ; andrew.duig...@intel.com
<mailto:andrew.duig...@intel.com> ; Srinivas Chaganti
mailto:schaga...@versa-networks.com> >;
MORTON JR., AL mailto:acmor...@att.com> >
Subject: Re: [opnfv-tech-discuss] Updated invitation: [barometer] Weekly
Call @ Weekly from 12pm to 1pm on Tuesday (EDT)
(opnfv-tech-disc...@lists.opnfv.org
<mailto:opnfv-tech-disc...@lists.opnfv.org> )

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Team:

 

Please find enclosed a presentation from ONAP mulit-vim project requesting
feedback on the metrics we should include in the main body. Please help
provide feedback on following:

*   Please see chart 5 with metrics categories currently in VES shown on
the Left column. The list from Right column includes metrics that could be
included with VES frame work. Please provide feedback, the ones that you
would like me to include in VES mfvs domain. 
*   ON pages 7 thru 10 we define metrics that is VES and delta metrics
detail that is currently not in VES. Please review the embedded excel file
on pg 5 and the pg 7 thru 10 and advice if you would like me to expand the
metrics category.

Please send me feedback soon, so I can update VES Requirements and provide
you a draft copy for approval.

 

Regards,

 

Alok Gupta

732-420-7007

MT B2 3D30

 <

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

[HU, BIN]

Jessie,

Thank you for your interest. Please refer to this 
link<https://wiki.onap.org/download/attachments/8227952/Multi%20VIM%20Data%20Model.pptx?version=1&modificationDate=1521138254534&api=v2>
 for the document.

Look forward to your feedback.

Thanks
Bin

From: jessie jewitt [mailto:jessie.jew...@oamtechnologies.com]
Sent: Thursday, March 15, 2018 10:18 AM
To: HU, BIN 
Cc: onap-discuss@lists.onap.org; zhang ab ; Ke 
Liang ; Hellmann, Gil ; Andrew 
Philip 
Subject: Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM 
Metrics for VES Requirement

This is a long email chain. Could you please provide a link to the document 
that is supposed to be reviewed and for which we should provide feedback?
Thank you,
Jessie

On Wed, Mar 14, 2018 at 12:14 PM, HU, BIN 
mailto:bh5...@att.com>> wrote:
Hello my fellow colleagues in MultiVIM project,

Following our great discussion on February 26th, and follow up email on Feb 
27th for feedback of MultiVIM metrics in VES requirement, this is the last call 
for feedback.

Please provide any feedback in terms of MultiVIM metrics for VES Requirement. 
VES team intends to publish official requirement next week.

Because this is the last call for feedback, and prior communication has been 
made for reasonable times. Lacking of feedback means that MultiVIM project team 
agrees to official VES requirement that will be published next week.

Thank you everyone.
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto: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 GUPTA, ALOK
Sent: Tuesday, February 27, 2018 10:07 AM
To: aasm...@redhat.com<mailto:aasm...@redhat.com>; 
bj@intel.com<mailto:bj@intel.com>; 
tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>; 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; 
scott.mansfi...@ericsson.com<mailto:scott.mansfi...@ericsson.com>; 
mario.rodrig...@arm.com<mailto:mario.rodrig...@arm.com>; 
aput...@redhat.com<mailto:aput...@redhat.com>; 
calin.gher...@intel.com<mailto:calin.gher...@intel.com>; SULLIVAN, BRYAN L 
mailto:bryan.sulli...@research.att.com>>; 
romanx.korynkev...@intel.com<mailto:romanx.korynkev...@intel.com>; 
manish.ja...@cavium.com<mailto:manish.ja...@cavium.com>; 
pavan.gu...@calsoftinc.com<mailto:pavan.gu...@calsoftinc.com>; 
damien.po...@intel.com<mailto:damien.po...@intel.com>; 
kand...@us.ibm.com<mailto:kand...@us.ibm.com>; 
wesley.campb...@intel.com<mailto:wesley.campb...@intel.com>; Javier Arauz 
mailto:j.javier.ar...@gmail.com>>; 
ning@intel.com<mailto:ning@intel.com>; 
ab...@redhat.com<mailto:ab...@redhat.com>; 
tarasx.chor...@intel.com<mailto:tarasx.chor...@intel.com>; 
ola.liljed...@arm.com<mailto:ola.liljed...@arm.com>; 
raghuveer.re...@intel.com<mailto:raghuveer.re...@intel.com>; 
yangya...@chinamobile.com<mailto:yangya...@chinamobile.com>; 
serkant.ulude...@argela.com.tr<mailto:serkant.ulude...@argela.com.tr>; 
krishna.j.mur...@intel.com<mailto:krishna.j.mur...@intel.com>; 
opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>; 
andrew.duig...@intel.com<mailto:andrew.duig...@intel.com>; Srinivas Chaganti 
mailto:schaga...@versa-networks.com>>; MORTON 
JR., AL mailto:acmor...@att.com>>
Subject: Re: [opnfv-tech-discuss] Updated invitation: [barometer] Weekly Call @ 
Weekly from 12pm to 1pm on Tuesday (EDT) 
(opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>)

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Team:

Please find enclosed a presentation from ONAP mulit-vim project requesting 
feedback on the metrics we should include in the main body. Please help provide 
feedback on following:

-  Please see chart 5 with metrics categories currently in VES shown on 
the Left column. The list from Right column includes metrics that could be 
included with VES frame work. Please provide feedback, the ones that you would 
like me to include in VES mfvs domain.

-  ON pages 7 thru 10 we define metrics that is VES and delta metrics 
detail that is currently not in VES. Please review the embedded excel file on 
pg 5 and the pg 7 thru 10 and advice if you would like me to expand the metrics 
category.
Please send me feedback soon, so I can update VES Requirements and provide you 
a draft copy for approval.

Regards,

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


-Original Appointment-
From: aasm...@redhat.com<mailto:aasm...@redhat.com> [mailto:aasm...@redhat.com]
Sent: Tuesday, October 24, 2017 10:51 AM
To: aasm...@redhat.com<mailto:aasm...@redhat.co

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

[jessie jewitt]

This is a long email chain. Could you please provide a link to the document
that is supposed to be reviewed and for which we should provide feedback?
Thank you,
Jessie

On Wed, Mar 14, 2018 at 12:14 PM, HU, BIN  wrote:

> Hello my fellow colleagues in MultiVIM project,
>
>
>
> Following our great discussion on February 26th, and follow up email on
> Feb 27th for feedback of MultiVIM metrics in VES requirement, this is the
> last call for feedback.
>
>
>
> Please provide any feedback in terms of MultiVIM metrics for VES
> Requirement. VES team intends to publish official requirement next week.
>
>
>
> Because this is the last call for feedback, and prior communication has
> been made for reasonable times. Lacking of feedback means that MultiVIM
> project team agrees to official VES requirement that will be published next
> week.
>
>
>
> Thank you everyone.
>
> Bin
>
>
>
> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:
> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *GUPTA, ALOK
> *Sent:* Tuesday, February 27, 2018 10:07 AM
> *To:* aasm...@redhat.com; bj@intel.com; tony.b.mcma...@intel.com;
> emma.l.fo...@intel.com; scott.mansfi...@ericsson.com;
> mario.rodrig...@arm.com; aput...@redhat.com; calin.gher...@intel.com;
> SULLIVAN, BRYAN L ;
> romanx.korynkev...@intel.com; manish.ja...@cavium.com;
> pavan.gu...@calsoftinc.com; damien.po...@intel.com; kand...@us.ibm.com;
> wesley.campb...@intel.com; Javier Arauz ;
> ning@intel.com; ab...@redhat.com; tarasx.chor...@intel.com;
> ola.liljed...@arm.com; raghuveer.re...@intel.com;
> yangya...@chinamobile.com; serkant.ulude...@argela.com.tr;
> krishna.j.mur...@intel.com; opnfv-tech-disc...@lists.opnfv.org;
> andrew.duig...@intel.com; Srinivas Chaganti ;
> MORTON JR., AL 
> *Subject:* Re: [opnfv-tech-discuss] Updated invitation: [barometer]
> Weekly Call @ Weekly from 12pm to 1pm on Tuesday (EDT) (
> opnfv-tech-disc...@lists.opnfv.org)
>
>
>
> Security Advisory:* This Message Originated Outside of AT&T ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
>
> *Team:*
>
>
>
> Please find enclosed a presentation from ONAP mulit-vim project requesting
> feedback on the metrics we should include in the main body. Please help
> provide feedback on following:
>
> -  Please see chart 5 with metrics categories currently in VES
> shown on the Left column. The list from Right column includes metrics that
> could be included with VES frame work. Please provide feedback, the ones
> that you would like me to include in VES mfvs domain.
>
> -  ON pages 7 thru 10 we define metrics that is VES and delta
> metrics detail that is currently not in VES. Please review the embedded
> excel file on pg 5 and the pg 7 thru 10 and advice if you would like me to
> expand the metrics category.
>
> Please send me feedback soon, so I can update VES Requirements and provide
> you a draft copy for approval.
>
>
>
> Regards,
>
>
>
> Alok Gupta
>
> 732-420-7007 <(732)%20420-7007>
>
> MT B2 3D30
>
> ag1...@att.com
>
>
>
>
>
> -Original Appointment-
> *From:* aasm...@redhat.com [mailto:aasm...@redhat.com ]
>
> *Sent:* Tuesday, October 24, 2017 10:51 AM
> *To:* aasm...@redhat.com; aasm...@redhat.com; bj@intel.com;
> tony.b.mcma...@intel.com; emma.l.fo...@intel.com;
> scott.mansfi...@ericsson.com; mario.rodrig...@arm.com; aput...@redhat.com;
> calin.gher...@intel.com; SULLIVAN, BRYAN L; romanx.korynkev...@intel.com;
> manish.ja...@cavium.com; pavan.gu...@calsoftinc.com;
> damien.po...@intel.com; kand...@us.ibm.com; wesley.campb...@intel.com;
> Javier Arauz; ning@intel.com; ab...@redhat.com;
> tarasx.chor...@intel.com; ola.liljed...@arm.com; raghuveer.re...@intel.com;
> yangya...@chinamobile.com; serkant.ulude...@argela.com.tr;
> krishna.j.mur...@intel.com; opnfv-tech-disc...@lists.opnfv.org;
> andrew.duig...@intel.com; Srinivas Chaganti; MORTON JR., AL; GUPTA, ALOK
> *Subject:* [opnfv-tech-discuss] Updated invitation: [barometer] Weekly
> Call @ Weekly from 12pm to 1pm on Tuesday (EDT) (opnfv-tech-discuss@lists.
> opnfv.org)
> *When:* Tuesday, February 27, 2018 12:00 PM-1:00 PM America/New_York.
> *Where:* https://global.gotomeeting.com/join/819733085
> 
>
>
>
>
>
> *This event has been changed.*
>
> *more details »*
> 

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

[TOFIGH, TOM]

ALOK, Bin and Multi-VIM  team;

In addition to what is listed in your table, Should the domain be expanded to 
include collecting matrices from mobility and Transport infrastructure?
For example ;  Radio, ONUs, SSDs, GPUs, Roadms, Amplifiers, Transponders

In addition can " Collector" be also its own domain. For example an specific  
collector may be part of the infrastructure that is responsible for Meta Data 
or special type of data acquisition engine that can feed the uppers layers such 
as DCAE or operational sub-systems.

Regards
Tom Tofigh
tof...@att.com<mailto:tof...@att.com>






Domain

Description

Host

These are physical server metrics for performance and utilization for the 
physical host including CPU, memory, disk, fans, power, network, power, etc.

Hypervisor

This is the Hypervisor's view of resources and usages including CPU, memory, 
storage, network, etc.

Virtual Machine

This the individual VM view of performance and usage of CPU, memory, storage, 
network, etc.

Switching

These are performance and usage metrics for the logical virtual switch and 
distributed port groups.

OS

This is the performance and health metrics from the host and guest operating 
system flavor, including system, network, CPU, memory, processes, paging, swap, 
etc.

Tenant

Compute and memory KPI's partitioned across hosts and resource clusters for a 
tenant/consumer - representing an enterprise, wholesale, or retail consumption 
model.

Resource Cluster

This is an aggregate representation of hosts as a combined compute function 
sharing similar networking and storage. All hosts in the resource cluster have 
identical HW capabilities and capacity.

Resource Cluster Group

A Resource Cluster Group is a logical construct which comprises of multiple 
resource clusters.

Data Store

This is the data storage usage and performance metrics for an aggregate logical 
store including read, write, latency, IOPS, etc. from the underlying disks.

Data Center

Aggregate summarization across resources in a data center, useful for 
cross-site optimization, workload placement, capacity planning functions, for 
example.



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HU, BIN
Sent: Wednesday, March 14, 2018 12:15 PM
To: onap-discuss@lists.onap.org
Cc: zhang ab ; Ke Liang ; 
Hellmann, Gil ; Andrew Philip 

Subject: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics 
for VES Requirement

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hello my fellow colleagues in MultiVIM project,

Following our great discussion on February 26th, and follow up email on Feb 
27th for feedback of MultiVIM metrics in VES requirement, this is the last call 
for feedback.

Please provide any feedback in terms of MultiVIM metrics for VES Requirement. 
VES team intends to publish official requirement next week.

Because this is the last call for feedback, and prior communication has been 
made for reasonable times. Lacking of feedback means that MultiVIM project team 
agrees to official VES requirement that will be published next week.

Thank you everyone.
Bin

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 GUPTA, ALOK
Sent: Tuesday, February 27, 2018 10:07 AM
To: aasm...@redhat.com<mailto:aasm...@redhat.com>; 
bj@intel.com<mailto:bj@intel.com>; 
tony.b.mcma...@intel.com<mailto:tony.b.mcma...@intel.com>; 
emma.l.fo...@intel.com<mailto:emma.l.fo...@intel.com>; 
scott.mansfi...@ericsson.com<mailto:scott.mansfi...@ericsson.com>; 
mario.rodrig...@arm.com<mailto:mario.rodrig...@arm.com>; 
aput...@redhat.com<mailto:aput...@redhat.com>; 
calin.gher...@intel.com<mailto:calin.gher...@intel.com>; SULLIVAN, BRYAN L 
mailto:bryan.sulli...@research.att.com>>; 
romanx.korynkev...@intel.com<mailto:romanx.korynkev...@intel.com>; 
manish.ja...@cavium.com<mailto:manish.ja...@cavium.com>; 
pavan.gu...@calsoftinc.com<mailto:pavan.gu...@calsoftinc.com>; 
damien.po...@intel.com<mailto:damien.po...@intel.com>; 
kand...@us.ibm.com<mailto:kand...@us.ibm.com>; 
wesley.campb...@intel.com<mailto:wesley.campb...@intel.com>; Javier Arauz 
mailto:j.javier.ar...@gmail.com>>; 
ning@intel.com<mailto:ning@intel.com>; 
ab...@redhat.com<mailto:ab...@redhat.com>; 
tarasx.chor...@intel.com<mailto:tarasx.chor...@intel.com>; 
ola.liljed...@arm.com<mailto:ola.liljed...@arm.com>; 
raghuveer.re...@intel.com<mailto:raghuveer.re...@intel.com>; 
yangya...@chinamobile.com<mailto:yangya...@chinamobile.com>; 
serkant.ulude...@argela.com.tr<mailto:serkant.ulude...@argela.com.tr>; 
krishna.j.mur...@intel.com<mailto:krishna.j