Versions Compared

Key

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

Table of Contents

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:

Image RemovedImage Added

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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAPPC-1277

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAPPC-1258

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-551

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-555

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDNC-556

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 own client certificate and private key as well as trusted CAs 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

Tickets have Feature has been createddelivered.

Note: It is planned to start with SDNC . In order to use NETCONF/TLS with APPC as wellin Dublin. To have same level of support in APPC, an additional ticket should be defined for (3), similar to SDNC-556.

VNFRQTS

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVNFRQTS-519

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVNFRQTS-520

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVNFRQTS-603

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 Feature has been created. Next step is to identify specific xNF requirements that are impacted.delivered.

Part 2: Configuration use cases

The second part of the feature will secure support for a complete PNF configuration use

cases

case, based on NETCONF/TLS as the device protocol. The solution

with

will utilize Controller Design Studio (CDS) components including the run-time blueprint processor.

Image Added


Ticket created.
ProjectPTLJIRADescriptionStatus

CCSDK


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCCSDK-926



Additional support for NETCONF/TLS 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
  3. PNF or VNF as target for request
  4. Template lookup and download to target via Develop new capability in the CDS blueprint processor allowing use of the ODL netconf-connector Self-service support for the configuration use cases
  5. User interface
  6. from controller blueprints
  7. Create and verify sample CBA fileBlueprint distribution

PTL notified

Ticket Feature has been createddelivered.

Note: As CDS components are under active development during Dublin, there are dependencies to several other Jira issues as well.

SO


Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1506

UC1: Post-instantiation configuration

  1. Orchestration of service with PNF
    • Develop extended PNF workflow that includes configAssign and configure steps following PNF registration

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1604

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1671

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

PTL notified

Ticket has been created.

INT

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyINT-885

Support NETCONF/TLS in the PNF simulator

PTL notified

Feature has been

delivered.

Testing

See the the Integration test page for details: