7 Upgrading VNFM

Perform the following procedure for both primary and secondary VNFM each one after the other:

1. Change the VNFM state to secondary.
2. The current VNFM stack must be deleted. All the data is stored in the volume which is created in the install procedure. This acts as a persistent storage, so the stack can be safely deleted - the volume will be automatically detached from the stack.
3. The user must follow the steps in the Install and Configure VNFM with the new IMAGE provided. Flavor, Volume need not be created again. The existing volume ID must be given as the volume ID in the dsrVnfmParams.yaml file.

   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 that is going to be attached to other stack is full (around 7GB), then it will take some time to restart the VNFM and load the data.
   • It supports with same versions of VNFM releases, major VNFM version upgrade is not supported. For Backward compatibility, user must follow Discover Stack feature.