Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

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

Planning for the Dublin release is ongoing.

Originally presented Nov 8, 2018 to the 5G UC meeting.

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

ProjectPTLJIRADescriptionStatus

APPC

SDNC

CCSDK

Takamune Cho

Dan Timoney

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

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

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

Steven wright

VNFRQTS-519 - Getting issue details... STATUS

VNFRQTS-520 - Getting issue details... STATUS

Update xNF requirements

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

PTL notified

Tickets have been created. Next step is to identify specific xNF requirements that are impacted.

Part 2: Configuration use cases

The second part of the feature will secure support for complete configuration use cases, based on NETCONF/TLS as the device protocol.

ProjectPTLJIRADescriptionStatus

APPC

SDNC

CCSDK


Takamune Cho

Dan Timoney

To be defined



Additional support for NETCONF configuration in the controller layer

  1. 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
  2. Controller north-bound APIs and implementation
    • PNF or VNF as target for request
    • Template lookup and download to target via ODL netconf-connector
  3. Self-service support for the configuration use cases
    • User interface
    • Blueprint distribution

PTLs notified

Ongoing discussions

SO

VID

Seshu Kumar Mudiganti

ittay

To be defined

UC1: Post-instantiation configuration

  1. Provide workflows and building blocks for instantiation with configuration step
    • For PNFs based on PnP workflow
  2. Trigger main workflow from GUI

PTLs notified

Coordinating with other activities in the same area

Policy
Pamela Dragosh
To be defined

UC2: (Stretch goal) Configuration change triggered by Policy

  • Possible impact: updated APIs, PNF as target
PTL notified
  • No labels