...
- ConfigAssign - Resolve application params and generates a configlet for network base-configuration and incremental configlets for PNF, VNFs and in the future CNFs.
- ConfigDeploys - Deploy the configlet that is generated as part of the configAssign action to the network using netconf/restconf.
SDNC will also use a new API provided by CCSDK for 5G OOF/PCI called "oofpcipoc-api", which supports the following RPCs:
- greeting
- configuration-phy-cell-id
- generic-neighbor-configuration
- add-neighbor
- delete-neighbor
SDNC will also support interfaces to NETCONF devices in Dublin over TLS transport, using the NETCONF/TLS support introduced in the OpenDaylight Fluorine release.
Interface naming
SDNC exposes the following APIs implemented by CCSDK:
- 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.
- selfservice-api : gRPC interface used with CDS (see above)
- oofpcipoc-api : RESTCONF interface for OOF/PCI integration
SDNC itself also provides the following interfaces, not found in CCSDK:
...
SDNC is used in the following use cases:
- vFW
- vDNS
- vCPE
- VoLTE
- CCVPN
- 5G
- BBS
Listing of new or impacted models used by the project (for information only)
...