Originally presented Nov 8, 2018 to the 5G UC meeting.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 Removed
Development Status
Planning for the Dublin release is ongoing.
Image 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).
Project | PTL | JIRA | Description | Status |
---|
APPC SDNC CCSDK | | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | APPC-1277 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | APPC-1258 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-551 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-555 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-556 |
---|
|
| Enable NETCONF and TLS support in OpenDaylight when used by ONAP controller - Upgrade to ODL Flourine release (service release may be required)
- Ensure required ODL features are installed by default in controller
- Develop mechanism solution to obtain and configure keys and client certificate and private key as well as trusted 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 other 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 Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VNFRQTS-519 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VNFRQTS-520 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | VNFRQTS-603 |
---|
|
| Update xNF requirements - NETCONF and security requirements shall allow NETCONF over /TLS
- YANG requirements shall allow YANG 1.1
| PTL notified Tickets have been created. Next step is to identify specific xNF requirements that are impactedFeature has been delivered. |
Part 2: Configuration use cases
cases
Project | PTL | JIRA | Description | Status | APPC
SDNC
CCSDK
| To be defined |
---|
CCSDK
| | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CCSDK-926 |
---|
|
| Additional support for NETCONF/TLS configuration in the controller layer - 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
- Controller north-bound APIs and implementation
- PNF or VNF as target for request
- Template lookup and download to target via ODL netconf-connector
- Self-service support for the configuration use cases
- User interface
- Blueprint distribution
| PTLs notified Ongoing discussions |
SO VID | | To be defined | UC1: Post-instantiation configuration - Provide workflows and building blocks for instantiation with configuration step
- For PNFs based on PnP workflow
- Trigger main workflow from GUI
| PTLs notified Coordinating with other activities in the same area |
Policy | | To be defined | UC2: (Stretch goal) Configuration change triggered by Policy - Possible impact: updated APIs, PNF as target
| PTL notified- Develop new capability in the CDS blueprint processor allowing use of the ODL netconf-connector from controller blueprints
- Create and verify sample CBA file
| PTL notified Feature has been delivered. Note: As CDS components are under active development during Dublin, there are dependencies to several other Jira issues as well. |
SO
| | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-1506 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-1604 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-1671 |
---|
|
| Extend PNF support in the Service Orchestrator
- Update catalog DB schema for PNFs
- Add PNF model ingestion including blueprint information
- 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. |
INT | | Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INT-885 |
---|
|
| Support NETCONF/TLS in the PNF simulator | PTL notified Feature has been delivered. |
Testing
See the the Integration test page for details: