...
All the sites and VPN Infras needs a set of inputs. 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 (To support multiple sets of inputs in one service template)
Note: 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.
(Anatoly Katzman Hui Deng Andy Mayer shitao li ) - SDC supports multiple node design in TOSCA service template (Ofir Sonsino )
- SO support List input interface(Seshu Kumar Mudiganti )
...