Controller Design Studio-Dublin-[11]-API Strategy

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.

What is CDS Dynamic API Strategy?

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. 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 above two tabs.

config-assign

action Identifiers container

Name	Data Type	Description
actionName	string
blueprintName	string
blueprintVersion	string
mode	enumeration [sync, async]	sync used for config-assign action async used for config-deploy action

commonHeader Container

Name

Data

Type

Description

originatorId

string

example: "so"

requestId

string

subRequestId

string

payload Container

Name	Data Type	Description
config-assign-request {	container
resolution-key	string
config-assign-properties{	container	contains data summary for model information, vnf information, pnf information and instance params.
service-instance-id	string
pnf-id	string	//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-name	string	//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-uuid	string
pnf-customization-uuid	string
instanceParam1	string
instanceParam2	string
etc.

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

config-deploy

action Identifiers container

Name	Data Type	Description
actionName	string
blueprintName	string
blueprintVersion	string
mode	enumeration [sync, async]	sync used for config-assign action async used for config-deploy action

commonHeader Container

Name

Data

Type

Description

originatorId

string

example: "so"

requestId

string

subRequestId

string

payload Container

Name	Data Type	Description
config-deploy-request {	container
resolution-key	string
config-deploy-properties{	container	contains data summary for model information, vnf information, pnf information and instance params.
service-instance-id	string
pnf-id	string
pnf-name	string
service-model-uuid	string
pnf-customization-uuid	string

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