Overview:
The E2E integration test consists of three main parts:
Gliffy Diagram | ||||||||
---|---|---|---|---|---|---|---|---|
|
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 | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
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.
- Repo : Yet to update
- Clone the integration/csit repo (git clone ssh://gerrit.onap.org:29418/integration/csit).
- RUN : Yet to update
Run:
Use Case preconditions:
- xNF simulator.
E2E Netconf config over TLS Sequence Diagram
High Level End-to-End feature integration
Test cases :
# | Test Case | Description | Reference | Tester |
---|---|---|---|---|
1 | Create and distribute service which contains PNF | Verify distribution and ingestion of PNF service csar to VID, AAI & SO. | 5G - PNF Onboarding Test Cases and Status |
: PNF-OB-5 | Andy Walshe | |||
2 | Waiting for PNFReady | Verification if PNF PnP functionality within SO is waiting for PNFReady to be published by PRH. | 5G - PNF PnP -WaitingforPNFReady | |
3 | PNF registration accepted | Verification if PNF resource registration is done properly | 5G : Configuration with NETCONF - E2E test case for Netconf over TLS | |
4 | Send Configuration with NETCONF over TLS | Verify the configuration is sent to the PNF with NETCONF | 5G : Configuration with NETCONF - Success Flow |
Detailed Description End-to-End Feature Integration Testcases :
Test Case ID |
---|
NETCONF_CONFIGURATION_ |
---|
TLS_E2E |
---|
Test Case Name |
E2E test case for NETCONF over TLS | |
Description | Ensure that |
PNF_READY notification is received by SO from PRH then SO sends CONFIG-ASSIGN, CONFIGURE request to SS-API, to configure the xNF | ||||
Release | Dublin | |||
Pre-conditions |
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 |
|
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
| ||
Conclusion (Pass /Fail) |
|
https://jenkins.onap.org/view/CSIT/ Ubuntu Docker Machine
Testing Steps
Information:
For more information on the DMaaP API's see this link DMaaP API
| |||||
Testing Lab | Ericsson Lab, Windriver Lab |
Information:
Next Step(s):