Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Test Case ID

Test Case Name

Conclusion, Tosca(Pass/Fail)

Progress & Block Issue(s)

T001

Infrastructure

100%


T002Tosca vCPE VNFs100%

T003

ONAP Installation

100%


T101

Windriver VIM Registration

100%

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-1920

ESR doesn't support domain name in vnfm registration GUI, currently we just use the IP address to register

T102Create Flavor100%
T103Upload Image to Windriver100%
T104Validate CPE Image in Windriver100%
T201vCPE VNFs Onboarding100%
T202vCPE Service Design100%
T203vCPE VNF and Service distribution100%

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-1900

'artifacts' definition is missing in the exported csar's VDU node ,because SDC postpone this to Dublin release, we only use the workaroud way to handle it


T301

VF-C Tosca parser

100%

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySDC-1897
(Will be fixed at Dublin)

VFC could ignore that error. To ignore that error, we need either apply the patch at https://jira.opnfv.org/browse/PARSER-187 locally in nfv-toscaparser which VFC uses or wait for nfv-toscaparser got that fixed.

The output vnf package from SDC is not ETSI alignment, we just use the standard package under Artifact/Deployment/OTHERS directory

VF-C would like SDC can support export ETSI standard VNF and NS package

T302

vCPE Service Creation

100%

One simple Service with simple vCPE vnf has been created successfully

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-405

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-404

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-1188

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyMULTICLOUD-407

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVFC-1193

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1235

when updating the SO images in vCPE env.  And the error is the same

Because SO can't work now , we use UUI to trigger the NS lifecycle management

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-1239

vCPE service with five vCPE vnfs have been created successfully

T303

vCPE Service Termination

100%

One simple Service with simple vCPE vnf has been terminated successfully

vCPE Service with five vCPE vnfs have been terminated successfully

T304vCPE VNF heal100%VNF Heal success
T305HPA Verification100%SRIOV-NIC and base capabilities had been registered
T306HPA policy100%optional
T307OOF compare100%

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyOPTFRA-401

optional

  1. package onboarding 
    VNF Packages:
    NS Packages:
  2. Video