Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

In ONAP Dublin release, CDS community has contributed design time and run time mS for supporting declarative model driven controller provisioning and configuration management. From the run time perspective, the blueprint processors offers Self-Service-API. The Self-Service API is a single endpoint API that is supported by the blueprint process that is able to execute declarative and model driven controller workflow action (such as DG) that is model in the controller blueprint archive package. 

 CDS API Strategy

The ONAP community shall show case VNF and PNF use case for supporting post instantiation configuration using the config assign and config deploy actions.

config-assign - Resolve config params and generates the configlet based on the resolved params and meshed templates.

config-deploy - Deploy the configlet that has been generated during config-assign action.


Learn more about the workflow actions of config-assign and config-deploy payload definition by clicking on the below two tabs.

 config-assign

action Identifiers container

Name

Data

Type

Description
actionNamestring
blueprintNamestring
blueprintVersionstring
modeenumeration [sync, async]

sync used for config-assign action

async used for config-deploy action

commonHeader Container

Name

Data

Type

Description
originatorIdstringexample: "so"
requestIdstring
subRequestIdstring

payload Container

Name

Data

Type

Description
config-assign-request {container
resolution-keystring
config-assign-properties{containercontains data summary for model information, vnf information, pnf information and instance params.
service-instance-idstring
pnf-idstring

//Note pnf-id is applicable for PNF Use Case. For VNF use case CDS controller blueprint archive will be model to include vnf-id

pnf-namestring//Note pnf-name applicable for PNF Use Case. For VNF use case CDS controller blueprint archive will be model to include vnf-name
service-model-uuidstring
pnf-customization-uuidstring
instanceParam1string
instanceParam2string
etc.




}
closed config-assign-properties container
}
closed config-assign-request


 config-deploy

action Identifiers container

Name

Data

Type

Description
actionNamestring
blueprintNamestring
blueprintVersionstring
modeenumeration [sync, async]

sync used for config-assign action

async used for config-deploy action

commonHeader Container

Name

Data

Type

Description
originatorIdstringexample: "so"
requestIdstring
subRequestIdstring

payload Container

Name

Data

Type

Description
config-deploy-request {container
resolution-keystring
config-deploy-properties{containercontains data summary for model information, vnf information, pnf information and instance params.
service-instance-idstring
pnf-idstring
pnf-namestring
service-model-uuidstring
pnf-customization-uuidstring



}
closed config-deploy-properties container
}
closed config-deploy-request






  • No labels