SDNC is a network controller based on CCSDK, which provides most of the base functionality used to implement the network controller. The SDNC project assembles those components, adding real-time configurable service logic (aka directed graphs) to implement network controller instances or "personas".
The following table lists the Frankfurt functional requirements which impact SDNC.
Requirements |
---|
These requirements require enhancements to existing SDNC functionality, as opposed to new interfaces.
SDNC currently provides 2 interfaces with overlapping capabilities:
All the capabilities of VNF-API are now also provided by GENERIC-RESOURCE-API. Our existing ONAP use cases have been updated to use GENERIC-RESOURCE-API instead of VNF-API. Therefore, our plan is to deprecate VNF-API in the Frankfurt release, and remove the code in the Guilin release.
CCSDK provides the following APIs which are exposed by SDNC:
SDNC itself also provides the following interfaces, not found in CCSDK:
Reference to the interfaces.
All APIs have Swagger documentation, which is referenced in readthedocs
Due to limitations inherent in OpenDaylight clustering - which is based on akka - SDNC should always be run with an odd number of replicas. This is needed to guarantee there can be no "ties" in the akka leader election procedure.
SDNC is used in the following use cases:
None