Project Name:
- Proposed name for the project:
External API Framework - Proposed name for the repository:
ExtApiFw
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 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?
- Service Orchestrator
- A&AI
- DCAE
- SD&C
- Controllers
- What other ONAP projects does this project depend on?
- How does this align with external standards/specifications?
- Base service abstraction Information Model on best in breed standard models (e.g., ONF TAPI, TM Forum SID, etc.)
- MEF LSO Legato
- ONF Core Model and TAPI
- TM Forum SID
- TM Forum Zoom effort and related TM Forum APIs where applicable.
- Are there dependencies with other open source projects?
- ??
Resources:
- Primary Contact Person:
- Andy Mayer, AT&T, am803u@att.com
- Names, gerrit IDs, and company affiliations of the committers
- Alex Vul, Intel, alex.vul@intel.com
- Al Hua, Huawei,
- Jack Pugaczewski, Century Link, Jack.Pugaczewski@CenturyLink.com
- Laurent Leboucher, Orange, laurent.leboucher@orange.com
- Mahesh Jethanandani, Cisco, mahesh@cisco.com
- Mehmet Toy, Verizon, mehmet.toy@verizon.com
- Shahar Steiff, PCCW Global, ssteiff@pccwglobal.com
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- 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:
- JIRA project prefix:
Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix]
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval:
Link to approval of additional submitters:
1) Well defined specifications for the NB APIs (e.g., JSON Swagger). These define what the BSS/OSSs would need to build to.
2) An ONAP implementation of these APIs