Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 49 Next »


Use CaseLabResponsibleStatusVideo URLUse Case Details Testing StatusQuick Notes
1vFW / vDNS

Intel / Windriver

100%



vFW closed loop worked with instantiation from GUI (SDC/VID). Based on new closed loop for scale out (see test number 8), the old vLB/vDNS use case is onboard and instantiate regression only, which worked successfully.

2

vCPE Integration Test Case

Intel / Windriver

60%


VNF onboarding and service creation passed

Service distribution passed

Infra instantiation passed



BRG tap-0 and tap-1 ports stay up for a minute before going down. Asking Intel team to look at the VNFs. Resolved after a meeting with Eric and documented the solution on use case wiki.

AAI-2076 - Getting issue details... STATUS

SDC-2053 - Getting issue details... STATUS

DCAEGEN2-1106 - Getting issue details... STATUS

AAI-2090 - Getting issue details... STATUS

SDNC-593 - Getting issue details... STATUS

APPC-1367

DMAAP-1010

LOG-950

OPTFRA-423

3

vCPE with TOSCA VNF Test Case

CMCC

Completed


ONAP installation and hearth check: 100%

VNF onboarding and service design passed

service distribution passed

service instantiation passed


4

5G - Real Time PM and High Volume Stream Data Collection - Integration Test Status

TLab

Work in progress



TLAB unavailable so using SB-05 instead.

24.01.2019 r:

Unable to test due to issues with pods for example dmaap-message-router and 56 another ones
root@oom-rancher:~# kubectl get pods -n onap | grep message
dev-dmaap-message-router-647bbfc54d-9tqq9 0/1 Init:0/1 10 1d

Comment from Yang: Marcin Przybysz Can you try again on SB-00? Now all dmaap pods are up on SB-00.

5

5G - PNF PnP - Integration Test Status

TLabCompleted

TLAB unavailable so using SB-05 instead.

24.01.2019 r:

Unable to test due to issues with pods for example dmaap-message-router and 56 another ones

root@oom-rancher:~# kubectl get pods -n onap | grep message
dev-dmaap-message-router-647bbfc54d-9tqq9 0/1 Init:0/1 10 1d

26.01.2019r.

We observed an issue in PRH and reported a bug

INT-828 - Getting issue details... STATUS


6

5G - Bulk PM - Test Status

Intel / Windriver

Completed



TLAB unavailable so using SB-05 instead.

7

5G - OOF and PCI - Integration Test Cases

Intel / Windriver

Completed






Only OOF module was part of intergration testing (using Windriver Lab). Rest of use case was implemented as PoC only in Rutgers Winlab ONAP Wireless Lab (OWL)
8

Scale Out - Integration Test Cases and Status

Intel / Windriver

100% Completed



Tested manual scale out with SDNC and automated scale out with APPC and guard policies. No issues reported.

SO-1400 - Getting issue details... STATUS

9CCVPN Integration Test CasesCMCC

70%


Two set of ONAP installation and hearth check: 100%

Resource onboarding and Service Design: 100%

service distribution: 80%(SOTNVPNInfraService and SDWANVPNInfraService distribution passed, but site service distribution error)

Topology discovery: 50%

SOTNVPNInfraService create: 100%

SDWANVPNInfraService:100%

SDWAN service create: 20%

Site service Model parse error. SDC-1955 - Getting issue details... STATUS ,block site service creation

SO-1407 - Getting issue details... STATUS

SO-1417 - Getting issue details... STATUS

10

vFW/vDNS HPA Testing

(Test Plan 1 in

HPA & Cloud Agnostic Intent - R3 Test Plan)
Intel / Windriver


100% Completed


SO-1416 - Getting issue details... STATUS - using so 1.3.6 image, workaround is to manually increase the size of the column, the issue is supposed to be fixed in 1.3.7

MULTICLOUD-456 - Getting issue details... STATUS - Stack is successfully created in windriver but a timeout issue causes it to return as a failure during the vf module create process in ONAP and so the created stack is automatically deleted. Current workaround is to set suppress rollback to true when creating the vfmodule and so the created stack is not deleted although onap registers it as a failure

11Change Management - Flexible Designer & Orchestrator Intel / Windriver

Completed




Tested designer/orchestrator end-to-end on 1.3.5 Release with SO catalog-db-adapter being on 1.3.6.  Successfully tested the end-to-end functionality – activities distribution from SO to SDC, workflow creation and distribution to SO, and workflow execution in SO.

For SO activities only the A&AI-interfacing activities were functionally tested during workflow execution, since no suitable VNFs were available for testing APP-C-related ones, but used APP-C-related activities to create valid workflows.

12Change Management - Traffic Management-Intel / Windriver

Work in progress



Need to onboard dedicated version of vFW for Distribute Traffic 80%

APPC-CDT 0%

Ansible server must be configured also 0%

So far tests are blocked and vFW instance cannot be created.

SDNC-593 - Getting issue details... STATUS

AAI-2090 - Getting issue details... STATUS

13

Change Management - 5G PNF in-place software upgrade

Intel / Windriver

Work in progress





14Change Management - Schedule optimizationIntel / Windriver

Completed



Functional testing completed by Jerry.
  • No labels