2018-03-14 [ExtAPI] Meeting notes

Date

Mar 14, 2018 at 10:00AM EST

Meeting Link: https://zoom.us/j/399880266

Discussed

  • Record the Meeting!! (issue with Zoom recording)

  • Introductions

  • API Documentation @Andy Mayer

  • M3 Review passed!

  • Continue ExtAPI Design for Beijing @Ludovic Robert

    • Documentation

    • Repo committs

    • 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?

  • Begin Interlude Use Case discussion

  • Dana Bobko will present an API Versioning proposal (NEXT WEEK )

  • 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 21 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