5G - Configuration with NETCONF
- Oskar Malm
- Kamel Idir
- Raj Gumma
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 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 | @Takamune Cho @Dan Timoney | APPC-1277: ODL upgrade to Flourine SR2Closed APPC-1258: Support clustered configuration for the odl-netconf-topology packageClosed SDNC-551: OpenDaylight Fluorine SupportClosed SDNC-555: Install ODL features for NETCONF by defaultClosed SDNC-556: Develop mechanism to configure keys and certificates for NETCONF/TLS in ODLClosed | 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 Feature has been delivered. Note: It is planned to start with SDNC in Dublin. To have same level of support in APPC, an additional ticket should be defined for (3), similar to SDNC-556. |
VNFRQTS | @Steven wright | VNFRQTS-519: Update requirements for NETCONF/TLSClosed | Update xNF requirements
| PTL notified Feature has been delivered. |
Part 2: Configuration use cases
The second part of the feature will secure support for a complete PNF configuration use case, based on NETCONF/TLS as the device protocol. The solution will utilize Controller Design Studio (CDS) components including the run-time blueprint processor.
Project | PTL | JIRA | Description | Status |
|---|---|---|---|---|
CCSDK | @Dan Timoney | CCSDK-926: Blueprint function component for Python ODL netconf-connectorClosed | Additional support for NETCONF/TLS configuration in the controller layer
| PTL notified Feature has been delivered. Note: As CDS components are under active development during Dublin, there are dependencies to several other Jira issues as well. |
SO | @Seshu Kumar Mudiganti | SO-1506: E2E Automation - Extend PNF workflow with post-instantiation configurationClosed SO-1604: SO Catalog Enhancement to support CDS Meta Data for VNF/PNF and PNF Tosca Ingestion Closed SO-1671: skip_post_instantiation_configuration schema and tosca ingestionClosed | Extend PNF support in the Service Orchestrator
| PTL notified Feature has been delivered. 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: