6 Upgrading VNFM
VNFM upgrade is not supported in this release.
Ivolume needs to be re-used for a new VNFM stack on the same release, perform the
following procedure:
- Change the VNFM state to SECONDARY
- Delete the current VNFM Stack.
Note:
Volume acts as a persistent storage and the data is stored in the volume. The stack can be safely deleted. The volume will be automatically detached from the stack. The user must follow the steps provided in the VNFM Installation procedure with
the new IMAGE provided. The Volume should not be created again. Use the existing IMAGE,
Flavor and volumeID in the dsrVnfmParams.yaml file.
After the the new VNFM is deployed successfully, change the state of the new VNFM to PRIMARY, if required.
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.