Project Overview
CCSDK is a set of libraries and base docker containers that are used to create ONAP controllers. SDNC and APPC are both based on CCSDK, and DCAE also uses some CCSDK libraries. The target vision is that most base controller functionality should be implemented as reusable components within CCSDK, and then assembled into specific controller instances or "personas" in the controller projects.
New component capabilities for Dublin, i.e. the functional enhancements
- Controller Design Studio (CDS) : a self-service design tool that allows service designers to define configuration rules for VNFs/PNFs. This tool will be integrated as a subtending editor for SDC in a later ONAP release.
New or modified interfaces
CDS introduces the following new interfaces:
Interface naming
CCSDK provide the following APIs:
- ASDC-API : RESTCONF interface used to process certain non-TOSCA artifacts distributed by SDC (license model updates).
- dataChange : RESTCONF interface pub/sub interface that allows controller to be notified on data change events (note: not currently used in ONAP use cases)
- LCM : RESTCONF interface used to handle LifeCycle Management events
- SLI-API : RESTCONF interface to service logic interpreter. Used primarily for health check.
Reference to the interfaces
All APIs have Swagger documentation, which is referenced in readthedocs
What are the system limits
Since CCSDK is a toolkit, this doesn't really apply.
Involved use cases, architectural capabilities or functional requirements
CCSDK is used in the following use cases:
- vFW
- vDNS
- vCPE
- VoLTE
- CCVPN
- 5G
Listing of new or impacted models used by the project (for information only)
None