Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Project Name:

  • Proposed name for the project: External API Framework
  • Proposed name for the repository: externalapi

Project description:

  • This project will describe and define the APIs between ONAP and External Systems.
  • Proposed initial focus may be on the Common Northbound APIs between ONAP and BSS/OSS.

  • Common Northbound APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP using their existing BSS/OSS environment with minimal customization.

Scope:

  • Deliver points of interoperability between ONAP and External Systems
  • Initial focus on ONAP Northbound APIs to BSS/OSS
  • May support the following capabilities:
    • Service feasibility; 
    • Service provisioning configuration & activation; 
    • Usage events & metrics; 
    • License accounting; 
    • Service performance & quality; 
    • Service Trouble management;
    • Service policy; 
    • Capacity engineering;
    • Address allocation management

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

  • API development
    • Well defined specifications for the NB APIs (e.g., JSON Swagger). 
    • ONAP implementation of these APIs
  • Explore use of Tool Chain to automatically generate APIs based on models

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?

    • What other ONAP projects does this project depend on?
      • This project will also analyze the functionality of the implemented set of APIs in ONAP components that are relevant to providing the described Northbound functionality. Mapping and alignment between this project and the ONAP components implementing the supporting APIs is essential since functional API gaps and potential enhancements will be identified based on the functional analysis. This project also allows the pertinent ONAP component specific Northbound API artifacts (e.g., JSON/Swagger) to be collected and referenced. 
      • Define Northbound API capabilities to support the Change Management project
      • Service Orchestrator
      • A&AI
      • DCAE
      • SD&C
      • Controllers
      • Reference VNFs (related Use Cases)
  • How does this align with external standards/specifications?
    • Base service abstraction Information Model on best in breed standard models (e.g., TM Forum SID, MEF 7.3 Service Info Model, etc.)
    • MEF LSO Legato (MEF 7.3 Service Info Model)
    • TM Forum SID
    • TM Forum Zoom effort and related TM Forum APIs where applicable.
  • Are there dependencies with other open source projects?
    • ??

Resources:

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
      • This project is vendor neutral and open-sourced under the Apache license from the OPEN-O project
  • Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name: externalapi
  • JIRA project prefix: externalapi

Repo name: 

  • org.onap.externalapi/nbi


Lifecycle State: incubation
Primary Contact: Andy Mayer, AT&T, am803u@att.com 
Project Lead: Andy Mayer, AT&T, am803u@att.com
mailing list tag [externalapi] 
Committers:


*Link to TSC approval: 
Link to approval of additional submitters: 


  • No labels