Page Status: Copied from
...
Guilin-R7 - Aug-24-2020
Component Status: Pending PTL
...
updates and ArchCom Review
Last Reviewed on:
Certified by:
1. High Level Component Definition and Architectural Relationships
SDN-C / App-C:
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- Configure Network Functions (VNF/PNF)
- Provides programmable network application management platform:
- Behavior patterns programmed via models and policies
- Standards based models &protocols for multi-vendor implementation
- Extensible SB adapters such as Netconf, Ansible, Rest API, etc.
- Operational control, version management, software updates, etc.
- Local source of truth
- Manages inventory within its scope
- Manages and stores state of NFs
- Supports Configuration Audits
2. SDN-C/APP-C API definitions
Controller provides the following interfaces:
...
| Interface Name | Interface Definition | Interface Capabilities | API Spec (Swagger) |
|---|---|---|---|
| CONE-5 | Rest API | An interface for communication with external systems such as IP management | |
| CONE-6 | Resource Chef API | An interface for configuration and Lifecycle management of network resources using Chef protocol | |
| CONE-7 | Resource NetConf API | An interface for configuration and Lifecycle management of network resources using NetConf protocol | |
| CONE-8 | Resource Ansible API | An interface for configuration and Lifecycle management of network resources using Ansible protocol | |
| SDCE-6 | SDC Interface | An interface to receive resource Templates from SDC design catalog | |
| CDSE-1 | CDS Interface | An interface to receive resource blueprint from CDS | |
| AAIE-1 | Inventory Service Interface | An interface to create, update, query, and delete resource information and relationships | |
| POE-2a | PDP Query API | Policy Decision Point query for IP address |
3. Component Description:
4. known system limitations
- Lack of clarity & roles in the controller (which controller does what?)
- Proliferation of controller instances (many similar yet different controller instances)
- Divergence of controller implementation (lack of common controller framework)
- Duplicate and uncoordinated interfaces (lack of uniform common services in southbound interfaces)
- Controller resiliency and horizontal scaling
5. Used Models
Controllers use the following models:
- TOSCA
- YANG
6. System Deployment Architecture
Controller consists of the following containers:
...
draw.io Diagram border true viewerToolbar true fitWindow false diagramName xxxx Deployment View simpleViewer false diagramWidth 1291 revision 1
7. New Release Capabilities
- Upgrade of ODL to Sodium (SR3 initially - SR4 when available in late August)
- Upgrade to Java 11
- OpenDaylight separation:
- Currently, CCSDK/SDNC/APPC is installed as a set of OSGi features within the OpenDaylight karaf container. This means that each ONAP release is tightly coupled with a specific OpenDaylight release. In order to loosen this coupling - so that ONAP deployers can use the same ONAP release with whatever OpenDaylight release suits their needs - CCSDK/SDNC/APP will move towards a microservice-based architecture, where components are installed as springboot-based containers.
- RunTime Config DB is an independent component that is integrated with the ODL SDN-C controller in R7 (Guilin release). The RunTime Config DB capabilities are part of CC-SDK. q.v. CONFIGURATION & PERSISTENCY SERVICE R6 for more information.
8. References
- APP-C overview & User Guide: https://docs.onap.org/en/casablanca/guides/onap-developer/developing/index.html#application-controller
- SDN-C overview & User Guide: https://docs.onap.org/en/casablanca/guides/onap-developer/developing/index.html#software-defined-network-controller
...