Use Case Authors:
...
High Priority Extensions (enhancements) in Dublin release:
...
Multi-site to multi-site Service Creation (Priority: Layer 3 > Layer2 > Layer1)
...
In an ideal implementation, the Portal shall create a single Service Order via TMF 641, with multiple service orderItem(s) for each of the services that make up the CCVPN Service.
- SDC should support create an E2E service with one service template by supporting inputs of multiple resources at the same time (instead of using multiple service templates one by one when creating an E2E service) and SO should have the capability to decompose and (eventually) delegate the nested Services.
- A&AI should maintain composite End-to-End Service Instance for CCVPN.
- Parameters for all services can be passed as one composite orderItem to External API.
Service
...
Change : Add or Delete a site (Priority: Layer 3 > Layer2 > Layer1):
A CCVPN End-to-End Service Change (e.g., bandwidth change), should be either triggered by the portal (as TMF 641 single service orderItem with ACTION ‘change’) or by a policy implemented to guarantee that SLS is met.
...
Priorities for Dublin
(Initial assessment)
High Priority
| Feature | Impacted Project | Note |
|---|---|---|
| Layer 3 Multi-site to Multi-Site Service Creation | SDC, SO, SDN-C, AAI | |
| Service Change: Add or Delete a Site | SDC, SO, SDN-C, AAI | |
*feature already proposed for Dublin release
...