Hi Thinh

It is output of meeting, but we did hear your disagreement, and we also 
questioned whether you and Nokia could contribute all implementation for SOL001 
into ONAP SDC/VNFSDK/VFC/SO projects or not, we haven’t heard any reply yet.

Thanks a  lot


From: Nguyenphu, Thinh (Nokia - US/Irving) [mailto:thinh.nguyen...@nokia.com]
Sent: Wednesday, March 07, 2018 11:29 PM
To: Vul, Alex; denghui (L); Gadiyar, Rajesh; Addepalli, Srinivasa R; 
onap-discuss@lists.onap.org; onap-...@lists.onap.org
Cc: GILBERT, MAZIN E (MAZIN E); Katzman, Anatoly
Subject: RE: [onap-discuss] URGENT - Modeling Subcommittee meeting minutes from 
March 6th meeting...

Hi Deng Hui,

This statement in meeting note is not correct either.

“2) will update onap type with TOSCA NFV profile, and”

We did not agreed to update onap types with TOSCA NFV profile 
(tosca-nfv-profile-wd05-rev03). The tosca-nfv-profile-wd05-rev03 is out of date 
and no long align with ONAP R2 IM. The correct mapping should be SOL001 v.0.6.0 
(a draft is available and  expect to be public available in 3 days from now).

SOL001 v0.6.0 includes update on all of nodes, datatypes, capabilities types 
and HPA with all of the data types. in addition, it has all of the TOSCA types 
for support single deployment too.

Would please update the meeting note and if need further discussion, my 
recommendation is to assign the topic for next week call again.


[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vul, Alex
Sent: Wednesday, March 07, 2018 7:04 AM
To: denghui (L) <denghu...@huawei.com<mailto:denghu...@huawei.com>>; Gadiyar, 
Rajesh <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>; Addepalli, 
Srinivasa R 
<ma...@research.att.com<mailto:ma...@research.att.com>>; Katzman, Anatoly 
Subject: [onap-discuss] URGENT - Modeling Subcommittee meeting minutes from 
March 6th meeting...

Dear Deng Hui,

The meeting minutes appear to be incorrect…

Item 4) under the 1) DM incorrectly states that…

4) will work on improve R3 modeling spec before end of Beijing release

Extra addition related to IM+(including HPA) will be added later

As I understand it, the above statement alleges that we agreed to postpone the 
HPA modeling extensions until R3. Is this correct?

I am afraid we never agreed to postpone the implementation of HPA until after 
R2. In fact, if I remember correctly, when asked if anyone had any objections 
to implementing HPA in R2, no one on the call raised any objections. Having 
talked to Anatoly, my understanding is that he never agreed to exclude the HPA 
model extensions from R2 either.

Once again, HPA is an agreed upon functional requirement to be implemented in 
ONAP R2. HPA has gone through the public review. HPA information and data model 
extensions need to be considered as part of R2

The HPA modeling extensions are based on the same industry standard information 
model as ONAP IM R2+  �C ETSI IFA011 v2.4.1. The HPA modeling extensions can 
added to either the NFV profile based data model or a ETSI SOL001 based data 

If the community decision is to use the NFV Profile based data model so be it. 
We will add the HPA related data types, node types and attributes to what 
Victor uploaded on the Wiki, under the NFV Profile model and move on. The 
implementation of HPA in R2 is on-going…

In the future, I would suggest that we record the Modeling Subcommittee 
meetings. This way we can avoid any misunderstandings like this from happening…

Kind regards,

Alex Vul
Intel Corporation
20180306 Meeting agenda and Minutes

1) DM:                     Anatoly Katzman

●Victor’s proposal will be agreed �C TOSCA NFV profile plus R2 IM+


Note: need to confirm whether onboarding has any issue, if fail then need to 
fall back to R1 solution.

1) will keep onap type and heat type both folders, and

2) will update onap type with TOSCA NFV profile, and

3) will best effort to let 2 use cases use it, if fail, and will fall back to 
heat type , and

4) will work on improve R3 modeling spec before end of Beijing release

Extra addition related to IM+(including HPA) will be added later

2)Resource IM:        Xu Yang
3)Service IM/DM:    Lingli Deng & Maopeng (Wednesday call)
4)Modeling workshop in ONS 2017

5) If time allows:

  Modeling spec Papyrus:  Jessie Jewitt

  Modeling tools:               Nigel Davis

  Parser:                              Atul Purohit

  A&AI                                James Forsyth

onap-discuss mailing list

Reply via email to