Versions Compared

Old Version 7

changes.mady.by.user Rahul Tyagi

Saved on

compared with

New Version Current

changes.mady.by.user Kamel Idir

Saved on

Key

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

Overview:

The E2E integration test consists of three main parts:


Gliffy Diagram
size600
nameSDC-service-distribution Copy
pagePin1

Image Added


Image Added


THIS PAGE IS UNDER DEV.

---TEST STATUS for Dublin Release ----

The Bulk PM feature consists of two main parts:

  • Event-driven bulk transfer of monitoring data from an xNF to ONAP/DCAE. A micro-service will listen for 'FileReady' VES events sent from an xNF via the VES collector. Once files become available the collector micro-service will fetch them using protocol such as FTPES (committed) or SFTP. The collected data files are published internally on a DMaaP Data Router (DR) feed. (committed goal for Casablanca release)
  • For 3GPP formatted measurement data and for consumers that prefer such data in VES format, an optional 3GPP PM Mapper micro-service is planned that can extract selected measurements from a 3GPP XML file and publish them as VES events on a DMaaP Message Router topic. The mapper receives the files by subscribing to a Data Router feed (committed goal for Dublin release)

JIRAs:

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

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

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

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

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

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

Deployment:

Test environment requirements for above the test cases:

  • xNF simulator for test cases:  PNF Simulator with TLS & YANG support.
  • with VES 7.0.1 support for 'fileReady' event.
    • E.g. xNF able to produce data files and send VES fileReady events,
    • E.g. xNF emulator able to produce 'fileReady' notification events including updated events, or a series or predefined VES events at periodic intervals.
  • SO with Config-Assign and Configure steps implemented in workflows.
  • CCSDK, CDS Blueprint processor enhanced so that it can send mount, configure and un-mount rest request to SDNC.
  • SDNC enhanced with ODL flourine SR2 and also capable to import client and trusted certificate and private key at deployment time.

This environment can be set up by following the steps below.

  1. Repo : Yet to update
  2. Clone the integration/csit repo (git clone ssh://gerrit.onap.org:29418/integration/csit).
  3. RUN : Yet to update
  4. Run:

Use Case preconditions:

    • xNF simulator.

E2E Netconf config over TLS Sequence Diagram

Image Removed

High Level End-to-End feature integration

Testcases

Test cases :


#Test CaseDescriptionReferenceTester
1Create and distribute service which contains PNFVerify distribution and ingestion of PNF service csar to VID, AAI & SO.5G - PNF Onboarding Test Cases and Status
1234567 StatuscolourGreytitleNot Started
: PNF-OB-5Andy Walshe
2Waiting for PNFReadyVerification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH.5G - PNF PnP -WaitingforPNFReady

Rahul Tyagi

Eric Moore

3

PNF registration accepted

Verification if PNF resource registration is done properly

5G : Configuration with NETCONF - E2E test case for Netconf over TLS

Rahul Tyagi

Eric Moore

4Send Configuration with NETCONF over TLSVerify the configuration is sent to the PNF with NETCONF5G : Configuration with NETCONF - Success Flow

Rahul Tyagi

Eric Moore



Detailed Description End-to-End Feature Integration Testcases :


Test Case ID

Bulk

NETCONF_CONFIGURATION_

PM

TLS_E2E

_01

Test Case Name
Send FileReadyEvent to VES Collector

E2E test case for NETCONF over TLS

DescriptionEnsure that
the 'FileReady' VES event is sent from the simulated xNF to the VES collector.ReleaseCasablancaPre-conditionsFrom the above section "Deployment" a test environment with all the required components - xNF (simulated with sftp or sftpe ), VES Collector are all started
PNF_READY notification is received by SO from PRH then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API, to configure the xNF
ReleaseDublin
Pre-conditions
  1. SO should be waiting for PNF_READY notification after registration process and fully configured as per registration process.
  2. Blueprint archive should be configured for correct blueprint.
  3. SDNC should be installed successfully with keystore preconfigured with certificates of PNF-SIM.
    Certificates for PNF simulator can be picked up from here. Copy these certs in /dockerdatanfs/sdnc/certs and install sdnc.
  4. PNF-SIM should be running with TLS support.

      Install pnf simulator from here using ./simulator.sh start. It will start simulator in TLS/SSH mode at 6503/830 port. Send VES message by changing config/config.json.

Testing Steps


StepsExpected Result
  1. Send
FileExist VES event to VES collector to simulate what the xNF would initiate.

Example File Ready VES Notification:

curl -i -X POST    -H "Content-Type:application/json"    -d '{
    "event": {
        "commonEventHeader": {
            "version": "4.0.1",
            "vesEventListenerVersion": "7.0.1",
            "domain": "notification",
            "eventName": "Noti_RnNode-Ericsson_FileReady",
            "eventId": "FileReady_1797490e-10ae-4d48-9ea7-3d7d790b25e1",
            "lastEpochMicrosec": 8745745764578,
            "priority": "Normal",
            "reportingEntityName": "otenb5309",
            "sequence": 0,
            "sourceName": "oteNB5309",
            "startEpochMicrosec": 8745745764578,
            "timeZoneOffset": "UTC+05.30"
        },
        "notificationFields": {
            "changeIdentifier": "PM_MEAS_FILES",
            "changeType": "FileReady",
            "notificationFieldsVersion": "2.0",
            "arrayOfNamedHashMap": [
              { "name": "pm.xml.gz",
                "hashMap":{
                              "location": "sftp://admin:admin@172.18.0.2:22/pm.xml.gz",
                              "compression": "gzip",
                              "fileFormatType": "org.3GPP.32.435#measCollec",
                              "fileFormatVersion": "V10"
                              }
              }
            ]  
        }
    }
  }' 'http://172.17.0.2:8080/eventListener/v7'

The VES Collector accepted the "File Ready" Notification send by xNF.

We should get 202 response from the VES Collector. e.g.

HTTP/1.1 202

Content-Type: application/json

Content-Length: 8

Date: Sat, 22 Sep 2018 21:16:07 GMT

  1. PNF_READY to SO(This step will trigger a run to SS-API, BP component, SDNC and PNF simulator)
  2. SO sends CONFIG-ASSIGN request to CDS.
  3. SO receives the response from CDS for CONFIG-ASSIGN as success.
  4. SO sends CONFIG-DEPLOY  async request to CDS.
  5. CDS sends patch(includes mount, configure and unmount request) to SDNC.
  6. SDNC sends mount request to PNF-SIM using TLS connection.
  7. CDS send connection status to SDNC for PNF-SIM.
  8. SDNC sends configuration request to PNF-SIM.
  9. SDNC sends unmount request to PNF-SIM.
  10. Verify received configuration is correct on PNF-SIM (Manual verification).
Get response should give correct result for configuration on PNF-SIM



Conclusion (Pass /Fail)
PASS

Status

Testing Lab

https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine

Test Case IDTest Case NameDescriptionReleasePre-conditions

Testing Steps

StepsExpected ResultConclusion (Pass /Fail)Testing Lab

Information:

For more information on the DMaaP API's see this link DMaaP API

colourGreen
titlePassed

Testing Lab

Ericsson Lab, Windriver Lab


Information:


Next Step(s):