| Table of Contents |
|---|
Scope
Enhance NETCONF support in ONAP supporting 5G and other use cases.
Proposed UC to focus on in Dublin for configuration with NETCONF:
- Post-instantiation (triggered by SO)
- Including final configuration step (36/37) in the PNF PnP UC
- (Stretch goal) Configuration modification (e g triggered by Policy)
Specific requirements on NETCONF support in ONAP:
- Officially support both PNFs and VNFs for north-bound controller APIs in the use cases
- Support for NETCONF over TLS (RFC7589)
- Support for YANG 1.1 (RFC7950) modules in addition to YANG 1.0
Presentations:
Development Status
Part 1: Protocol support
The first part of the feature focuses on supporting NETCONF/TLS and YANG 1.1 south-bound from the ONAP controller to PNFs and VNFs. OpenDaylight netconf-connector is proposed as the NETCONF client. TLS support has been added in the latest release (Flourine) although bug fixes may be required. One of the ONAP additions will be a run-time mechanism in the controller to configure the keys and certificates used by ODL for NETCONF/TLS.
NETCONF requests could be triggered directly by using the ODL RESTCONF API for testing purposes, or from a directed graph (assuming suitable plugin is available).
| Project | PTL | JIRA | Description | Status | ||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
APPC SDNC CCSDK |
| Enable NETCONF and TLS support in OpenDaylight when used by ONAP controller
Verify configuration with NETCONF via controller/ODL with mix of YANG 1.0 and YANG 1.1 modules. | PTLs notified Tickets have been created. Note: It is planned to start with SDNC. In order to use NETCONF/TLS with APPC as well, an additional ticket should be defined for (3), similar to SDNC-556. | |||||||||||||||||||||||||||||||||||||||||||||
| VNFRQTS |
| Update xNF requirements
| PTL notified Tickets have been created. Next step is to identify specific xNF requirements that are impacted. |
Part 2: Configuration use cases
case, based on NETCONF/TLS as the device protocol. The solution with utilize Controller Design Studio (CDS) components including the run-time blueprint processor.
| Project | PTL | JIRA | Description | Status | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
CCSDK |
| Additional support for NETCONF/TLS configuration in the controller layer |
- Configuration blueprint format
- Possible to specify NETCONF/TLS as device protocol
- Possible to attach YANG XML template as artifact
- PNF or VNF as level/scope
- Controller north-bound APIs and implementation
- PNF or VNF as target for request
- Template lookup and download to target via ODL netconf-connector
- Self-service support for the configuration use cases
- User interface
- Blueprint distribution
| PTL notified Ticket has been created. Note: As CDS components are under active development during Dublin, there are dependencies to several other Jira issues as well. | |||||||||||
SO |
|
UC1: Post-instantiation configuration
- Orchestration of service with PNF
- Develop extended PNF workflow that includes configAssign and configure steps following PNF registration
PTL notified
Ticket has been created.
| Extend PNF support in the Service Orchestrator
| PTL notified Tickets have been created. Note: The PNF workflow extension will share some code with the VNF workflow, some of which is developed as part of other SO Jira issues. | ||||||||||||
| INT | Yang Xu |
| Support NETCONF/TLS in the PNF simulator | PTL notified |
Feature has been |
delivered. |
Testing
See the the Integration test page for details: