Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Deliver points of interoperability between ONAP and External Systems
  • Initial focus on ONAP External APIs to BSS/OSS (i.e., MEF Legato)
    • Service Catalog
    • Service Ordering (including Service Instantiation)
    • Service Inventory Inventory (specification focus) (stretch goal: implementation)
    • Service Topology (stretch goal) (specification focus)
    • License Usage (stretch goal) (specification focus)
  • Initial focus on specification of ONAP External APIs supporting Inter-Provider (i.e., MEF Interlude)
    • Service ControlControl (specification focus)
    • Service State (operational state) (specification focus)
    • Service Inventory / Details (specification focus)
  • Explore Role-based view of single APIs descriptors for both Legato and Interlude

  • Alignment with MEF Legato, MEF Interlude and TM Forum APIs

  • Definition of Use Cases, Interactions, and Information Model engaging service providers and BSS/OSS vendors

  • UML Models (Eclipse Papyrus) (with Modeling sub-committee) and API definition (JSON Swagger) for

    • License Usage

    • Service Modeling and Service Topology

    • Service Inventory

    • Service State Management

    • Service Quality Management

  • Define API Styles to be applied to External APIs (along with Micro-service Bus (MSB) and Modeling Project)

  • API development (in conjunction with specific ONAP component projects)

    • Well defined specifications for the NB APIs (e.g., JSON Swagger). 
    • ONAP implementation of these APIs
  • Architecture for External APIs
    • Identification and involvement of stakeholder ONAP projects
    • Describe key External API foundation functionalites
    • Work with Architecture and MSB projects
  • Document the role and requirements of External APIs in Model Driven ONAP
    • Work with Modeling project and sub-committee to explore a Model Driven approach: a cohesive way to have a shared view of information across ONAP external interfaces that can be used for or be input into a model driven process whereby the cost of delivering platform functionality is drastically reduced and the time to delivery is dramatically decreased.
  • Explore use of Model Driven Tool Chain to automatically generate APIs based on models with Modeling Project

...

Main deliverables of this project may include: User Stories; Use Cases and Interactions (e.g., UML); Information Models (e.g., UML); Data Models (e.g., JSON); Interface Profiles and Functional Definition; ONAP Component Mapping and Functional Analysis; Code contribution for External API Agent functionality.

Resources:

  • Primary Contact Person: 
  • Names, gerrit IDs, and company affiliations of the committers and contributors:

...

Participants for Beijing: