2018-02-28 Meeting notes
Date
Feb 28, 2018 at 10:00AM EST
Meeting Link: https://zoom.us/j/399880266
Discussed
Record the Meeting!! (issue with Zoom recording)
Introductions
Review proposed ExtAPI Design for Beijing @Ludovic Robert
ACTION: Need to schedule meetings with SDC, SO, and A&AI to discuss API mapping; Also Run-time Catalog.
ISSUE: Is SDC Providing CSAR from Catalog API? Could SDC provide a simple service view with input parameters of the service?
ISSUE: Does SO require customer on instantiation requests? Is A&AI really keeping Customer (or Consumer) information?
External API context @Manoj Nair (NEXT WEEK 28 FEB)
Dana Bobko will present an API Versioning proposal (NEXT WEEK )
Review ExtAPI slides that were reviewed by the Architecture sub-committee @Andy Mayer
MEF Legato Interface Profile Spec project proposal @Andy Mayer
Put link to MEF TOSCA service spec on ONAP wiki.
ACTION: Ask Raghu about YAML files
MEF Interlude Project Proposal Update: Mehmet Toy (Verizon)
Use Case draft is available from MEF for comments.
Info Model (for MEF Service Descriptors) based on MEF Core Model is being worked
ONAP should generalize MEF Interlude use cases
Begin discussions on User Stories / Use Cases; State Models; Sequence diagrams for External and Internal interactions with ONAP components @Andy Mayer
End-to-end Operation Threads
Service Catalog
Query Service Catalog
Retrieve Service Model
Service Ordering
Place Service Order
Query Service Order
Retrieve Service Order
Delete Service Order
Retrieve Service Order State
Subscribe to Service Order Notifications
Receive Service Order Notifications
Service Inventory
Query Service Inventory
Retrieve Service
Retrieve Service State
Service Topology (spec only)
Query Service Topology
Retrieve Service Topology
License Management (spec only)
Receive License Usage Notifications
Recording:
Upcoming:
Next call will take place on 7 March 2018
Architectural considerations for External APIs (mapping to ONAP components)
User Stories / Use Cases; State Models; Sequence diagrams for External and Internal interactions with ONAP components
Continue review and refinement of ONAP Common Model UML (Service Abstraction focus)
Discussion on coordination with Architecture, Modeling, and MSB efforts (@Alex Vul)
Action items