You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 38
Next »
Test Case ID | Test Case Name | Conclusion (Pass/Fail) | Progress and Block Issue(s) |
| Lab infrastructure preparation: including hardware, VIMs, EMS, s-VNFM, PNFs / VNFs installation | 100% | No external SDN controller Huawei VNFM upgrade is complete Huawei EMS upgrade is complete |
| Install ONAP and health check | 100% |
|
V00001 | WindRiver OpenStack VIM Registration | 100% |
|
V00005 | Vendors' SVNFMs Registration | 100% |
|
V00006 | Vendors' EMSs Registration | 100% |
|
V00007 | VoLTE VNFs Onboarding | 100% |
|
V00009 | vIMS Service Creation | 100% |
|
V00013 | VoLTE Service Instantiation | 90% |
SO-615
-
Getting issue details...
STATUS
USECASEUI-113
-
Getting issue details...
STATUS
SO-619
-
Getting issue details...
STATUS
SO-624
-
Getting issue details...
STATUS
SO-630
-
Getting issue details...
STATUS
|
V00014 | System Performance and Alarm Monitoring | 100% |
|
V00015 | VoLTE Auto-healing | 70% | Issues: 1) Unable to register a https aai service from MSB GUI. Command line works. 2) VoLTE Policy fails to send restartvm request to VFC on ONSET event. Policy team is debugging the issue. 3) Huawei SVNFM driver needs to convert vmid to internal id to start VM. Huawei team is working on the issue |
V00016 | VoLTE Service Termination | 60% |
|
V00017 | VoLTE Manual scaling | 50% | Tested VNF scaling from SVNFM |
Service Instantiation Flow
http://13.82.90.118/EtherPlant/src/?http://13.82.90.118:9001/p/vIMS
@startuml
Title Service Instantiation\n
Actor "User" as User
Participant "UUI" as UUI
Participant "SO" as SO
Participant "VFC" as VFC
Participant "AAI" as AAI
Participant "MultiVIM" as MultiVIM
Participant "SVNFM" as SVNFM
autonumber 2.1 1 "."
User -> UUI : Start service instantiation\n by choosing a service model
UUI -> SO : Send service instantiation request
SO -> AAI : Insert a service instance record
SO -> SO : Get service and resource\ninfo from SO catalog
SO -> VFC : Deploy vIMS
VFC -> MultiVIM : Create VLs between VNFs
VFC -> AAI : Create VL records
VFC -> SVNFM : Deploy VNFs
SVNFM -> VFC : Notify VNF resource created
VFC -> AAI : Update VNF records
VFC -> SO : Return job status
SO -> UUI : Return job status
@enduml
Test Step ID | Progress | Notes |
---|
2.1 | Pass |
|
2.2 | Pass | resolved by
USECASEUI-116
-
Getting issue details...
STATUS
|
2.3 | Pass | resolved by
SO-619
-
Getting issue details...
STATUS
|
2.4 | Pass | blocked by
SO-624
-
Getting issue details...
STATUS
|
2.5 | Pass |
|
2.6 | Pass |
|
2.7 | Pass |
|
2.8 | Partially passed | Huawei SBC passed; Nokia CSCF failed due to some parameter missing from VNFD. Will design a new service with SBC only to test out ONAP features, in the meantime, Nokia will fix VNFD |
2.9 | Partially passed | Huawei SVNFM passed; Nokia's has not |
2.10 | Pass |
|
2.11 | Pass |
|
2.12 | Pass |
|
Auto Healing Flow
http://13.82.90.118/EtherPlant/src/?http://13.82.90.118:9001/p/autoHealing
@startuml
Title Auto Healing\n
Participant "DCAE" as DCAE
Participant "Holmes" as Holmes
Participant "VFC" as VFC
Participant "Policy" as Policy
Participant "AAI" as AAI
Participant "MultiVIM" as MultiVIM
Participant "3rd VNFM" as SVNFM
Participant "3rd EMS" as EMS
autonumber 3.1 1 "."
MultiVIM -> DCAE : Report VM event
DCAE -> Holmes : Forward VM event to Holmes
EMS -> VFC : Report VNF event
VFC -> DCAE : Forward VNF event to DCAE
DCAE -> Holmes : Forward VNF event to Holmes
Holmes -> AAI : Query vserver info
Holmes -> Holmes : Event correlation
Holmes -> Policy : Send DCAE_CL_OUTPUT event
Policy -> AAI : Query service instance info
Policy -> VFC : Send closed loop healing action
VFC -> SVNFM : Send healing action
VFC -> SVNFM : Job status
@enduml
Test Step ID | Progress | Notes |
---|
3.1 | Pass |
|
3.2 | Pass |
|
3.3 | Pass |
|
3.4 | Pass |
|
3.5 | Pass |
|
3.6 | Pass |
|
3.7 | Pass |
|
3.8 | Pass |
|
3.9 | Failed | Issue: Policy doesn't fill in instance-id etc info |
3.10 | Failed | Issue: Policy doesn't send healing request to VFC |
3.11 |
|
|
3.12 |
|
|
Manual Scaling with VFC Flow
http://13.82.90.118/EtherPlant/src/?http://13.82.90.118:9001/p/ScaleOutWithVFC
@startuml
Title Manual Scale In/Out with VFC\n
Actor "User" as User
Participant "UUI" as UUI
Participant "SO" as SO
Participant "Controller\n(VFC)" as Controller
Participant "AAI" as AAI
Participant "SVNFM" as SVNFM
Participant "vSBC" as vSBC
Autonumber
User -> UUI : Send scale in/out request
UUI -> SO : Send scale in/out request
SO -> Controller : Send NS scale in/out request
Controller -> Controller : Use local configuration\n file to find VNF scaling info
Controller -> SVNFM : Send VNF scaling request
SVNFM -> vSBC : Scaling
SVNFM -> Controller : Job status and notification
Controller -> SO : Job status
Controller -> AAI : Update VNFC and its relationship
SO -> UUI : Job status
@enduml
Test Step ID | Progress | Notes |
---|
1 | Pass |
|
2 | Failed | UUI server missing code to handle scaling request in vfcadapter |
3 |
|
|
4 |
|
|
5 |
|
|
6 | Pass | Manually tested VNF scaling from SVNFM |