Checkpoint

List by each relevant project

Evidences

How to?

List of not supported/wrongly supported etc. APIs along with the corresponding project name

 None

VID:  VID R4 M3 Architecture Review :

  Display cloud-owner of each cloud region

  Each cloud-region will be presented to the user along with its owner, based on A&AI data

VFC: VF-C R4 Architecture Review :

  Upgrade Mutlicloud API invocation to support Centralized Representation and Consistent Identification of Cloud Region functional requirement

APPC:

    Patch: https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=appc-outbound/appc-aai-client/provider/src/main/java/org/onap/appc/aai/client/aai/AaiService.java;h=76336c1de4e448fd678d09296f96ab9f563bd3f0;hb=0190a9cfa67b3470d6cbdab2277f1b68a53d84bb

UUI: Usecase-UI Dublin Release Planning :

  Support Functional Requirements identified: Centralized Representation and Consistent Identification of Cloud Regions In ONAP

SDNC:   https://gerrit.onap.org/r/#/c/67413/

SO:   Claimed being ready , the evidence is still to be provided.

OOF: OOF Dublin (R4) Architecture Alignment :

    MultiCloud: https://docs.onap.org/en/latest/submodules/multicloud/framework.git/docs/specs/multicloud_resource_capacity_check.html   (updated API for F-GPS)

In case some parts of use case/ functional requirement implementation are broken, this will raise the flag

Link to the API Documentation

 

UUI-> VFC: VF-C R4 API Update

VFC→ MultiCloud: https://docs.onap.org/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-APIv1-Specification.html

VID→SO: https://docs.onap.org/en/latest/submodules/so.git/docs/api/offered_consumed_apis.html

SO->SDNC: https://onap.readthedocs.io/en/latest/submodules/sdnc/oam.git/docs/apis/genericresource.html

SO → MultiCloud:  https://docs.onap.org/en/latest/submodules/multicloud/framework.git/docs/specs/multicloud_infra_workload.html

OOF->MultiCloud : https://docs.onap.org/en/latest/submodules/multicloud/framework.git/docs/specs/multicloud_resource_capacity_check.html  


This field is optional, will be filled in in case use case/functional requirements owner believes it can bring more clarity

Additional information

 

 

This field is optional, will be filled in in case use case/functional requirements owner believes it can bring more clarity

  • No labels