SDC Dependencies
- Michael Lando
- Former user (Deleted)
this table was created to map all the SDC dependencies
Component | API name/URI | Type | Direction (incoming/outgoing) | Adjacent module(s) | Information expected | Information provided |
|---|---|---|---|---|---|---|
VID | /sdc/v1/catalog/services | GET | incoming | SDC | a list of all the SERVICES in DCS | |
/sdc/v1/catalog/resources/{uuid}/toscaModel | GET | incoming | SDC | uuid of the service | the csar for the requested uuid | |
using parser | Dependency | sdc-tosca | using the parser API's to retrieve information from the csar | difrent parts of the CSAR according to the API call | ||
SO | SdcDistributionClient subscribed to DMaaP (SDC-NOTIF-TOPIC and SDC-DISTR-STATUS-TOPIC ) | GET/POST | Dependency | Dmaap and SDC | the distribution client subscribes to topics in Dmaap. After the subscription a notification from SDC will be consumed by SO | based on the notification SO downloads the artifact it needs from the SDC catalog. the artifacts used by SO are
from Resource instance. |
/sdc/v1/catalog/services/{serviceName}/{serviceVersion}/artifacts/{artifactName} | GET | incomming | SDC | service info | the artifact file requested | |
APPC | SdcDistributionClient subscribed to DMaaP (SDC-NOTIF-TOPIC and SDC-DISTR-STATUS-TOPIC ) | GET/POST | Dependency | Dmaap and SDC | the distribution client subscribes to topics in Dmaap. After the subscription a notification from SDC will be consumed by APPC | based on the notification APPC downloads the artifact it needs from the APPC catalog. the artifacts used by APPC are
from Resource instance. |
/sdc/v1/catalog/services/{serviceName}/{serviceVersion}/artifacts/{artifactName} | GET/POST | incomming | SDC | service info | the artifact file requested | |
A&AI | SdcDistributionClient subscribed to DMaaP (SDC-NOTIF-TOPIC and SDC-DISTR-STATUS-TOPIC ) | GET | Dependency | Dmaap and SDC | the distribution client subscribes to topics in Dmaap. After the subscription a notification from SDC will be consumed by A&AI | based on the notification A&AI downloads the artifact it needs from the A&AI catalog. the artifacts used by A&AI are
from Resource instance. |
/sdc/v1/catalog/services/{serviceName}/{serviceVersion}/artifacts/{artifactName} | GET | incomming | SDC | service info | the artifact file requested | |
using parser | Dependency | sdc-tosca | using the parser API's to retrieve information from the csar | difrent parts of the CSAR according to the API call | ||
SDNC | SdcDistributionClient subscribed to DMaaP (SDC-NOTIF-TOPIC and SDC-DISTR-STATUS-TOPIC ) | GET/POST | Dependency | Dmaap and SDC | the distribution client subscribes to topics inDmaap. After the subscription a notification from SDC will be consumed by SDNC | based on the notification SDNC downloads the artifact it needs from the SDNC catalog. the artifacts used by SDNC are
from Resource instance. |
/sdc/v1/catalog/services/{serviceName}/{serviceVersion}/artifacts/{artifactName} | GET | incomming | SDC | service info | the artifact file requested | |
using parser | Dependency | sdc-tosca | using the parser API's to retrieve information from the csar | difrent parts of the CSAR according to the API call | ||
VFC | this is an open issue since they cannot consume our utilities as they are a Python project they can implement the logic them selfs since it is based on restcallesto Dmaap and SDC | |||||
DCAE | SdcDistributionClient subscribed to DMaaP (SDC-NOTIF-TOPIC and SDC-DISTR-STATUS-TOPIC ) | GET/POST | Dependency | Dmaap and SDC | the distribution client subscribes to topics inDmaap. After the subscription a notification from SDC will be consumed by DCAE | based on the notification DCAE downloads the artifact it needs from the DCAE catalog. the artifacts used by SDNC are
from Resource instance. |
/sdc/v1/catalog/services/{serviceName}/{serviceVersion}/artifacts/{artifactName} | GET | incomming | SDC | service info | the artifact file requested | |
CLAMP | /sdc/v1/catalog/services | GET | incomming | SDC | none | retrives a list of all service from SDC catalog |
/sdc/v1/catalog/resources | GET | incomming | SDC | retrives a list of all resources from SDC catalog | ||
/sdc/v1/catalog/{assetType}/{uuid}/artifacts/{artifactUUID} | GET | incomming | SDC | asset type : resource or service uuid : id of the resource/service we want the artifact from artifactUUID: id of the artifact we want to dounload | downloades the chosen artifact file. | |
/sdc/v1/catalog/{assetType}/{uuid}/resourceInstances/{resourceInstanceNormalizedName}/artifacts | GET | incomming | SDC | asset type : resource or service uuid : id of the resource/service we want the artifact from resourceInstanceNormalizedName: the name of the instance from which we want to recive the info | returnes alist of the artifacts connected to the choosen instance | |
/sdc/v1/catalog/{assetType}/{uuid}/resourceInstances/{resourceInstanceNormalizedName}/artifacts/{artifactUUID} | GET | incomming | SDC | asset type : resource or service uuid : id of the resource/service we want the artifact from artifactUUID: id of the artifact we want to dounload resourceInstanceNormalizedName: the name of the instance from which we want to recive the info | downloades the chosen artifact file. | |
/sdc/v1/catalog/{assetType}/{uuid}/lifecycleState/{lifecycleOperation} | POST | incomming | SDC | asset type : resource or service uuid : id of the resource/service we want the artifact from lifecycleOperation: checkin checkout | allows to mange the life sycle of a resource and service. | |
VNF-SDK | /onapapi/marketplace/v1/csars/{csarId} | GET | outgoing | SDC | csarid | downloades the CSAR |
/onapapi/marketplace/v1/csars | GET | outgoing | SDC | retrives a list of avilable pacakes | ||
PORTAL | usingportalSDK/sdc2/v2/api | GET/POST | incoming/dependency SDC uses a library provided byportal, using the library we define a servlet that is called from the portal for user mangment | SDC | the API calls are directed into an sdc implementation of this functions:
| the API's return the user data according to the call |
Dmaap | using Cambria client | GET/POST | outgoing | SDC/Distribution client | the SDC creates topics in the Dmaapand subscribers to the status topic | sdc pushes and retrives notifications from the Dmaap |
Policy | SdcDistributionClient subscribed to DMaaP (SDC-NOTIF-TOPIC and SDC-DISTR-STATUS-TOPIC ) | GET/POST | Dependency | Dmaap and SDC | the distribution client subscribes to topics inDmaap. After the subscription a notification from SDC will be consumed by DCAE | based on the notification Policy downloads the artifact it needs from the SDC catalog. |