Project Name:
- Proposed name for the project:
External API Framework - Proposed name for the repository:
externalapi
Project description:
Scope:
- Deliver points of interoperability between ONAP and External Systems
- Initial focus on ONAP 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
initial focus is likely to be: “Service provisioning configuration & activation”, "License management", and “Address allocation management”
Definition of Use Cases, Interactions, and Information Model engaging service providers and BSS/OSS vendors
- 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
- Work with Modeling project 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
- 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.
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 external interface 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 external API artifacts (e.g., JSON/Swagger) to be collected and referenced.
- Define external API capabilities to support the Change Management project
- Will work with the Modeling project to: identify overall modeling guidelines and approaches, determine modeling tools and tool chaining, and identification of industry standard models (e.g., TMF SID, ONF TAPI, etc.) that may be applied to the APIs
- Service Orchestrator: Will work closely with the Service Orchestrator team to gather information about the relevant Service Orchestrator APIs (particularly the Service Instantiation API). Will collaborate with Service Orchestrator team to ensure that APIs remain consistent for R1.
- External APIs team will work closely with the Standards Coordinator as there will be related activities in the TM Forum, MEF, etc.
- Align with ONAP Use Cases
- A&AI
- DCAE
- SD&C
- Controllers
- DMaaP
- Reference VNFs (related Use Cases)
- How does this align with external standards/specifications?
- Work with Modeling project to determine base service abstraction Information Model on best in breed standard models (e.g., MEF 7.3 Service Info Model, etc.)
- MEF LSO Legato (MEF 7.3 Service Info Model)
- TM Forum Zoom effort and related TM Forum APIs where applicable. TM Forum APIs to consider include:
- Service Catalog (TMF633)
- Service Order (TMF641)
- Resource Order (TMF652)
- Service & Resource Activation & Configuration (TMF640)
- Service Inventory (TMF638)
- Are there dependencies with other open source projects?
Resources:
- Primary Contact Person:
- Names, gerrit IDs, and company affiliations of the committers and contributors:
- Abinash Vishwakarma, Netcracker, abinash.vishwakarma@NetCracker.com
- Alex Vul, Intel, alex.vul@intel.com
- Al Hua, Huawei, al.hua1@huawei.com
- Chen Yan, China Telecom, chenyan.bri@chinatelecom.cn
- Jack Pugaczewski, Century Link, Jack.Pugaczewski@CenturyLink.com
- Jay Akins, IBM, jakins@us.ibm.com
- Jeff Mitryk, AT&T, jm5764@att.com
- Joe Houle, AT&T, jh2974@att.com
- Joël Viale, IBM, joel.viale@fr.ibm.com
- Julien Grosso, Orange, julien.grosso@orange.com
- Laurent Leboucher, Orange, laurent.leboucher@orange.com
- Ludovic Robert, Orange, ludovic.robert@orange.com
- Mahesh Jethanandani, Cisco, mahesh@cisco.com
- Maopeng Zhang, ZTE zhang.maopeng1@zte.com.cn
- Marc-Alexandre Choquette, Bell Canada, m.a.choquette@bell.ca
- Marc Volovic, Amdocs, marc.volovic@amdocs.com
- Mark Gibson, Amdocs, markgi@amdocs.com
- Matthieu Geerebaert, Orange, matthieu.geerebaert@orange.com
- Mehmet Toy, Verizon, mehmet.toy@verizon.com
- Murat Turpcu, Turk Telekom, murat.turpcu@turktelekom.com.tr
- Nicolas Laplaud, Orange, nicolas.laplaud@orange.com
- Nigel Davis, Ciena, ndavis@ciena.com
- Romain Gimbert, Orange, romain.gimbert@orange.com
- Raghu Ranganathan, Ciena, rraghu@ciena.com
- Raluca Sirbu, AT&T, rs2184@att.com
- Shahar Steiff, PCCW Global, ssteiff@pccwglobal.com
- Siva Dhurvas Sivakumar, AT&T, ds2345@att.com
- Srinivasa Vellanki, Amdocs, srinivasa.vellanki@amdocs.com
- Tara Cummings, Ericsson, tara.cummings@ericsson.com
- Troy Saulnier, Bell Canada, troy.saulnier@bellaliant.ca
- Xiaojun Xie, China Telecom, xiexj.gd@chinatelecom.cn
- Yawei Tian, China mobile, tianyawei@chinamobile.com
- Xiangyang Yuan,China mobile, yuanxiangyang@chinamobile.com
- John Strassner, john.sc.strassner@huawei.com, Huawei (gerrit id strazzie123)
- Kevin McDonnell, Huawei, kevin.mcdonnell@huawei.com
- Ignacio Perez Gonzalez, IBM, ignacio.perez@es.ibm.com
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- Potentially the Service Orchestrator's Service Instantiation API
- 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:
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 for release 1:
*Link to TSC approval:
Link to approval of additional submitters: