diff options
author | DarraghEgan <darragh.egan@est.tech> | 2020-03-13 16:47:55 +0000 |
---|---|---|
committer | DarraghEgan <darragh.egan@est.tech> | 2020-03-19 15:21:25 +0000 |
commit | a48752e10bd5dfa7588fe33fb7d6bff40f137731 (patch) | |
tree | d1c30e08a6d3c8a5bcaa4c465f67c41ec675f0a0 /docs/docs_5G_PNF_Software_Upgrade_direct_netconf_yang.rst | |
parent | b1778edfe0339c9225b760c1e01f1c794403991b (diff) |
[INT-1450] : Documentation of PNF Software Upgrade
This contains documentation for PNF Software Upgrade
with direct Netconf/Yang interface with PNF
Issue-ID: INT-1450
Signed-off-by: Darragh Egan <darragh.egan@est.tech>
Change-Id: I58acec3baed757bdc8cad2e2588c560f31c9025c
Diffstat (limited to 'docs/docs_5G_PNF_Software_Upgrade_direct_netconf_yang.rst')
-rw-r--r-- | docs/docs_5G_PNF_Software_Upgrade_direct_netconf_yang.rst | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/docs/docs_5G_PNF_Software_Upgrade_direct_netconf_yang.rst b/docs/docs_5G_PNF_Software_Upgrade_direct_netconf_yang.rst new file mode 100644 index 000000000..f2d4db1a4 --- /dev/null +++ b/docs/docs_5G_PNF_Software_Upgrade_direct_netconf_yang.rst @@ -0,0 +1,36 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + +.. _docs_5g_pnf_software_upgrade_direct_netconf_yang: + +=========================================================================== +PNF Software Upgrade Scenario: Using Direct Netconf/Yang interface with PNF +=========================================================================== +Software Upgrade Procedure +------------------------------------ + +With this scenario, the pre-conditions are: + +* SO PNF software upgrade workflows are ready to use +* An SDC service template with one PNF resource has been designed (including CBA association) and has been distributed +* Service instantiation is completed, including PNF PnP. meaning a PNF instance is in operation with connectivity between PNF-ONAP, PNF-SFTP +* At design time, the CONTROLLER_ACTOR is set for CDS client for the API selection decision +* PNF has direct NETCONF/YANG interface configured which can be reachable from ONAP controller. + +At run time, the PNF in-place software upgrade procedure is triggered when the operator provides the selected PNF software upgrade workflow, a PNF instance, and the target software version using VID GUI or CLI. +Then the software upgrade workflow is executed in SO: + +a. SO sends CDS request(s) with action-identifier {actionName, blueprintName, blueprintVersion} to the blueprint processor inside the controller using CDS self-service API +b. Controller/blueprint processor executes the blueprint scripts including sending NETCONF request(s) to the PNF instance via the direct NETCONF interface. +c. Repeat above two steps for each SO building blocks. + + .. image:: files/softwareUpgrade/DirectNetconfYangInterface.png + + +Test Status and Plans +------------------------------------ + +To see information on the status of the test cases please follow the link below: + +`PNF Software Upgrade Test Status <https://wiki.onap.org/display/DW/PNF+software+upgrade+in+R6+Frankfurt#PNFsoftwareupgradeinR6Frankfurt-TestStatus>`_ + |