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 7 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
  • 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





  1. Configuration blueprint format
    • Possible to specify NETCONF/TLS as device protocol
    • Possible to attach YANG XML template as artifact
    • PNF as level/scope
  2. Controller north-bound APIs and implementation
    • GR API or LCM API
    • PNF support in API definition
    • Directed graphs including template lookup and processing
  3. Controller south-bound adapter
    • NETCONF/TLS support
    • YANG 1.1 support
    • ODL-based?
  4. Self-service support for the configuration use cases
    • User interface
    • Blueprint distribution

PTLs notified

Started discussions with CCSDK and CDS

SO

VID


  1. Support day 1 configuration including PNFs
    • Workflow design
    • Agree API with controller
    • Note: part of documented workflow in PNF PnP use case (step 36)

PTLs notified

Coordinating with other activities in the same area

PolicyPamela Dragosh
  1. Request configuration update
    • Possible impact: updated APIs, PNF as target
PTL notified
AAFJonathan Gathman
  1. Investigate certificate handling for NETCONF over TLS
    • Also discuss component responsibilities and procedures in SECCOM
PTL notified
VNFRQTS



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