Date
at 10:00AM EDT
Meeting Link: https://zoom.us/j/399880266
Discussed
- Introductions
- Review Action Items from previous call
- Review Ordering and Activation Use Case
- Discuss UML tools (Tara uploaded Papyrus files)
- TMF and ONAP APIs discussion (need to add Service Config & Activation API, Service Catalog API)
- Discuss Next Call scheduled to take place on 23 August 2017 (Alex Vul will run it)
The meeting recording may be found at: EXTAPI Meeting Recording 16AUG2017.mp4
Next time
- Alex: Latest API Project description, division between outer and inner APIs; use of a single API structure
- Discuss Service Descriptor Guidelines
- Consider looking ETSI SOL005 for NS instantiation
- Begin exploring TOSCA guidelines for Service Descriptor
- TM Forum API update (need to add Service Config & Activation API, Service Catalog API)
Action items
- Alexander Vul, Andy Mayer invite joint session with MSB, CLI (and UI), plus Chris Donley DUE 16 AUG 2017 (Latest API Project description sent, division between outer and inner APIs; want to use a single API structure)
- Alexander Vul will add link to MSB API description to our wiki. by 23 AUG 2017
- Nigel Davis , Andy Mayer and Abinash Vishwakarma will Compare and Contrast the ONAP Service Instantiation API with TM Forum API Due 16 AUG 2017
- Alexander Vul and Andy Mayer will create a draft of a conceptual model and sequence diagram DUE 30 AUG 2017
- Andy Mayer to make user-4e592 a committer on the EXTAPI repo DUE 16 AUG 2017
1 Comment
Abinash Vishwakarma
Hi,
I have uploaded the draft document of comparison between TMF and ONAP APIs which I presented in today's call in the following location.
https://wiki.onap.org/download/attachments/8227019/ONAP%20Vs%20TMF%20API%20V0.1.pptx?api=v2
Additionally I would also like to put the question which we discussed during presentation today:
The scope of SO in ONAP is below the OSS/BSS layer and it exposes the NS instance creation APIs as part of service fulfillment which is northbound to OSS/BSS. Hence the mapping is done with OS NS Instance with RF APIs of TMForum.
We need to look into the current model of MSO and GSO too for this.
Thanks and Regards,
Abinash Vishwakarma