...
NOTE: More participants are welcome.
Description
CCVPN Use Case extension for Dublin, includes Service Creation and Modification using the concepts of Unified and Composite Services.
In Casablanca release, we propose CCVPN(Cross Domain and Cross Layer VPN) use case, in which scenario if a customer wants to set up a VPN from Beijing to London, we can use ONAP to stretch such a VPN service that is cross operator, cross domain and cross layer.
cross operator: the VPN service could be stretched between two ONAPs.
cross domain: a VPN service is cross diffrent OTN domains which is controlled by different 3rd parties
cross layer: the VPN service can be l1,l2,l3 or any composition of these layers, eg: a VPN service that is cross l2 and l3
The ultimate goal of this use case is, by taking advantage of the strong orchestration ability of ONAP, to automatically create and deploy a cross operator, cross domain (SOTN + SD-WAN), cross layer (L1, L2, L3) end to end VPN and update the service dynamically.
Main functions in this use case include automatically design of end to end service, creation of end to end service, cross-domain resource cooperation, global rerouting.
We testified this possibility in C release and realized functions like topology discovery, simple service creation, as well as back-up link switch in closed loop.
From Furthermore, from an Operator perspective, it is important to introduce the capability to manage the performance of the CCVPN End-to-End service (especially when it spans across different Operators). So, in Dublin release, we would like to extend the scenario of CCVPN use case to multiple sites and service modifications. The customer may want to add two sites in Shanghai and Wuhan onto the original service due to their business needs. Customers also have the need to do some modifications on the existing service, eg: to change the bandwidth or to build up a vFW in the VPN.
Current Situation
In Casablanca release, the CCVPN service is created by mean of separate multiple Service Orders via TMF 641, with one service orderItem for each of the services that make up the CCVPN connectivity Service. (Note -the UUI in Casablanca makes separate calls to SO, i.e. does decomposition but without Service Orders)
The complete removal of the CCVPN Service would involve the Portal/UUI making multiple separate Service Orders with one orderItem, each with a ‘delete’ action. This because there is no E2E Service Instance that corresponds to the full CCVPN Service.
Proposed enhancements for Dublin release
Service Model Optimization
In Casablanca release, the ability of SDC‘s service template doesn’t support multiple inputs of different instances, which leads to the situation that we need to design site and VPN Infra in separate service templates.
In R3, Modeling Subcommittee accepts the concepts of 'Atomic' and 'Composite', in which CCVPN is a strong evidence of composite service.
The needs of providing a real end to end service in ONAP arouse the demands for designing a composite service in one service template.
Our targeted solution to CCVPN model in Dublin release is:
CCVPN service is composed of two kinds of atomic service: SD-WAN service and SOTN service Atomic service consists of serveral composite resources, like site and VPN-Infra.
To support the composite service, there should be some improvements in implementation.
- In service template, It should support the list structure of inputs so that a service can have multiple inputs of resources.
2. SO should allow service updating work flow.
Extension (enhancements) in Dublin release:
Service Service Creation
In an ideal implementation, the Portal shall create a single Service Order via TMF 641, with multiple service orderItem orderItem(s) for each of the services that make up the CCVPN Service.
...
Finally, SDC must be able to model the LCM Operation/Interfaces for modifications allowed on the CCVPN Service (e.g., AdjustBandwidth) so that the modification capability can be exposed through the Service Catalog.
Service OAM
The Service OAMs (Fault & Performance Management) are used to guarantee the SLA objectives. Initial focus for CCVPN Dublin Release should be on modeling SOAM-PM for Composite Services in the Service Catalog.
Besides the change of service components like adding or deleting the sites, we also have the needs to add a VNF like vFW in the service or change the inputs parameters of an existing service.
Specific sub-use cases
...