7 Upgrading VNFM

Perform the following procedure for both primary and secondary VNFM:

  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. For installation, see Install and Configure VNFM section, with the new image provided.

    Note:

    Flavor and volume need not be created again.
  4. The existing volume id must be given as the volume id in the dsrVnfmParams.yaml file.

    Note:

    • VNFM supports both 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 being attached to another stack is full (about 7GB), the VNFM will take longer to restart and load the data.
    • It generally supports only the same VNFM release versions, major VNFM version upgrade is not supported. For backward compatibility, use the Discover VNF stack operation feature.
    • If the VNFM version is older than VNFM 6.0.2.x and if the user wants to migrate to VNFM 6.0.2.x or later, user must use the Discover VNF API.