Versions Compared

Old Version 32

changes.mady.by.user Raj Gumma

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.

Table of Contents
Image Removed

Overview:

The Netconf configuration over TLS use case consists The E2E integration test consists of three main parts:

  • SO will implement two more steps in workflow CONFIG-ASSIGN and CONFIGURE step.
  • CDS Blueprint Processor will implement the mount, configure and un-mount requests to SDNC after getting CONFIGURE request from SO. The processor currently has the ability to read a blueprint from archive and process it.
  • SDNC will load client cert , trusted certs and private key at deployment time. ODL should also be upgraded to Flourine SR2 version to serve above requests. The upgrade is being tracked as part of SDNC-555

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


Gliffy Diagram
size600
nameSDC-service-distribution Copy
pagePin1

Image Added


Image Added


Deployment:

Test environment requirements for the test cases:

  • xNF simulator for test cases:  PNF Simulator with TLS & YANG support.Rest Client simulator.
  • SO with Config-Assign and Configure steps implemented in workflows.
  • 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. RUN : Yet to update

Use Case preconditions:

    • xNF simulator.Rest Client sim.

E2E Netconf config over TLS Sequence Diagram

Image Removed

High Level End-to-End feature integration

Testcases

Test cases :


#Test Case
Status
Description
1After PNF_READY, SO sends CONFIG-ASSIGN and CONFIGURE request to Self Service API (SS-API)2SO Sends CONFIGURE request to SS-API3Verify SDN-C have client cert, private key and trusted certs setup at deployment
ReferenceTester
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 : 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

NETCONF_CONFIGURATION_TLS_E2E

4Connect SDN-C and PNF Simulator for configuration step5E2E test case for NETCONF over TLS6

Successful flow: CONFIG-ASSIGN and CONFIGURE steps will conclude as expected, and the desired configuration will be applied to the PNF; successful outcome

Detailed Description End-to-End Feature Integration Testcases :

Test Case ID AnchorConfiguration Entry PointConfiguration Entry PointTest Case NameSO sends CONFIG-ASSIGN and CONFIGURE request to SS-APIDescriptionEnsure that PNF_READY notification is received by SO from simulated environment then SO sends CONFIG-ASSIGN request to SS-APIReleaseDublinPre-conditions

SO should be waiting for PNF_READY notification after registration process and fully configured as per registration process.

Follow the 5G - PNF PnP - Integration Test Cases T01, T02, T03, T04 to complete the PNF registration and waiting for the PNF_READY notification.

Testing StepsStepsExpected Result
  1. Send PNF_READY to SO
  2. SO will send CONFIG-ASSIGN to SS-API
  3. Receive it and Check if it is correct
  4. Send OK response to SO
  5. SO will send CONFIGURE request to SS-API
  6. Receive it and check if it is correct
  7. Send OK response to SO

The SO accepted the "PNF_READY" Notification.

and sends out the CONFIG-ASSIGN request to SS-API

and receive an OK response from SS-API

Conclusion (Pass /Fail)Testing LabTest Case IDNetconf_TLS_E2E_02Test Case Name

Sends CONFIGURE request to SS-API

DescriptionIn this simulated CONFIG-ASSIGN request will be sent to SS-API and response will be picked to check if response is OK.ReleaseDublinPre-conditions

Blueprint processor should have access to correct blueprint in archive to process it.

SDN-C should be available

Testing Steps

StepsExpected Result
  • Sends CONFIGURE request to SS-API
  • SS-API will receive it
    • SS-API send CONFIGURE request to Blueprint Processor component.
  • Component sends Mount to SDN-C
  • Receive this request read it if it is correct
    • Send OK 200 response
  • Blueprint processor sends configuration request to SDN-C
  • Receive this request read it if it is correct
    • SDN-C sends OK 200 response
  • Blueprint processor sends un-mount request to SDN-C
  • Receive this request read it if it is correct
  • SDN-C sends OK 200 response

    • Check for mount, configure and un-mount messages triggered by the Blueprint processor component.

    Verify that messages are valid and reflect all the expected parameters.

    Conclusion (Pass /Fail)Testing LabTest Case IDNetconf_TLS_E2E_03Test Case Name

    Check SDN-C has client cert, private key and trusted certs setup at deployment

    DescriptionSDN-C configure client cert, private key and trusted certs and deployment time. This test case verifies if all certificates are configured fine.ReleaseDublinPre-conditions

    SDN-C should be up and running successfully

    Testing Steps

    StepsExpected Result
    1. Send GET request from rest client to SDN-C for key store
    2. Verify if it has all necessary entries for Client cert, trusted certs and private key.

    Get request should get all certs and private key successfully.

    Conclusion (Pass /Fail)Testing LabTest Case IDNetconf_TLS_E2E_04Test Case Name

    Connect SDN-C and PNF simulator for configuration step

    DescriptionSDN-C/ODL will send mount , configure and un-mount request to PNF simulator and check if PNF simulator is configured successfully.ReleaseDublinPre-conditions

    PNF simulator should be up and running with TLS port listening. It should also be configured with Yang Models necessary for configuration request.

    Testing Steps

    StepsExpected Result
  • Send mount request to SDN-C from rest client.
  • Check for 200 OK response
  • Send GET request for mount
    • Check data from GET response
  • Send configuration request to SDN-C from rest client.
  • Check for 200 OK response
  • Send GET request for configuration
    • Check data from GET response
  • Send un-mount request to SDN-C from rest client
  • check for 200 OK response
  • Send GET request for un-mount
    • Check data from GET response

    Get response should give correct result for mount, configure and un-mount.

    Conclusion (Pass /Fail)Testing LabTest Case IDNetconf_TLS_E2E_05

    Test Case Name

    E2E test case for NETCONF over TLS

    DescriptionEnsure that PNF_READY notification is received by SO from
    simulated environment
    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
    PNF simulator
    1. install sdnc.
    2. 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 PNF_READY to SO(This step will trigger a run to SS-API, BP component, SDNC and PNF simulator)
  • Send SSH mount/connect request to SDNC/ODL using rest client.
  • Send GET request for configuration to get configuration, set in step 1.
  • Verify received configuration is correct.
    • Get response should give correct result for configure
    Conclusion (Pass /Fail)Testing LabTest Case IDNetconf_TLS_E2E_06Test Case Name

    Successful flow

    DescriptionSteps assignConfig and deployConfig will conclude as expected, and the desired configuration will be applied to the PNF
    Release

    Dublin

    Pre-conditions

    Valid PNF
    Valid blueprint
    SO is primed and post PNF registration stage
    ODL instance is installed and available

    Testing Steps

    StepsExpected Result

    1. SO sends a request to perform action assignConfig

    Code Block
    languageyml
    blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String

    2. SS-API forwards the request to BP, that will load the blueprint, execute the action specified, prepare the configlet, persist it and return a successful message to SO

    3. SO recognizes the success message and sends a request to perfom action deployConfig

    Code Block
    languageyml
    blueprintName: String
blueprintVersion: Integer
action: String
pnf-name: String
pnf-ip: String
    4. SS-API forwards the request to Blueprint Processor, that will load the blueprint, execute the action specified, retrieve the configlet from the persistence, connect to ODL, send the configlet(s) to the PNF and return a successful message to SO
    1. SO sends CONFIG-ASSIGN request to CDS.
    2. SO receives the response from CDS for CONFIG-ASSIGN as success.
    3. SO sends CONFIG-DEPLOY  async request to CDS.
    4. CDS sends patch(includes mount, configure and unmount request) to SDNC.
    5. SDNC sends mount request to PNF-SIM using TLS connection.
    6. CDS send connection status to SDNC for PNF-SIM.
    7. SDNC sends configuration request to PNF-SIM.
    8. SDNC sends unmount request to PNF-SIM.
    9. Verify received configuration is correct on PNF-SIM (Manual verification).
    		Get response should give correct result for configuration on PNF-SIM



    Conclusion (Pass /Fail)

    Status
    colourGreen
    titlePassed

    Testing Lab
    ?

    Ericsson Lab, Windriver Lab


    Information:


    Next Step(s):