Service Instantiation and Activation (Frankfurt)
- David Perez Caparros
ID | Test Case Name | Status |
|---|---|---|
C1 | NOT TESTED | |
C2 | PENDING | |
C3 | PENDING | |
C4 | HSIA Service Activation and Service Status Change Notification | PENDING |
Recovery after HSIA Service Instantiation Timeout
Test Case ID | C1 |
|---|---|
Test Case Name | Recovery after HSIA Service Instantiation Timeout |
Description | During service instantiation, SO waits for CPE PNF to be registered. There is a 14-day timeout. After timeout service instantiation is rolled back. |
Release | Frankfurt (6.0.0) |
Preconditions | SO is configured with the right mapping between resource models and BPMN recipes. See BBS Documentation (Frankfurt) |
Testing Steps | |
Expected Results | |
Actual Results | |
Conclusion (Pass/Fail) | NOT TESTED |
Testing Lab | |
Testing Date | |
Tester Name |
CPE Registration
Test Case ID | C2 |
|---|---|
Test Case Name | CPE Registration |
Description | CPE PNF PnP |
Release | Frankfurt (6.0.0) |
Preconditions | - BBS E2E service instance and CPE PNF resource object have been created in AAI by SO - Access SDN M&C IP is configured in SDNC DG in ONAP |
Testing Steps |
|
Expected Results |
|
Actual Results | 0. Service order is sent to ONAP via ExtAPI, the service instantiation is started by SO, SO creates a PNF resource in AAI and waits for the PNF_READY event to continue with the rest of resources PNF Resource in AAI after step 0{
"pnf-name": "Huawei-4857544302FF269D",
"pnf-id": "cc726992-8f34-4008-9ef3-3a406852f283",
"in-maint": false,
"resource-version": "1559724100728"
}1. Access SDN M&C notifies RESTCONF collector with a PNF registration event PNF Registration Event{
"event": {
"commonEventHeader": {
"startEpochMicrosec": 1555076831055,
"eventId": "registration_15550768310388",
"sequence": 0,
"domain": "pnfRegistration",
"lastEpochMicrosec": 1555076831054,
"eventName": "pnfRegistration",
"vesEventListenerVersion": "7.0.1",
"eventType": "pnfRegistration",
"sourceName": "Huawei-4857544302FF269D",
"priority": "Normal",
"version": "4.0.1",
"reportingEntityName": "VESMapper"
},
"pnfRegistrationFields": {
"unitType": "",
"serialNumber": "4857544302FF269D",
"additionalFields": {
"remote-id": "AC9.000.010.001",
"attachmentPoint": "001-5-1",
"cvlan": "10",
"svlan": "100"
},
"pnfRegistrationFieldsVersion": "2.0",
"manufactureDate": "",
"modelNumber": "",
"lastServiceDate": "",
"unitFamily": "",
"vendorName": "Huawei",
"oamV4IpAddress": "",
"oamV6IpAddress": "",
"softwareVersion": "v1"
}
}
}2. VES mapper maps RESTCONF event to VES message and publish the message in DMaaP's unauthenticated.VES_PNFREG_OUTPUT unauthenticated.VES_PNFREG_OUTPUT"{\"event\":{\"commonEventHeader\":{\"startEpochMicrosec\":1555076831055,\"eventId\":\"registration_15550768310388\",\"internalHeaderFields\":{\"collectorTimeStamp\":\"Wed, 06 05 2019 09:22:03 UTC\"},\"eventType\":\"pnfRegistration\",\"priority\":\"Normal\",\"version\":\"4.0.1\",\"reportingEntityName\":\"VESMapper\",\"sequence\":0,\"domain\":\"pnfRegistration\",\"lastEpochMicrosec\":1555076831054,\"eventName\":\"pnfRegistration\",\"vesEventListenerVersion\":\"7.0.1\",\"sourceName\":\"Huawei-4857544302FF269D\"},\"pnfRegistrationFields\":{\"unitType\":\"\",\"serialNumber\":\"4857544302FF269D\",\"additionalFields\":{\"remote-id\":\"AC9.000.010.001\",\"attachmentPoint\":\"001-5-1\",\"cvlan\":\"10\",\"svlan\":\"100\"},\"pnfRegistrationFieldsVersion\":\"2.0\",\"manufactureDate\":\"\",\"modelNumber\":\"\",\"lastServiceDate\":\"\",\"unitFamily\":\"\",\"vendorName\":\"Huawei\",\"oamV4IpAddress\":\"\",\"oamV6IpAddress\":\"\",\"softwareVersion\":\"v1\"}}}"3. PRH consumes PNF registration VES event Updated PNF resource object in AAI5. PRH publishes PNF_READY event in DMaaP's unauthenticated.PNF_READY topic unauthenticated.PNF_READY6. SO consumes PNF_READY event and proceeds with service orchestration Complete service instance with PNF and Generic-VNFs (AccessConnectivity and InternetProfile) |
Conclusion (Pass/Fail) | |
Testing Lab | |
Testing Date | |
Tester Name |
CPE Authentication
Test Case ID | C3 |
|---|---|
Test Case Name | CPE Authentication |
Description | Right after the service is instantiated, it's orchestration-status is "Assigned". The service instance becomes "Active" only after the CPE Authentication is successful. Edge SDN M&C reports to ONAP about CPE Authentication |
Release | Frankfurt (6.0.0) |
Preconditions | BBS E2E Service has been successfully instantiated by ONAP and it's orchestration-status is "Assigned". |
Testing Steps | 1. Edge SDN M&C detects and reports via a VES event the CPE Authentication. The VES event contains the CPE / PNF correlation ID as sourceName 2. BBS-ep process the CPE Authentication VES event and triggers policy to update the orchestration status of the service instance 3. BBS APEX's policy updates the service instance in AAI with the correct orchestration-status |
Expected Results | Service instance orchestration-status is updated from "Assigned" to "Active" |
Actual Results | 0. Service is instantiated and stored in AAI with orchestration-status = "Assigned" Service instance in AAI, orchestration-status="Assigned"1. Edge SDN M&C detects and reports via a VES event the CPE Authentication. The VES event contains the CPE / PNF correlation ID as sourceName CPE Authentication VES message2. BBS-ep process the CPE Authentication VES event and triggers policy to update the orchestration status of the service instance 3. BBS APEX's policy updates the service instance in AAI with the correct orchestration-status Updated service instance in AAI |
Conclusion (Pass/Fail) | |
Testing Lab | |
Testing Date | |
Tester Name |
HSIA Service Activation and Service Status Change Notification
Test Case ID | C4 |
|---|---|
Test Case Name | HSIA Service Activation and Service Status Change Notification |
Description | After service activation, the BSS is notified by ExtAPI about the service instance being active |
Release | Frankfurt (6.0.0) |
Preconditions | CPE Authentication is successful |
Testing Steps | 1. Check that service instance orchestration-status is active in AAI 2. Check that External API is sending to the BSS listener a notification on service activation right after CPE Authentication |
Expected Results | 1. Service instance orchestration-status=active 2. BSS listener is notified about service activation |
Actual Results | 1. Service instance orchestration-status=active 2. BBS portal (BSS mockup) is notified that service is completed by ExtAPI listener |
Conclusion (Pass/Fail) | |
Testing Lab | |
Testing Date | |
Tester Name |