vCPE Integration Test Case


Category: VNF Onboarding and Service Creation


vCPE VNFs Onboarding

Test Case IDT201
Test Case NamevCPE VNFs Onboarding
DescriptionOnboard vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
Actual Results

All VNFs onboarded successfully with Robot script (TODO: add screenshot)


Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab, Integration-SB-03
Testing DateNov. 26, 2018
Tester NameYang and Brian


vCPE Service Creation

Test Case IDT202
Test Case NamevCPE Service Creation
DescriptionThis creates vCPE service
Actual Results

All service created and distributed successfully (TODO: screenshot)

Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab, Integration-SB-03
Testing DateNov. 26, 2018
Tester NameYang and Brian


Closed Loop Configuration

Test Case IDT203
Test Case NameClosed loop configuration
DescriptionCreate and distribute closed loop artifacts from CLAMP


Actual ResultsPolicy is preset. No need to design in this use case
Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab, Integration-SB-03
Testing DateNov. 26, 2018
Tester NameYang and Brian


Closed Loop Deployment

Test Case IDT204
Test Case NameClosed loop deployment
Description

Deploy and activate closed loop control for vCPE

Actual ResultsClosed loop is preset in DCAE with ONAP install, and policy is installed with a preinstalled script (see details in Use Case service design wiki)
Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab, Integration-SB-03
Testing DateNov. 26, 2018
Tester NameYang and Brian

Category: Service Instantiation and Monitoring


Infrastructure Service Instantiation

Test Case IDT301
Test Case NamevCPE Infrastructure Service Instantiation
DescriptionThis test covers the infrastructure service instantiation process, including DHCP, AAA, DNS, Webserver, vBNG, and vGMux.
Actual Results

All networks and VNF were successfully instantiated (TODO: screenshot)


Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab SB-03
Testing DateNov. 26, 2018
Tester NameYang and Brian

   

Customer Service Instantiation

Test Case IDT302
Test Case NamevCPE Customer Service Instantiation
DescriptionThis test covers the customer service instantiation process, including vBRG emulator and vG and the related configuration.
Actual Results

Customer service successfully instantiated and configured. Need to manually update temp_network_heat_template and network_resource tables to set aic_version_max = 3.0

Demo Video

Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab SB-03
Testing DateNov. 26, 2018
Tester NameYang and Brian


Category: Closed Loop


vCPE Auto-healing

Test Case IDT401
Test Case NamevCPE Auto-healing
DescriptionThis test covers the closed loop to restart vGMux when packet loss is detected.
Actual Results

Closed loop test succeeded. Was able to restart vGMUX VM at the expected event. Need to manually insert identity-url for CloudRegion in A&AI

TODO: Screenshot of vgmux reboot


Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab SB-03
Testing DateNov. 26, 2018
Tester Name

Yang and Brian


Category: Service Termination


vCPE Service Termination

Test Case IDT501
Test Case NamevCPE Service Termination
DescriptionThis test covers vCPE service termination process
Actual Results

Succeeded in removing all components of the customer service with Openstack operation and script

TODO: screenshot of stack and network after deletion

Conclusion (Pass/Fail)Pass
Testing LabWindRiver Lab SB-03
Testing DateNov. 26, 2018
Tester NameYang and Brian


Reference

ONAP Beijing: Understanding the vFWCL use-case mechanism

Tutorial_vIMS : SDNC Updates

vCPE SO to SDNC Message Flow

Configuring SNIRO Emulator for vCPE Testing


Issues fixed during integration test

Set up ONAP and health check  

NumberIssuesJIRAWorkaround
1SDNC fails health check intermittently

SDNC-482 - Getting issue details... STATUS

Reduce replica from 3 to 1 and not using clustering make the problem go away

2

SDC GUI doesn't come up

SDC-1839 - Getting issue details... STATUS

The workaround is find an old working image for sdc-frontend and replace the failing one
3

SO fails on health check due to bpmn

can't start

SO-1166 - Getting issue details... STATUS


Find a older working bpmn image from nexus3 repo and replace image version in Helm

deployment with kubectl edit command

4Portal GUI doesn't work on 8989 port

Use Firefox with portal 30225, and when switching to SDC click on the info icon at

the url bar and accept unsecure access to SDC GUI

5

All health check failed, due to the connection failure in k8s.

All cluster nodes are in Ready state:

root@oom-rancher:~/oom/kubernetes/robot# kubectl -n onap get node
NAME STATUS ROLES AGE VERSION
oom-etcd-1 Ready,SchedulingDisabled <none> 5d v1.11.2-rancher1
oom-etcd-2 NotReady,SchedulingDisabled <none> 5d v1.11.2-rancher1
oom-etcd-3 Ready,SchedulingDisabled <none> 5d v1.11.2-rancher1
oom-k8s-01 Ready <none> 5d v1.11.2-rancher1
oom-k8s-02 Ready <none> 5d v1.11.2-rancher1
oom-k8s-03 Ready <none> 5d v1.11.2-rancher1
oom-k8s-04 Ready <none> 5d v1.11.2-rancher1
oom-k8s-05 Ready <none> 5d v1.11.2-rancher1
oom-k8s-06 Ready <none> 5d v1.11.2-rancher1
oom-k8s-07 Ready <none> 5d v1.11.2-rancher1
oom-k8s-08 Ready <none> 5d v1.11.2-rancher1
oom-k8s-09 Ready <none> 5d v1.11.2-rancher1
oom-k8s-10 Ready <none> 5d v1.11.2-rancher1
oom-k8s-11 Ready <none> 5d v1.11.2-rancher1
oom-k8s-12 Ready <none> 5d v1.11.2-rancher1
oom-orch-1 NotReady,SchedulingDisabled <none> 5d v1.11.2-rancher1
oom-orch-2 Ready,SchedulingDisabled <none> 5d v1.11.2-rancher1



Restart oom-orch node can make k8s correction problem go away. You may have to restart a few pod manually like aaf-locate and aaf-service. But ONAP data seems preserved.


VNF onboarding, service creation and distribution

NumberIssue DescriptionJIRAWorkaround
1

AAI model loader fails model distribution. It appears AAI widgets are not loaded after initialization. The model loader error log shows 404 Not Found error like:

2018-11-01T22:39:25.117Z|5d569c28-6e2b-410f-98f2-17d11e978f5d|pool-2-thread-10|ModelLoader|Event-Bus|AAIRESTClient||INFO|AC0004I|AC0004I request at url = https://aai.onap:8443/aai/v14/service-design-and-creation/models/model/bb540550-d449-4745-b769-18f66508c56e resulted in http response: 404 Not Found|


AAI-1759 - Getting issue details... STATUS

run the script manually

root@oom-rancher:~# kubectl exec -it dev-aai-aai-traversal-b95847c96-fklkx -n onap gosu aaiadmin /opt/app/aai-traversal/bin/install/updateQueryData.sh

2Model distribution fails in SDNC because ueb-listener did not connect to SDC successful when starting

SDNC-472 - Getting issue details... STATUS

Bounce ueb-listener can resolve the issue
3Model distribution fails on SO due to missing table entry for Generic NeutronNet

SO-1184 - Getting issue details... STATUS

sql to insert data
INSERT INTO catalogdb.heat_template(`ARTIFACT_UUID`, `NAME`, `VERSION`, `BODY`, `TIMEOUT_MINUTES`, `DESCRIPTION`, `CREATION_TIMESTAMP`, `ARTIFACT_CHECKSUM`) VALUES('efee1d84-b8ec-11e7-abc4-cec278b6b50a', 'Generic NeutronNet', '1', 

'heat_template_version: 2013-05-23

description: A simple Neutron network

parameters:

  network_name:

    type: string

    description: Name of the Neutron Network

    default: ONAP-NW1

  shared:

     type: boolean

     description: Shared amongst tenants

     default: True

outputs:

  network_id:

    description: Openstack network identifier

    value: { get_resource: network }

resources:

  network:

    type: OS::Neutron::Net

    properties:

      name: { get_param: network_name }

      shared: { get_param: shared }

', 10, 'Generic Neutron Template', NOW(), 'MANUAL RECORD');

INSERT INTO catalogdb.heat_template_params(`HEAT_TEMPLATE_ARTIFACT_UUID`, `PARAM_NAME`, `IS_REQUIRED`, `PARAM_TYPE`, `PARAM_ALIAS`) VALUES('efee1d84-b8ec-11e7-abc4-cec278b6b50a', 'shared', 0, 'string', NULL);


INSERT INTO catalogdb.temp_network_heat_template_lookup (`NETWORK_RESOURCE_MODEL_NAME`, `HEAT_TEMPLATE_ARTIFACT_UUID`,`AIC_VERSION_MIN` , `AIC_VERSION_MAX` ) VALUES ('Generic NeutronNet','efee1d84-b8ec-11e7-abc4-cec278b6b50a','2.0','2.5');


If table is populated with wrong content (e.g. Generic NetronNet yaml), you can run SQL command to update it

root@mariadb:/# cat neutron.sh 
mysql -uroot -ppassword -e 'update catalogdb.heat_template set body="
heat_template_version: 2013-05-23
description: A simple Neutron network
parameters:
 network_name:
 type: string
 description: Name of the Neutron Network
 default: ONAP-NW1
 shared:
 type: boolean
 description: Shared amongst tenants
 default: False
outputs:
 network_id:
 description: Openstack network identifier
 value: { get_resource: network }
resources:
 network:
 type: OS::Neutron::Net
 properties:
 name: { get_param: network_name }
 shared: { get_param: shared }" where name="Generic NeutronNet"'
4




Service Instantiation

NumberIssueJIRAWorkaround
1Failed to create vCPE customer service with error message in bpmn log as
Cannot orchestrate Service-Macro-Create without user params with a vnf

SO-1189 - Getting issue details... STATUS


2DHCP_MAP is not populated in SDNC because kea DHCP is not downloaded correctly

INT-712 - Getting issue details... STATUS

You can manually download kea lib. See vCPE tutorial
3CloudOwner is not defined in SDNC configuration. vCPE customer service instantiation will fail

SDNC-448 - Getting issue details... STATUS

Add cloud-region.cloud-owner=CloudOwner container sdnc-sdnc-0: /opt/sdnc/data/properties/generic-resource-api-dg.properties

4

Customer service instantiation uses self-service flow and failed to find cloud owner

SDNC-511 - Getting issue details... STATUS

Add preload to GRA for the vBRG based on SO name to be assigned zRegionOne1base_vgw_0 , zRegionOne2base_vgw_0, etc.
5SUBCATEGORY and ALLOTTED_RESOURCE_ROLE not set in allotted_resource_customization/allotted_resource tables correctly


SDC-1909 - Getting issue details... STATUS

SO-1200 - Getting issue details... STATUS

SO-1208 - Getting issue details... STATUS

Manually update the allotted_resource table and allotted_resource_customization tables to set TunellXCon and BRG
6mso.workflow.sdnc.replication.delay not set in override.yaml for BPMN

SO-1198 - Getting issue details... STATUS

Manually set it to PT60S
7SO query to AAI after SDNC service-topology-operation fails -

arUrl is null

SO-1201 - Getting issue details... STATUS

Need patch




3 Comments

  1. MariaDB [catalogdb]> select * from allotted_resource;
    +--------------------------------------+--------------------------------------+---------------+-------------------------+-------------------------------------------------+----------------+-----------------+---------------------+
    | MODEL_UUID | MODEL_INVARIANT_UUID | MODEL_VERSION | MODEL_NAME | TOSCA_NODE_TYPE | SUBCATEGORY | DESCRIPTION | CREATION_TIMESTAMP |
    +--------------------------------------+--------------------------------------+---------------+-------------------------+-------------------------------------------------+----------------+-----------------+---------------------+
    | 6b0a5aa5-98d8-455c-8cd1-618a3f1ac859 | 531f9aa5-dea4-4958-89ad-ef03f77cbf07 | 1.0 | vcpear_brg_1111 | org.openecomp.resource.vf.VcpearBrg1111 | TunnelXConnect | vcpear for brg | 2018-11-12 00:00:59 |
    | d99e5442-c5e4-4197-ad8d-54f7ad43dd83 | 61c17371-e824-4587-a9bb-21782aa28391 | 1.0 | vcpear_tunnelxconn_1111 | org.openecomp.resource.vf.VcpearTunnelxconn1111 | TunnelXConnect | tunnel xconnect | 2018-11-12 00:00:59 |
    +--------------------------------------+--------------------------------------+---------------+-------------------------+-------------------------------------------------+----------------+-----------------+---------------------+



    BRG SUBCATEGORY needs to be BRG not TunnelXConnect


    update allotted_resource set SUBCATEGORY='BRG' where MODEL_INVARIANT_UUID='531f9aa5-dea4-4958-89ad-ef03f77cbf07';

  2. MariaDB [catalogdb]> select * from allotted_resource;
    +--------------------------------------+--------------------------------------+---------------+-------------------------+-------------------------------------------------+-------------+-----------------+---------------------+
    | MODEL_UUID | MODEL_INVARIANT_UUID | MODEL_VERSION | MODEL_NAME | TOSCA_NODE_TYPE | SUBCATEGORY | DESCRIPTION | CREATION_TIMESTAMP |
    +--------------------------------------+--------------------------------------+---------------+-------------------------+-------------------------------------------------+-------------+-----------------+---------------------+
    | 6b0a5aa5-98d8-455c-8cd1-618a3f1ac859 | 531f9aa5-dea4-4958-89ad-ef03f77cbf07 | 1.0 | vcpear_brg_1111 | org.openecomp.resource.vf.VcpearBrg1111 | BRG | vcpear for brg | 2018-11-12 00:00:59 |
    | d99e5442-c5e4-4197-ad8d-54f7ad43dd83 | 61c17371-e824-4587-a9bb-21782aa28391 | 1.0 | vcpear_tunnelxconn_1111 | org.openecomp.resource.vf.VcpearTunnelxconn1111 | TunnelXConn | tunnel xconnect | 2018-11-12 00:00:59 |
    +--------------------------------------+--------------------------------------+---------------+-------------------------+-------------------------------------------------+-------------+-----------------+---------------------+

  3. Until a new vgmux image is built, the attached 'libevel.so' file can be placed on the instantiated vgmux to resolve the issue reported in:   TEST-132 - Getting issue details... STATUS

    Associated gerrit is:  https://gerrit.onap.org/r/#/c/72726/

    Instructions:

    1. get the attached 'libevel.so' file and move to your jumphost
    2. scp onto the running vgmux vm:  say in /opt
      1. scp libevel.so root@<vgmux ip>:/opt
    3. ssh root@<vgmux ip>
    4. cd /opt
    5. cp ./libevel.so /usr/lib
    6. Check that it looks ok:
      1. ls -l /usr/lib/libevel.so
      2. -rwxr-xr-x 1 root root 533752 Nov 15 01:38 /usr/lib/libevel.so

      3. <fix owner and group if not root, verify size matches above>
    7. ldconfig

    8. libevel.so