The CCVPN E-LAN Service Use Case will impact each of the Projects listed on this page. Depending on the chosen implementation Option (listed here), impact will be different. Listed impacts refer to Option 2 for Service Creation and Option A for Service Modification
AAI
- Support Composite Services Service Instances (also multi-operator)
DCAE
Performance management - Stretched GOAL
OOF
(Not Pursing in R3)- OOF will process Homing and capacity placement request from MSO.
OOF will support additional Policies for Scale Out to check the following:
- If there is enough capacity in the region or close to the region
- For the VNF Instance, is the license sufficient to satisfy the configuration requested
- TBA
Modeling
- Need to add Controller type to the VNF Model in SDC
SDC
- Support Composite Services creation
- Must be able to model LCM operations/Interfaces and expose the modification capabilities through the Service Catalog
SDNC
- For L1-3 VNFs, process a HealthCheck action from SO via DMaaP
- Import Scaling changes from APPC so that all configuration changes may be done on VNFs controlled by SDNC
- Retrieve the IP addresses from A&AI for the ConfigScaleOut action
- Obtain Configuration information for new instance from A&AI
SO
External API
- Implement
SO
- Implement ability to "decompose" the End-to-End service (in collaboration with SDC). The same applies for the Service Change
- Implement Service Modification API and associated workflows to interact with other projects (SDN-C, A&AI & ExtAPI)