Versions Compared

Key

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


Category: External System Registration

WindRiver OpenStack VIM Registration

Test Case IDT101
Test Case NameWindRiver OpenStack VIM Registration
DescriptionWindRiver OpenStack VIM Registration
ReleaseDublin
Preconditions
  1. The WindRiver OpenStack VIM is configured with tenant information and provider networks
  2. The WindRiver OpenStack VIM services (console, auth, neutron, image, glance, etc) are accessible from ONAP by IP
  3. Create flavor onap.hpa.flavor1 and aggregate

     $ openstack aggregate create --property aggregate_instance_extra_specs:sriov_nic=sriov-nic-intel-1234-5678-physnet1:1 aggr11

     $ openstack flavor create onap.hpa.flavor1 --id auto --ram 512 --disk 40 --vcpus 4

     $ openstack flavor set onap.hpa.flavor1 --property aggregate_instance_extra_specs:sriov_nic=sriov-nic-intel-1234-5678-physnet1:1

Testing Steps

Use CLI command to add the above info.

# Create complex
$ oclip complex-create \
-j <street2> -r <physical_location> -x <complex_name> \
-y <data_center_code> -lt <latitude> -l <region> \
-i <street1> -lo <longitude> -S <state> \
-la <lata> -g <city> -w <postal-code> \
-z <complex_name> -k <country> -o <elevation> \
-q <identity_url> -m <aai_url> -u <aai_username> -p <aai_password>

# Create cloud
$ oclip cloud-create -e <esr-system-info-id> -b <user-name> -I <cloud-region>
\
-x <cloud-owner> -y <cloud-region> -j <password> \

-w <cloud-region-version> -l <default-tenant> -url <service-url> \
-n <complex_name> -q <cloud-type> -r <owner-defined-type> \
-Q <system-type> -i <identity-url> -g <cloud-zone> \
-z <ssl-insecure> -k <system-status> -c <cloud-domain> \
-m <aai_url> -u <aai_username> -p <aai_password>

# Associate Cloud with complex

oclip complex-associate -x <complex_name> -y <cloud-region> -z <cloud-owner> -m <aai_url> -u <aai_username> -p <aai_password>


# Register Cloud with Multicloud

$ oclip multicloud-register-cloud -x <cloud-region> -y <cloud-owner> -m http://<ip>:<port> 

Expected Results
  1. VIM is registered successfully
  2. Tenant authentication information is stored correctly
Actual Results

All information stored in AAI.

Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang


GVNFM Registration

Test Case IDT102
Test Case NameGVNFM Registration
DescriptionRegister GVNFM to AAI, VFC can use the GVNFM
ReleaseDublin
PreconditionsWe can access GVNFMDRIVER
Testing Steps
  1. Use CLI command to add the above info.
Expected Results
  1. VIM is registered successfully
  2. Tenant authentication information is stored correctly
Actual Results

All information stored in AAI.

Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang


Category: VNF Onboarding and Service Design


vCPE VNFs Onboarding

Test Case IDT201
Test Case NamevCPE VNFs Onboarding
DescriptionOnboard vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vGW
ReleaseDublin
Preconditions
  1. All HEAT and TOSCA templates are ready
  2. VNF license has been created
Testing Steps
  1. Use SDC to import, test and certify the following VNF templates, including both yaml and env files: vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
Expected Results
  1. All VNFs are onboarded successfully
Actual Results

All VNFs onboarded successfully

Image Added

Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang


vCPE Service Design

Test Case IDT202
Test Case NamevCPE Service Design
DescriptionOnboard vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
ReleaseDublin
Preconditions
  1. All HEAT and TOSCA templates are ready
  2. VNF license has been created
Testing Steps
  1. Use SDC to import, test and certify the following VNF templates, including both yaml and env files: vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
Expected Results
  1. All VNFs are onboarded successfully
Actual Results

All VNFs onboarded successfully

Image Added

Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang

vCPE VNFs and Service distribution

Test Case IDT203
Test Case NamevCPE VNFs and Service distribution
DescriptionOnboard vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
ReleaseDublin
Preconditions
  1. All HEAT and TOSCA templates are ready
  2. VNF license has been created
Testing Steps
  1. Use SDC to import, test and certify the following VNF templates, including both yaml and env files: vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
Expected Results
  1. All VNFs are onboarded successfully
Actual Results

All VNFs onboarded successfully


Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang

Category: Service Create, Instantiation and Termination

vCPE Service Creation

Test Case IDT301
Test Case NamevCPE Service Creation
DescriptionThis creates vCPE service
ReleaseDublin
Preconditions
  1. All VNFs have been onboarded
  2. All VNFs images files have been uploaded manually into VIM
Testing Steps
  1. Use SDC to create core infrastructure service including vDHCP, vAAA, vDNS, and Web server
  2. Use SDC to create a service including vBNG
  3. Use SDC to create a service including vGMux
  4. Use SDC to create a service including vBRG
  5. Use SDC to create vCpeResCust sevice service including vG, TunnelXConn allotted resource, and BRG allotted resource.
Expected Results
  1. Each service is created successfully and stored in the catalog
Actual Results
Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang


vCPE Service Instantiation

Test Case IDT302
Test Case NamevCPE Service Instantiation
DescriptionThis test covers the customer service instantiation process, including vBRG emulator and vG and the related configuration.
ReleaseDublin
Preconditions
  1. vCPE services have been created
  2. vCPE infrastructure service has been instantiated
Testing Steps
  1. ONAP user uses VID to instantiate a vBRG and a VM that is connected to the vBRG
  2. Once vBRG is instantiated, its subsequent DHCP request will invoke ONAP to instantiate a vG and complete all required configuration. This step does not require human intervention.
  3. ONAP user sign on to the VM connected to the vBRG and test connection to the web server.
Expected Results
  1. vBRG and vG are up and running
  2. ONAP user can access the web server
Actual Results

Customer service successfully instantiated and configured. Data plane communication verified. See video recording below.

Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang


vCPE Service Termination

Test Case IDT303
Test Case NamevCPE Service Termination
DescriptionThis test covers vCPE service termination process
ReleaseDublin
Preconditions
  1. vCPE service is created
  2. Closed loop is established
Testing Steps
  1. ONAP user uses Web GUI and/or scripts to remove vCPE service
Expected Results
  1. All vCPE VNFs and VLs are removed
Actual Results

Succeeded in removing all components of the service. Below is a video showing the process of deleting customer service.

Conclusion (Pass/Fail)Pass
Testing LabIntegration Lab - VFC tenant
Tester NameHaibin Huang