2018-06-13[ExtAPI] Meeting notes

Owned by Andy Mayer
Last updated: Jun 13, 2018Version comment
2 min read

Date

Jun 13, 2018 at 10:00AM EDT

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

Discussed

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

  • Introductions

  • Additional Casablanca Proposals

    • @Elizabeth Hoch

      • Service Request Status API

      • Service Request Profile API (may be part of TMF 641)

      • Performance Management API

      • Service Grouping on Service Order and Service Inventory APIs

      • Service Catalog Update Notifications

    • @Adrian OSullivan

      • Relationship of External APIs with MEF and TM Forum

      • Service Modification

      • CC VPN Use Case may help with requirements for Interlude

      • Need support from other component teams to build needed functionality within ONAP

      • Service Catalog: Notifications, and API schema for Service Characteristics (based on OpenAPI)

      • Service Ordering and Activation: Service Modification, Full E2E activation (SO Impacts

      • Service Inventory: Service State; Traversal (Depth and Expand)

      • Potential integration with MSB

      • Interlude Enhancements

    • @Manoj Nair

      • Hybrid Service Management

      • Edge automation Use Cases

      • Relationship with ETSI MEC Architecture

      • Mobile Edge Application Orchestrator and NFVO

      • Use of Legato and Interlude

      • External API is not addressing Presto, but we should identify which other projects are relevant here with the Architecture Sub-committee Explore TAPI 2.0 for Southbound

      • Explore TMF 640 and ETSI OS-MA

      • Need to capture E2E service capabilities

      • Explore Federated Network Slicing

      • ExtAPI to have it's own catalog and inventory for E2E (for coordination of multiple ONAP instances)

Last time:

  • Continue Proposal for Casablanca @Manoj Nair

    • Presented proposal for Casablanca for hybrid service orchestration

      • Support for TMF 640 (or TMF 641); and  TAPI 2.0 and SOL002 for Customer Configuration to Partner Domains (Interlude)

      • Discussion: 

        • Could TMF 641 be used instead of TMF 640

        • Interactions with Partner Domain (Interlude) should be at Service Level not the Resource Level

        • Need to define flows based CCVPN use case to define function interactions and Service Level information

        • Relationship to ONAP Service Information Modeling effort

  • Interlude discussion Mehmet Toy

  • Next Time:

    • Additional Casablanca Proposals

    • Proposal for Casablanca @Manoj Nair

    • Interlude discussion Mehmet 

Working:

  • Continue ExtAPI Design for Beijing @Ludovic Robert

    • Update: Removed VNF creation from scope and notification feature from scope

    • Utilizing the ExternalAPI/NBI repo for Beijing code

    • Making good progress for 29 March milestone

    • 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 20 June 2018

Action items