7 Upgrading VNFM
The VNFM upgrade must be performed in the following sequence for both Primary and Secondary VNFM:
- Change the VNFM state to secondary.
- Delete the current VNFM stack. All the data is stored in the volume that is created during the installation process. This acts as a persistent storage, so the stack can be safely deleted and the volume is automatically detached from the stack.
- Follow the steps provided in the VNFM Installation procedure with the new IMAGE
provided. Flavor, Volume need not be created again. The existing volume ID should be
given as the volume ID in the
dsrVnfmParams.yaml
file. - the 5.4.x Primary VNFM (transformed to Primary from step2) should be converted to Stand alone VNFM for the VNF's which cannot be upgraded (for eg IDIH).
- Invoke "VNF Upgrade by VnfInstanceId" and "All VNF Upgrades" endpoint to upgrade the VNF's.
- Deploy the 6.1.0 secondary VNFM from 6.1.0 primary VNFM.
Note:
- VNFM supports both the fixed and dynamic IP support. In order to bring up the new VNFM with the same IP as the existing one, the user can use FIXED IP deployment model.
- If the existing volume required to be attached to other stack is full (around 7GB), then it takes some time to boot the VNFM and load the data.