Configuration with NETCONF in Frankfurt/R6

Owned by Benjamin Cheung
Last updated: Nov 13, 2019 by Oskar Malm
2 min read

Business Driver

Executive Summary -This feature aims to enhance NETCONF and YANG support in ONAP:

  • Support for additional IETF RFCs, including RFC7589 (NETCONF/TLS)

  • Support NETCONF-based configuration in certain ONAP use cases, including PNF initial configuration as part of PnP

Business Impact - It provides capabilities which ONAP service providers will find useful for network functions providing a NETCONF interface for configuration management.

Business Markets - These capabilities are generic and can be used for any network function supporting NETCONF.

Funding/Financial Impacts - the development of NETCONF communications from ONAP to xNFs will enable many other use cases which impact OPEX (thus indirectly this U/C saves OPEX).

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Frankfurt Scope

  1. Improvements to certificate handling for NETCONF/TLS. For AAF development, there is overlap with other use cases involving external communication to xNFs.

  2. For Frankfurt, there is also proposal to change the SO PNF workflow to use the new building block approach. This would impact the workflow configuration steps as well. See also PNF PLUG and PLAY in R6 Frankfurt.

Previous Release

R4 Dublin page: 5G - Configuration with NETCONF

Epics

  1. REQ-76: NETCONF/TLS Certificate ManagementDone

Project Impact

PROJECT

PTL

User Story / Epic

Requirement

A&AI

@James Forsyth





AAF

@Jonathan Gathman

Functionality will be developed in separate release requirement

REQ-140: Create Client, Plugin using Client and mechanisms for using CMPv2 as a CA.Done

  • Addition of CMPv2 client integrated with CertMan

  • Ensure AAF provides interface allowing SDNC to deploy extra client certificate for external NETCONF/TLS

APPC

@Takamune Cho





CLAMP

@Gervais-Martial Ngueko





CC-SDK

@Dan Timoney





DCAE

@Vijay Kumar





DMaaP

@Mandar Sawant





External API

@Matthieu Geerebaert





MODELING

@Hui Deng





Multi-VIM /

Cloud

@Bin Yang





OOF

@Shankaranarayanan Puzhavakath Narayanan





POLICY

@Pamela Dragosh





PORTAL

@Manoop Talasila





SDN-C

@Dan Timoney

EPIC#1

SDNC-966: NETCONF/TLS Certificate ManagementClosed



  • Improve support for deploying NETCONF/TLS client certificates into ODL netconf-keystore

    • Provided by external CA via AAF

    • Separate from certificate used for ONAP internal communication

SDC

@Ofir Sonsino





SO

@Seshu Kumar Mudiganti



  • Test only, no SO development in R6 for this feature.

    For integration e2e test case, the latest PNF workflow will be used. It is possible that this WF will be updated by other release requirements during R6 development.

VID

@ittay





VNFRQTS

@Steven wright





VNF-SDK

@victor gao





CDS

@Yuriy Malakov





Integration



EPIC#1

INT-1295: Update e2e integration test for NETCONF/TLS configuration in R6Closed

  • Develop extended test case based on Configuration with NETCONF from Dublin release

    • Include client certificate deployment using AAF and external CA (open source CA implementation to be used for testing)

List of PTLs:Approved Projects

Test Status