Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Presented Nov 8, 2018 to the 5G UC meeting.

ProjectPTLJIRADescriptionStatus

APPC

SDNC

CCSDK


Enable NETCONF and TLS support in OpenDaylight

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

PTLs notified

Ongoing discussions

APPC

SDNC

CCSDK





Complete 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


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

UC2: (Stretch goal) Configuration change triggered by Policy

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVNFRQTS-519

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyVNFRQTS-520

Updated xNF requirements

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