...
The primary focus of the ONAP release 4 (Dublin) is to advance platform maturity, with a focus on S3P (Scalabllity, Stability, Security and Performance).
Use Cases
CCSDK SDNC will support the following use cases from previous releases:
- vFW
- vDNS
- vCPE
- VoLTE
- CCVPN
CCSDK SDNC will also support the following additional use cases for Dublin:
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.One critical long term objective for the SDN-C project is support for integration with other third party SDN Controllers (e.g. Open Contrail), well as integration with the SDN Agent project from Open-O. For the Dublin release, since our primary goal is to support the use cases identified above and to improve platform maturity, the degree to which we support such integration will be dictated by the needs of those use cases. However, we do want to bear in mind that such integration is critical and will be included in our release plans going forward.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
...
| Deliverable Name | Deliverable Description | Deliverable Location |
|---|---|---|
| CCSDK SDNC Source Code | Source code for CCSDK SDNC project | ONAP gerrit |
| CCSDK SDNC Maven Artifacts | Compiled code that can be referenced in other projects as maven dependencies | ONAP Nexus |
| CCSDK SDNC Docker Containers | Docker containers associated with SDNC project:
| ONAP Nexus |
| Documentation | User and developer guides | ONAP Wiki |
| CCSDK SDNC CI/CD automation | Scripts to automate compilation and deployment of maven artifacts and docker containers | ONAP gerrit ONAP Jenkins |
Sub-Components
Subcomponents of each ONAP project may be found on the Resources and Repositories page on this wiki. Please see the CCSDK SDN-C section of that page for subcomponent list of SDN-C.
ONAP Dependencies
SDN-C depends on the following projects:
- Active and Available Inventory (A&AI)
- Common Controller SDK (CCSDK).
- Service Design and Creation (SDC)
- Data Movement as a Platform (DMaaP)
- Documentation
- Integration
- External API
- Modeling
- Multi VIM/Cloud
- Policy
Architecture
High level architecture diagram
...
The following diagram illustrates how CCSDK is used by the controller projects:
High level architecture diagram
The following diagram shows the high level architecture of SDNC:
The major architectural components of the SDN-C controller are:
- Device Data Models : Yang models that define interfaces to devices (virtual or physical) that the SDNC configures
- Service Network Data Models : Yang models that define data maintained within the SDNC about the network used by the set of services supported by this SDNC instance
- Service Chain Data Models : Yang models that define how services supported by an SDNC instance can be chained
- Service Data Models : Yang models that define data maintained within the SDNC for the set of services it supports
- Directed Graphs : programmable logic, updatable at run time with no restart, that define the behavior of the SDNC
- Service Logic Interpreter : module provided by CCSDK which allows platform to execute directed graphs
- API Handler : code (mostly generate from service Yang models) which implements RESTCONF API into SDNC. Most API handlers should follow the following pattern:
- Call directed graph named after invoked RPC, passing RESTCONF RPC parameters as Java Properties object.
- Return results from directed graph invocation as response to RESTCONF RPC
- Interface adaptors - code that allows directed graphs to invoke external interfaces
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | ||
|---|---|---|---|---|---|---|
| Performance | 0 | 0 | Awaiting guidance from Benchmark subcommittee |
| ||
| Stability | 0 | N/A | As a project that provides a library framework, CCSDK has no standalone component that can be soaked1 | SDNC will perform 72 hour soak at component level. We assume that integration team will also do a 72 hour ONAP soak which includes SDNC. |
| |
| Resiliency | 1 | 2 | While CCSDK itself has no standalone component, it does provide an OpenDaylight docker container used by SDNC and APPC. In Beijing, CCSDK will support a clustered OpenDaylight configuration in Kubernetes, as well as a clustered database, to allow for automated detection and recovery within a site. SDNC will use that configuration to meet this requirement. See SDN-C Clustering on Kubernetes for further details |
| ||
| Security | 0 | 1 | CCSDK will achieve 50% code coverageSDNC will improve test coverage to > 50% |
| ||
| Scalability | 0 | N/A | Scaling does not apply to CCSDK itself, as a set of libraries | 1 | SDNC can be scaled either by adding additional OpenDaylight containers and/or database containers, or by deploying multiple instances of SDNC cluster. |
|
| Manageability | 1 | 1 | CCSDK SDNC will support ONAP standard logging. |
| ||
| Usability | 1 | 1 | See readthedocs and wiki. |
|
API Incoming Dependencies
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| A&AI : schemasA&AI schemas used by CCSDK aaa-service moduleVNF | API used to read/write information about VNFs | Defined in seed code | Included in seed code | TBD |
| SDC : distribution client | API used by ueb-listener (in CCSDK sdnc-northbound repo) to receive to distribute artifacts from SDC to subscribers | Defined in seed code | Included in seed code | TBD |
| DMaaP | API used to receive DHCP event notification | 8/23/17 | 8/23/17 | DMaaP API |
API Outgoing Dependencies
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | ||
|---|---|---|---|---|---|---|
| Maven librariesHealthcheck | Libraries used as dependencies by SDN-C, APP-C, DCAE and OOMAPI used to verify that platform is available and healthy | Included in seed code | Delivered in seed code | Javadoc will be provided | Docker containers | Base docker containers will be provided which can be used by SDN-C and APP-C as a basis for their docker containersTBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki) |
| Generic VNF API | API used to request resources for VNFs. Will be deprecated in Beijing in favor of Generic Resource API. | Included in seed code | Delivered in seed code | TBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki) | ||
| Generic Resource API | API used to request resources for VNFs. This API is a superset of the generic VNF API, which it replaces | Included in Amsterdam release | Delivered in Amsterdam | TBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki) |
Third Party Products Dependencies
| Name | Description | Version |
|---|---|---|
| OpenDaylight | OpenDaylight SDN Controller Platform | Fluorine |
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...