2019-11-18 ONAP Model Enabled Meeting
- Bob Papa
Date
Nov 18, 2019
Attendees
@Bob Papa
@Andy Mayer
@Yuriy Malakov
@Ciaran Johnston
@sal Ricci
Discussion Items
Item | Who | Notes |
|---|---|---|
Agenda | @Bob Papa | 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** |
General Discussion | All | Reviewed our last meeting notes; No conflicts Make sure we don’t break anything Tal presented ideas to SO last week. Puccini POC with SO. Tal starts at 25 minutes into the recording. They don't have a specific roadmap yet. What are they trying to solve? Tal is wanting to bring TOSCA in to drive orchestration Tal has a very good TOSCA background knowledge TOSCA driven thru out the system, what are the gaps? Pucci takes Tosca and converts to CLOUT Puccini does not do orchestration Parser is a Parser A parser is not orchestration Tosca can’t replace everything, would still need technology specific artifacts Delegate some of the low level processing to Lower level tech instead of trying to do it all in Tosca Need to keep involved with the SO POC Parser service versus common library (there was a user story that was being discussed during arch call Define principles Each component should have a common understanding tosca translation BPMN needs recompiles…?? No recompiles but need to be rebuilt and redistributed. Just an XML file. Use standards but should ONAP be tied to a slow moving standard committee. ETSI to define extension points. Need a demo on CDS. Maybe on how Bell Canada is using CDS. Need more info on ETSI modeling. Next session Dec 2nd …. Yuriy will cover an ETE flow using CDS. Session will start an hour later. Following sessions, Ciaran will have someone cover ETSI modeling.
|