Page Comparison

The purpose of the meeting was to have each group the has done some sort of ONAP Model Driven/Enabled in the past year to explain their view.

**Meeting was not recorded**

• None of the 3 presentations contradicted any others presentations
• Everyone was in agreement that we should have a common internal model because;
• Custom code causes delays and increase cost
• ONAP components should only process one internal model  
• Need to preserve on boarding artifacts
• We should probably look at the SDC Internal model to see what is actually in it
• What state is it in?  
• https://

• lf-onap.

• atlassian.

• net/wiki/display/DW/SDC+Distribution+client+AID
• Need to take an inventory of what components are using TOSCA model concepts
• Need to define Gaps
• 3 other work efforts are taking place related to Model Driven ( CDS , API Documentation Project, SO POS (Driven by TOSCA syntax) )
• CDS is a project that has implemented some TOSCA syntax processing  
• Yuriy talked about CDS
• He presented CDS at Antwerp
• Link to what Yuriy presented in Antwerp is listed above.
• Policy is using same concepts
• Not all people were aware of CDS- will look into learning more about it  
• API Documentation Project
• Need standard API doc template
• https://

• lf-onap.

• atlassian.

• net/wiki/display/DW/Developing+ONAP+API+Documentation
• Andy holds meetings are on Friday … 10:00AM Eastern Time
• Zoom Meeting   - https://zoom.us/j/731954210
• SO POC – processing driven by TOSCA syntax
• SO has started on
• https://

• lf-onap.

• atlassian.

• net/wiki/display/DW/SO+Weekly+Meeting+2019-11-06

• Next Steps
• Continue meeting every two weeks on Monday
• Look at the current internal model
• Define what is are target goal and how to get there without breaking things that work.
• Define any Gaps.
• Who else should be part of these discussions?

First review by Samuli from Samsung.

• Reviewed a couple slide from his CNF presentation (link to deck is posted above)
• Focused was onboarding process
• ONAP has made multiple attempts to generalize modeling and orchestration
• TOSCA
• ETSI
• Blueprints , etc…
• Need to choose a single common modeling language  - TOSCA
• TOSCA is expressive and extensible
• Any technology should be converted to an internal TOSCA format
• Some translators already exist in ONAP

Samuli (Samsung) presentation from Antwerp ….  https://wiki.lfnetworking.org/display/LN/ONS%3AEU+%2719+Technical+Event+Schedule?preview=/19006711/22675630/CNF_Modeling.pptx

Third Review …  Andy Mayer