Page Comparison

...

• 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 

...

• Next call will take place on 30  May 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)20 June 2018

Action items