Page Comparison

DMaaP DR API Updates.

Next Steps: Confirming API details.

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.

Next Steps: Dependency between this U/C with the CDS work. Basic support of API has been delivered. Some API details to be finalized.

API changes are needed. Config DB, 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.

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).

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 s-bound APIs will have right data (in the payload).

Next Steps: Plan for next week (Mar 6), will have draft for API.

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 s-bound APIs will have right data (in the payload).

Next Steps: Plan for next week (Mar 6), will have draft for API.

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).