| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | |
| Gary Wu | cd47a01 | 2018-11-30 07:18:36 -0800 | [diff] [blame] | 4 | .. _docs_5g_pnf_software_upgrade: |
| 5 | |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 6 | |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 7 | 5G PNF Software Upgrade |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 8 | ----------------------- |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 9 | |
| 10 | Description |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 11 | ~~~~~~~~~~~ |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 12 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 13 | The 5G PNF Software upgrade use case shows how users/network operators can modify the software of a PNF instance during installation or regular maintenance. This use case is one aspect of Software Management. This could be used to update the PNF software to a different version of software. |
| Yaoguang Wang | a6d37fe | 2019-07-09 11:39:14 +0800 | [diff] [blame] | 14 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 15 | Useful Link |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 16 | ~~~~~~~~~~~ |
| Yaoguang Wang | a6d37fe | 2019-07-09 11:39:14 +0800 | [diff] [blame] | 17 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 18 | `PNF Software Upgrade Wiki Page <https://wiki.onap.org/display/DW/PNF+software+upgrade+in+R6+Frankfurt>`_ |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 19 | |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 20 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 21 | Current Status in Frankfurt |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 22 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 23 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 24 | PNF Software Upgrade Scenarios |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 25 | ------------------------------ |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 26 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 27 | There are 3 PNF software upgrade scenarios supported in Frankfurt release: |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 28 | |
| DarraghEgan | 78f8d30 | 2020-03-19 15:46:57 +0000 | [diff] [blame] | 29 | * `Using direct Netconf/Yang interface with PNF <docs_5G_PNF_Software_Upgrade_direct_netconf_yang.html>`_ |
| Yaoguang Wang | a6d37fe | 2019-07-09 11:39:14 +0800 | [diff] [blame] | 30 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 31 | - (https://wiki.onap.org/pages/viewpage.action?pageId=64007309) |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 32 | |
| DarraghEgan | 78f8d30 | 2020-03-19 15:46:57 +0000 | [diff] [blame] | 33 | * `Using Ansible protocol with EM <docs_5G_PNF_Software_Upgrade_ansible_with_EM.html>`_ |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 34 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 35 | - (https://wiki.onap.org/pages/viewpage.action?pageId=64007357) |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 36 | |
| DarraghEgan | 78f8d30 | 2020-03-19 15:46:57 +0000 | [diff] [blame] | 37 | * `Using Netconf/Yang interface with EM <docs_5G_PNF_Software_Upgrade_netconf_with_EM.html>`_ |
| Yaoguang Wang | a6d37fe | 2019-07-09 11:39:14 +0800 | [diff] [blame] | 38 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 39 | - (https://wiki.onap.org/pages/viewpage.action?pageId=64008675) |
| Yaoguang Wang | 8a15648 | 2018-11-30 09:21:22 +0800 | [diff] [blame] | 40 | |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 41 | Common tasks for all scenarios |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 42 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 43 | |
| 44 | SO Workflows |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 45 | ~~~~~~~~~~~~ |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 46 | |
| 47 | Common SO workflows are used with generic SO building blocks which can be used for any PNF software upgrade scenarios. In Frankfurt release, a PNF software upgrade workflow and a PNF preparation workflow have been created. |
| 48 | |
| 49 | .. image:: files/softwareUpgrade/SWUPWorkflow.png |
| 50 | |
| 51 | LCM evolution with API Decision Tree |
| mrichomme | efb859d | 2020-03-19 19:02:41 +0100 | [diff] [blame] | 52 | ==================================== |
| DarraghEgan | a48752e | 2020-03-13 16:47:55 +0000 | [diff] [blame] | 53 | |
| 54 | A decision point has been introduced in the Frankfurt release. The service designer needs to indicate which LCM API they would like to use for the LCM operations on the selected PNF source at design time (via SDC). The possible LCM APIs are: SO-REF-DATA (default), CDS, SDNC, or APPC. |
| 55 | |
| 56 | .. image:: files/softwareUpgrade/APIDecisionTree.png |