Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 14 Next »

Table of Contents

Scenario Scope In Frankfurt

This scenario will complete the E2E procedure of PNF in-place SW upgrade case started from Casablanca (evolved in Dublin). The E2E procedure is VID→ SO→ Controller(SDNC/CCSDK)→Ansible Server→ EMS → PNF. 

  • Trigger by VID to upgrade speficific PNF instance's software
  • Enhance SO to support PNF S/W upgrade workflow execution
  • Add SO BBs to do precheck/downloadNESw/activateNESw/UpdateAAI/postcheck using SDNC client

  • Support LCM API for downloadNESw and activateNESw actions

  • Provide ansible playbooks for downloadNESw and activateNESw

  • Enhance EMS emulator for integration test

Since this scenario started from Casanblanca, it is helpful to find more details completed in past releases with following link.

Procedure

Pre-conditions

  • ONAP is ready to use, while min components are VID/SO/SDNC/CCSDK.
  • PNF PnP is completed, and EMS ipaddress is strored in AAI within PNF Registration step, as ipaddressV4Oam.
  • EMS (Emulator) is running, and SFTP (can be with EMS) is ready.

Upgrade procedure

  • (1) In PNF pre-onboarding, operator delivers the PNF packages, including necessary ansible artifacts, to SDC. [playbook distribution is out of scope in this release]
  • (2) In Sw Upgrade runtime, operator initiates the command, via VID or timer, to SO. (Before that, operator should design the upgrade workflow, or use the existing one).
  • (3) SO executes the Sw upgrade task, like A&AI retrieval, and sends LCM requests to the controller.
  • (4) Ansible Adaptor forwards requests to EMS via ansible server.

Sequence Diagram

Impacts

Project/ComponentStory

SO

Support generic PNF workflow design

SO

Support upgrade sw version at PNF instance level

SO

Align with SO building block for PNF Upgrade procedure

1) Create new SO BB – downloadNESw

2) Create new SO BB – activateNESw

3) Create new SO BB – update AAI

4) Update SO BB – preCheck and postCheck

SO

Support different controller decision points in SO

SDNC/CCSDK

Support LCM API for downloadNESw and activateNESw actions

SDNC/CCSDK

Provide ansible playbooks for downloadNESw and activateNESw

VNFRQTS

PNF Software Upgrade with ansible with EM

Integration

1) EMS simulator extension

2) Integration document revision for PNF Sw Upgrade UC

API Impacts Details

 - NBI of SO:

tbd

 - LCM API of CCSDK:

LCM API Abbre.HTTP MethodURIYang Model SectionRequest ExampleResponse Example
UpgradePreCheck*POST/operations/LCM:upgrade-pre-check
rpc upgrade-pre-check {
    description "An operation to check that the VNF has the correct software version needed for a software upgrade.";
    input {
        uses common-header;
        leaf action {
            type action;
            mandatory true;
        }
        uses action-identifiers;
        leaf payload {
            type payload;
            mandatory true;
       }
    }
    output {
        uses common-header;
        uses status;
        leaf payload {
            type payload;
            mandatory true;
                }
    }
}
{
  "input": {
    "action": "UpgradePreCheck",
    "action-identifiers": {
      "pnf-name": "5gDU0001"
    },
    "common-header": {
      "api-ver": "2.00",
      "flags": {
        "force": "FALSE",
        "mode": "NORMAL",
        "ttl": 65000
      },
      "originator-id": "MSO",
      "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "timestamp": "2019-03-15T09:07:58.255Z"
    },
    "payload": "{\"ipaddress-v4-oam\": \"192.168.35.83\", \"playbook-name\": \"ansible_huawei_precheck\", \"oldSwVersion\": \"v1\", \"targetSwVersion\": \"v2\", \"ruleName\": \"r001\", \"additionalData\":\"{}\"}"
  }
}

400: Success

{
    "output": {
        "common-header": {
            "api-ver": "2.00",
            "originator-id": "MSO",
            "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
            "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d"
        },
        "payload": "{\"result\": \"Success\"}",
        "status": {
            "code": 400,
            "message": "Ansible Request  f0f45105-1a51-4592-a31b-f178d5eb4638 finished with Result = success, Message = FINISHED"
        }
    }
}
UpgradePostCheck*/operations/LCM:upgrade-post-check
rpc upgrade-post-check {
    description "An operation to check the VNF upgrade has been successful completed and all processes are running properly.";
    input {
        uses common-header;
        leaf action {
            type action;
            mandatory true;
        }
        uses action-identifiers;
        leaf payload {
            type payload;
            mandatory true;
       }
    }
    output {
        uses common-header;
        uses status;
        leaf payload {
            type payload;
            mandatory true;
                     }
    }
}
{
  "input": {
    "action": "UpgradePostCheck",
    "action-identifiers": {
      "pnf-name": "5gDU0001"
    },
    "common-header": {
      "api-ver": "2.00",
      "flags": {
        "force": "FALSE",
        "mode": "NORMAL",
        "ttl": 65000
      },
      "originator-id": "MSO",
      "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "timestamp": "2019-02-23T09:07:58.255Z"
    },
    "payload": "{\"ipaddress-v4-oam\": \"192.168.35.83\", \"playbook-name\": \"ansible_huawei_postcheck\", \"oldSwVersion\": \"v1\", \"targetSwVersion\": \"v2\", \"ruleName\": \"r102\", \"additionalData\":\"{}\"}"
  }
}

400: Success

{
    "output": {
        "common-header": {
            "api-ver": "2.00",
            "originator-id": "MSO",
            "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
            "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d"
        },
        "payload": "{\"result\": \"Success\"}",
        "status": {
            "code": 400,
            "message": "Ansible Request  c1c14dee-a80d-40b8-800a-9216a27c7d1c finished with Result = success, Message = FINISHED"
        }
    }
}
DownloadNESw/operations/LCM:download-n-e-sw
rpc download-n-e-sw {
    description "An operation to download NE software";
    input {
        uses common-header;
        leaf action {
            type action;
            mandatory true;
        }
        uses action-identifiers;
        leaf payload {
            type payload;
            mandatory true;
        }
    }
    output {
        uses common-header;
        uses status;
        leaf payload {
            type payload;
            mandatory true;
        }
    }
}
{
  "input": {
    "action": "DownloadNESw",
    "action-identifiers": {
      "pnf-name": "5gDU0001"
    },
    "common-header": {
      "api-ver": "2.00",
      "flags": {
        "force": "FALSE",
        "mode": "NORMAL",
        "ttl": 65000
      },
      "originator-id": "MSO",
      "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "timestamp": "2019-10-19T10:20:16.125Z"
    },
    "payload": "{\"ipaddress-v4-oam\": \"192.168.35.83\", \"playbook-name\": \"ansible_huawei_downloadnesw\", \"swToBeDownloaded\": [{\"swLocation\": \"http://192.168.35.96:10080/ran_du_pkg1-v2.zip\", \"swFileSize\": 353, \"swFileCompression\": \"ZIP\", \"swFileFormat\": \"binary\"}]}"
  }
}

400: Success

{
    "output": {
        "common-header": {
            "api-ver": "2.00",
            "originator-id": "MSO",
            "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
            "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d"
        },
        "payload": "{\"result\": \"Success\"}",
        "status": {
            "code": 400,
            "message": "Ansible Request 29cc5afd-082f-49be-bb52-3e96b178480c finished with Result = success, Message = FINISHED"
        }
    }
}
ActivateNESw/operations/LCM:activate-n-e-sw
rpc activate-n-e-sw {
    description "An operation to activate NE software";
    input {
        uses common-header;
        leaf action {
            type action;
            mandatory true;
        }
        uses action-identifiers;
        leaf payload {
            type payload;
            mandatory true;
        }
    }
    output {
        uses common-header;
        uses status;
        leaf payload {
            type payload;
            mandatory true;
        }
    }
}
{
  "input": {
    "action": "ActivateNESw",
    "action-identifiers": {
      "pnf-name": "5gDU0001"
    },
    "common-header": {
      "api-ver": "2.00",
      "flags": {
        "force": "FALSE",
        "mode": "NORMAL",
        "ttl": 65000
      },
      "originator-id": "MSO",
      "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
      "timestamp": "2019-10-19T10:25:28.116Z"
    },
    "payload": "{\"ipaddress-v4-oam\": \"192.168.35.83\", \"playbook-name\": \"ansible_huawei_activatenesw\", \"swVersionToBeActivated\": \"v2\"}"
  }
}

400: Success

{
    "output": {
        "common-header": {
            "api-ver": "2.00",
            "originator-id": "MSO",
            "request-id": "a1171d12-2ae9-496b-a2df-99784572914d",
            "sub-request-id": "a1171d12-2ae9-496b-a2df-99784572914d"
        },
        "payload": "{\"result\": \"Success\"}",
        "status": {
            "code": 400,
            "message": "Ansible Request 0af55193-8177-41a7-b927-78646be6250b finished with Result = success, Message = FINISHED"

        }
    }
}

*: These LCM APIs are enhanced from R4/R5, and update the vnf-id field in action-identifiers to pnf-name in the request parameter.

The playbook-name in the payload of request is optional. If not set the playbook-name in the request, it will use the value in the config file /opt/onap/sdnc/data/properties/lcm-dg.properties of SDNC.


JIRA Status Tracking

key summary type created updated due assignee reporter priority status resolution
Refresh


Test Status

NoTest CaseTest Status
1

UpgradePreCheck for PNF instance from SDNC to EM using LCM API

COMPLETE
2DownloadNESw for PNF instance from SDNC to EM using LCM APICOMPLETE
3ActivateNESw for PNF instance from SDNC to EM using LCM APICOMPLETE
4UpgradePostCheck for PNF instance from SDNC to EM using LCM APICOMPLETE
5Test PNF SW upgrade Workflow for PNF instance from SO to SDNC (using LCM API) to EM

COMPLETE

With Exception: WF was executed as expected (SW version was changed) but not right response from SO.


Initial Status

Initial Status of EMS Simulator



Detailed Description of Integration Testcases and Results

Test case ID1
NameUpgradePreCheck for PNF instance from SDNC to EM using LCM API
DescriptionUpgradePreCheck for PNF instance from SDNC to EM using LCM API
ReleaseFrankfurt
Pre-conditions
Testing Steps


Test Command


Contents of request body


Response of SDNC


Status of EMS Simulator


Conclusion (Pass/Fail)
Test Lab
Test case ID2
NameDownloadNESw for PNF instance from SDNC to EM using LCM API
DescriptionDownloadNESw for PNF instance from SDNC to EM using LCM API
ReleaseFrankfurt
Pre-conditions
Testing Steps


Test Command


Contents of request body

Response of SDNC

Status of EMS Simulator

Conclusion (Pass/Fail)
Test Lab
Test case ID3
NameActivateNESw for PNF instance from SDNC to EM using LCM API
DescriptionActivateNESw for PNF instance from SDNC to EM using LCM API
ReleaseFrankfurt
Pre-conditions
Testing Steps


Test Command

Contents of request body


Response of SDNC


Status of EMS Simulator

Conclusion (Pass/Fail)
Test Lab
Test case ID4
NameUpgradePostCheck for PNF instance from SDNC to EM using LCM API
DescriptionUpgradePostCheck for PNF instance from SDNC to EM using LCM API
ReleaseFrankfurt
Pre-conditions
Testing Steps


Test Command

Contents of request body


Response of SDNC


Status of EMS Simulator

Conclusion (Pass/Fail)
Test Lab
Test case ID5
NameTest PNF SW upgrade Workflow for PNF instance from SO to SDNC (using LCM API) to EM
DescriptionTest PNF SW upgrade Workflow for PNF instance from SO to SDNC (using LCM API) to EM
ReleaseFrankfurt
Pre-conditions
Testing Steps


Test Command

Contents of request body


Status of EMS Simulator

Conclusion (Pass/Fail)
Test Lab
  • No labels