Hello All

ONAP Modeling workshop minutes

1       Service IM: back to service(customer facing service)/service 
component(resource facing service, e.g. network service)/resource/resource 
component layering class diagram, not using composite/decorative pattern for 
Beijing, translate into papyrus format based on agreed clean version.

2       Resource IM: For design time model, agreed to work on a subset of 
IFA011 for Beijing (i.e. remove internalCP as show in the discussion page), 
agreed to add hierarchy for CP inheritance, agreed to work on the latest 
version of IFA011 (v2.3.1). For run time model, agreed to refactor some of the 
attributes (e.g., ip addresses).

3       Design time DM: Agreed on Service and Resource hierarchy, while both 
service and resource can leverage substitution mapping mechanism to realize 
self-recursion aggregation or composition relations if needed by the IM.

4       Runtime DM A&AI will update NFV related API? in order to align with 
Information model, and notify the related project accordingly

5       Agreed to work on a concrete example to show how ONAP IM maps to ONAP 
DM.

6       R2 will be based on TOSCA simple profile 1.1 other than 1.2, but may 
need to consider some special feature of 1.2 if needed by the use case

7       Each DF should be described in a single TOSCA Service template (VNFD) 
and considered as a single VNF, in Beijing release, one VNF package will only 
contain one VNFD

8       R2+ Modeling spec naming convention will use the low camel for 
attribute names, will consider to add naming convention check during M1/M4

9       WiKi will be used for Modeling spec intermediate version,  Readthedoc 
will be used for published version

10    Michela volunteer to start to work on the common terminologies for ONAP 
modeling

11    Modeling spec will be migrate to Papyrus asap, needs to decide version 
number and setup the timeline to proceed it

12    Use Jira/backlog to track the work asap

Thanks for your checking
Best regards

DENG Hui
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to