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


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).





APPC-1277 - Getting issue details... STATUS

APPC-1258 - Getting issue details... STATUS

SDNC-551 - Getting issue details... STATUS

SDNC-555 - Getting issue details... STATUS

SDNC-556 - Getting issue details... STATUS

Enable NETCONF and TLS support in OpenDaylight when used by ONAP controller

  1. Upgrade to ODL Flourine release (service release may be required)
  2. Ensure required ODL features are installed by default in controller
  3. Develop solution to obtain and configure client certificate and private key as well as trusted certificates for NETCONF/TLS in ODL as part of controller instantiation
    • Review solution in SECCOM

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-519 - Getting issue details... STATUS

VNFRQTS-520 - Getting issue details... STATUS

VNFRQTS-603 - Getting issue details... STATUS

Update xNF requirements

  1. NETCONF and security requirements shall allow NETCONF/TLS
  2. YANG requirements shall allow YANG 1.1

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.



CCSDK-926 - Getting issue details... STATUS

Additional support for NETCONF/TLS configuration in the controller layer

  1. Develop new capability in the CDS blueprint processor allowing use of the ODL netconf-connector from controller blueprints
  2. Create and verify sample CBA file

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-1506 - Getting issue details... STATUS

SO-1604 - Getting issue details... STATUS

SO-1671 - Getting issue details... STATUS

Extend PNF support in the Service Orchestrator
  1. Update catalog DB schema for PNFs
  2. Add PNF model ingestion including blueprint information
  3. Add config-assign and config-deploy steps to the PNF workflow

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-885 - Getting issue details... STATUS

Support NETCONF/TLS in the PNF simulator

PTL notified

Feature has been delivered.


See the the Integration test page for details:

  • No labels