Use Case Overview & Description
The goal here is to enhance the CCVPN use-case to support Intent-based networking. Intent separates “what”(description of the desired outcome) from “how”(actual network configurations), and can be used to enable the full network automation. This requirement wants to make CCVPN offer an Intent NBI that can be used to enable the closed-loop automation of the transport network. Also, Cloud Leased Line (CLL) is another use-case which comes as an enhancement to CCVPN. In CLL, one VPN service connects an enterprise network to multiple clouds; i.e. multiple VPNs can co-exist (service-isolation, performance monitoring).
Use Case Key Information
TOPIC | DESCRIPTION | WIKI PAGE |
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | Istanbul release, functional requirements proposed list - CCVPN use-case |
Architecture S/C info | Information on the Architecture sub-committee presentation | |
Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |
Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case | https://jira.onap.org/browse/REQ-719 |
Key Use Case Leads & Contacts | USE CASE LEAD: @xyz USE KEY CONTACTS: | |
Meetings Register & Recordings | Link to Use Case Team meetings. |
BUSINESS DRIVER
Executive Summary - We would like to enhance the CCVPN use-case to support Intent-based networking. Intent separates “what”(description of the desired outcome) from “how”(actual network configurations), and can be used to enable the full network automation. We will make CCVPN offer an Intent NBI that can be used to enable the closed-loop automation of the transport network.
Business Impact - Driven by use-cases such as IoT and 5G, the complexity of today’s transport network grows abruptly. Intent-Based Networking (IBN) is an emerging technology that aims to effectively manage network complexity and also aims for closed-loop automation.
Business Markets - Intent Based Networking (IBN) is an essential feature of future networking. Any operators who would like to deploy ONAP-based network automation solution would most likely require ONAP to support IBN.
Funding/Financial Impacts - Intent CCVPN provides service automation, assurance, and the optimal use of network resources. Thus, it helps reduce OPEX for a service provider.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Development Status
Epic Ticket
- REQ-719Getting issue details... STATUS
Project REQ Tickets
Story Tickets
USE CASE DIAGRAM
Cloud Leased Line (CLL) Use-Case
IETF/ACTN Models and Interfaces
IETF ACTN YANG Schema:
- ietf-eth-te-topology@2019-11-18.yang
- ietf-eth-te-tunnel@2018-03-01.yang
- ietf-eth-tran-service@2021-01-11.yang
- ietf-eth-tran-types@2019-11-03.yang
- ietf-inet-types@2021-02-22.yang
- ietf-layer1-types@2021-02-19.yang
- ietf-network@2018-02-26.yang
- ietf-network-state@2018-02-26.yang
- ietf-network-topology@2018-02-26.yang
- ietf-network-topology-state@2018-02-26.yang
- ietf-optical-slice@2020-08-21.yang
- ietf-otn-topology@2021-02-22.yang
- ietf-otn-tunnel@2021-06-25.yang
- ietf-routing-types@2017-12-04.yang
- ietf-service-pm@2020-07-13.yang
- ietf-te@2021-02-20.yang
- ietf-te-packet-types@2020-06-10.yang
- ietf-te-topology@2020-08-06.yang
- ietf-te-topology-state@2020-08-06.yang
- ietf-te-types@2020-06-10.yang
- ietf-trans-client-service@2021-01-11.yang
- ietf-trans-client-svc-types@2019-11-03.yang
R9 Istanbul Release Yang Schema Collections:
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
Cloud Leased Line call flow
Transport MD Closed-loop call flow
Test Cases and Status
1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
2 | create additional requirements as needed for each discreet step | COMPLETE |
3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |