INT-63
-
Getting issue details...
STATUS
| VPP-based VNF development |
|
|
|
|
|
|
| | - VPP-based VNFs: vGMUX, vG, vBNG, vBRG
- Cross test with APPC if needed
- Cross test with SDNC if needed
- Cross test with DCAE if needed
|
INT-58
-
Getting issue details...
STATUS
| VNF packaging & certification |
|
| HEAT templates, env files, images |
|
|
|
| | |
INT-93
-
Getting issue details...
STATUS
| VNF TOSCA template development |
|
|
|
|
|
|
| |
|
INT-84
-
Getting issue details...
STATUS
| VNF onboarding | SDC | VNF templates, env files, references to images. | VNF packages |
|
|
|
| | - Onboard all the VNFs in SDC and get them ready for service design.
- Every HEAT received by SDC should be previously certified by ICE. ICE is not integrated with SDC so far.
- Images are not stored in SDC. Either in openstack directly or pulled from the Internet.
|
INT-85
-
Getting issue details...
STATUS
| A&AI data model |
|
|
|
|
|
|
| Christina Monteleone |
|
CLAMP-20
-
Getting issue details...
STATUS
| Closed loop design | CLAMP, SDC, DCAE | Closed loop TOSCA template VES/TCA templates VES onboarding yaml file | policies and a blueprint template |
|
|
|
| | - Distribute blueprint template to SDC
- Distribute vGMUX restart policy to policy engine
|
INT-87
-
Getting issue details...
STATUS
| Generic workflow test |
| Workflow diagrams | BPMN and groovy files |
|
|
|
| | - Service level generic flows
- Resource level generic flows
|
INT-147
-
Getting issue details...
STATUS
| Custom workflow design and test | Camunda Modeler | Workflow diagrams | BPMN and groovy files |
|
|
|
| | - Service level flow: vCpeResCust
- Resource level flow: TunnelXConn
- Resource level flow: BRG
|
INT-88
-
Getting issue details...
STATUS
| SDNC artifacts | Text editor & DG Builder |
| Yang files and DG |
| yes |
|
|
| - Yang models
- DGs
- API data model
- Configure vBRG
- Configure vGMUX for data collection
|
INT-89
-
Getting issue details...
STATUS
| APPC artifacts | Text editor & DG Builder |
| Yang files and DG |
| yes |
|
|
| - Restart vGMUX for auto-healing
|
INT-90
-
Getting issue details...
STATUS
| Data analytics application | Java for DCAE |
| jar file |
|
|
|
| | - TCA to process packet loss events
|
INT-91
-
Getting issue details...
STATUS
| DCAE Collector |
|
| VES docker container |
|
|
|
| |
|
INT-92
-
Getting issue details...
STATUS
| Robot to instantiate vGMUX |
|
|
|
|
|
|
|
| - A Robot to invoke vGMUX instantiation
|
| Robot to emulate BSS |
|
|
|
|
|
|
|
| - A Robot to emulate BSS. It captures BRG registration event sent to DMaaP by AAI, and then invokes the custom service level workflow to instantiate customer service.
|
| Robot to emulate SNIRO |
|
|
|
|
|
|
| to be identified by Yoav Kluger | - A Robot to emulate SINRO to providing homing information.
- It is used by the service level custome workflow vCpeResCust to determine the home information.
|
| Robot to invoke packet loss event |
|
|
|
|
|
|
|
| - A Robot to interact with vGMUX. It notifies vGMUX to emulate packet loss.
|
INT-126
-
Getting issue details...
STATUS
| Infrastructure Service template creation | SDC | vGMUX, vBNG, vDHCP, vAAA, vDNS packages | Service template in TOSCA |
|
|
|
| |
|
INT-127
-
Getting issue details...
STATUS
| Customer Service template creation | SDC | vBRG, vG packages | Service template in TOSCA |
|
|
|
| |
|
INT-123
-
Getting issue details...
STATUS
| Test case creation |
|
|
|
|
|
|
| | |
| DMaaP Config | OOM |
|
|
|
|
|
|
| - Configure DMaaP topics and sub/pub of DCAE, Policy, and APPC for closed loop control
- Configure DMaaP topic and sub of SDNC for customer service order
|
| Test infrastructure service instantiation | VID |
|
|
|
|
|
|
| - Generic VNF instantiation: vDHCP, vAAA, vDNS
- Specific VNF instantiation: vBNG, vGMUX
|
| Test customer service ordering | TBD |
|
|
|
|
|
|
| - Specific VNF instantiation: vBRG, vG
- Verification: success of packet exchange between vBRG and web server
|
| Test auto healing |
|
|
|
|
|
|
|
| - vGMUX can be restarted
- Service restored after restart completes
|
| Monitoring dashboard | Use Case UI |
|
|
|
|
|
|
| - Number of customers
- Traffic load from each customer
- Packet loss events
|