Description
In CCVPN use case, 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. Customer can also create a multi-site to multi-site service, as well as delete or add a site on the existing service according to their demands.
We abstract the VPN service topology into three kinds of nodes: Site, SOTN VPN Infra, SD-WAN VPN Infra. The composition of Sites and SOTN VPN Infras can comprise a SOTN VPN Service, the composition of Sites and SD-WAN Infras can comprise a SD-WAN VPN Service, while the combination of these three nodes can make up a SOTN+SD-WAN VPN Service.
All the sites and VPN Infras needs a set of inputs respectively. In Casablanca release, SDC is not capable to support multiple sets of inputs in one service template so that we have to design the sites and VPN infra as a service and use 3 service templates to describe each kinds of node. The CCVPN service is created by mean of separate multiple Service Orders , with one service orderItem for each of the services that makes up the CCVPN connectivity Service.
Such solution, on the one hand, obviously, violates the idea of using one service template to create a CCVPN service. A CCVPN service consists of several site service and VPN service which in fact should be resource; On the other hand, Customers couldn't choose which site or VPN Infra to be included when instantiating a real service because all these resources are regarded as a service.
But if the service template could support multiple instances inputs, we can design all the Site, SOTN and SD-WAN as resources into one service, which would be more reasonable.
Requirements
- Modeling team accepts multiple node template instances in service template (which means to provide the List type of inputs so that multiple sets of inputs can be supported in one service template
Note:
1）TOSCA service templates specify a set of nodes that need to be created at service deployment time. Some service templates may include multiple nodes that perform the same role. For example, a template that models an SD-WAN service might contain multiple VPN Site nodes, one for each location that accesses the SD-WAN. Rather than having to create a separate service template for each possible number of VPN sites, it would be preferable to have a single service template that allows the number of VPN sites to be specified at deployment time.
2) According to our discussion with Tosca team, the List type of inputs is also one of the needs of TOSCA 1.2.
(Anatoly Katzman Hui Deng Andy Mayer Former user (Deleted) ) - SDC supports design of List inputs in TOSCA service template (Ofir Sonsino )
1) On Design interface List type of resources can be provided
2) Tosca parser supports parsing of List type of inputs
3) Database supports store List type of inputs - SO support List input interface(Seshu Kumar Mudiganti )
The ideal solution should be that a CCVPN service can be instantiated by using one service template and customers can decide the number of resources when creating a service.
To satisfy this needs, an optimization on service template– List type of inputs should be supported
see Reference:
1, TOSCA Enhancements to Support Multiple Node Template Instances
2, SOTN VPN Infra Service CSAR File in C release