...
USE CASE | API Impacts |
---|---|
Bulk PM | DMaaP DR API Updates. See the Wiki page for details on the Data Router Changes: 5G - Bulk PM (Casablanca carry-over items) Next Steps: Confirming API details. |
Configuration with NetConf | Separate initiative E2E automation via CDS. Added new API between SO & Controller Design Studio (CDS). CDS team is defining this new API. This U/C will use that new API. The CDS API/Wiki is here: (add link) Next Steps: Dependency between this U/C with the CDS work. Basic support of API has been delivered. Some API details to be finalized. |
OOF / PCI | API changes are needed. Config DB API, SDN-R. APIs for individual nodes record updates in Config DB. Bulk APIs for updating. API associated with SDN-C project. SON MS & Policy & OOF Next Steps: JSON swagger document being produced. . Keep in sync with the corresponding Yang Model. OOF API: micro-service calls (optimization and passes data). Freeze on API changes. Next Steps: JSON swagger document being produced. (in progress) |
PNF PNF S/W Upgrade | Roll-back API. From SO to SDN-C (Controller). South-bound changes (captured in the Ansible Playbooks), impacting the external controller rather than the ONAP platform. Data pushed from API so ssouth-bound APIs will have right data (in the payload). Reusing LCM API (between SO to SDN-C) which already has the rollback in there. The Rollback action is already specified in SDN-C. In the yang model for LCM.Yang (in CCSDK repository) file. Mandatory/generic header fields need to make them optional so that we can use them as a generic API to pass specific 5G info in the Payload. Currently Rollback function was not implemented yet (so no one is currently using this API). Next Steps: API definition details in progress. Changing field options, and defining the payloadNext Steps: Plan for next week (Mar 6), will have draft for API. |
USE CASES WITH NO API IMPACT | |
PNF Plug and Play | New API for the Update Micro-service to SO (from the pnfUpdate event trigger) from Policy for the Reregistration Story. The "user" will be the BBS Micro-service U/C. Next Steps: Ajay in DCAE has accepted this micro-service. Final details of the new service-update API is being defined in conjunction with SO project (Seshu). |
PNF Pre-onboarding / Onboarding | No API Impacts. |
5G FM Meta Data 5G PM Dictionary | No API changes |
Network Slicing | (Modeling only) - No API Changes |
...