...
Project Overview
...
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 new functional requirements CCSDK/SDNC is committing to support for the Frankfurt Honolulu Release:
| Requirements | Companies Supporting Requirement | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| IBM | ||||||||||
| IBM | ||||||||||
| Orange, Samsung | ||||||||||
| Ericcson | ||||||||||
| Huawei (1) | ||||||||||
| Bell Canada (1) |
(1) Being evaluated for Honolulu, but not yet committed.
...
The following epics represent the minimum viable product of the CCSDK Guilin /SDNC Honolulu Release:
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project =in (CCSDK,SDNC) and issuetype in (epic) and (labels != relman OR labels is EMPTY) and fixversion="Honolulu Release" and priority >= high serverId 425b2b0a-557c-3c0c-b515-579789cceedb
The following epics are also in scope for GuilinHonolulu, but are not considered of the minimum viable product. In the event of unanticipated resource constraints, these could be reduced in scope or deferred without impacting any functionality deemed by the TSC as critical for GuilinHonolulu.
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project =in (CCSDK, SDNC) and issuetype in (epic) and (labels != relman OR labels is EMPTY) and fixversion="Honolulu Release" and priority< high serverId 425b2b0a-557c-3c0c-b515-579789cceedb
These requirements require enhancements to existing CCSDK/SDNC functionality, as opposed to new interfaces.
...
We plan to test both versions in the Honolulu release to validate that the springboot-based implementation is a fully backward compatible replacement. If successful, the ODL version of GENERIC-RESOURCE-API will be deprecated in the Istanbul release and removed in Jakarta.
If they are modified, are
...
they backwards compatible?
Yes. Care is taken to ensure backwards compatiblity:
- Any new fields added are declared as optional, with reasonable defaults assigned, so that version N of CCSDK/SDNC can be used with version N-1 of its interface peers.
Interface naming (point to an example)
...