You back up your existing data to the new deployment and then migrate to the new deployment. This procedure starts the new deployment and stops the old deployment.

Prerequisites

Install VMware Integrated OpenStack 5.0. See Install the New Version.

Procedure

  1. Log in to the new OpenStack Management Server and prepare a directory to store the backup.
    sudo viocli upgrade prepare old-mgmt-server-ip /nfs-server-folder
  2. Log in to the old OpenStack Management Server and back up its data to the prepared directory.
    sudo viocli backup mgmt_server new-mgmt-server-ip:/nfs-server-folder
  3. Log in to the new OpenStack Management Server again and reconfigure the new installation using the data backed up from the old installation.
    sudo viocli upgrade mgmt_server backup-directory new-mgmt-server-ip:/nfs-server-folder

    The backup directory name is in the format vio_ms_timestamp.

  4. If your current deployment is running VMware Integrated OpenStack 4.1.1 or later, modify the build number in the database of the new OpenStack Management Server.
    cd /opt/vmware/vpostgres/9.6/bin/
    ./psql -Uomsdb
    UPDATE cluster SET build_number = '8909571';

    This is not required if your current deployment has not been patched after version 4.1.0.

  5. Log out of the vSphere Web Client and log back in.

    This refreshes the interface so that the new deployment is displayed.

  6. In the vSphere Web Client, select Home > VMware Integrated OpenStack.
  7. Click the Summary tab and verify that the Version Information table shows the version of the new VMware Integrated OpenStack installation.
  8. Click the Manage tab and click the Upgrades tab.
  9. In the table displayed, right-click the current deployment and select Upgrade.
    1. Enter a name for the new deployment.

      This name must be different from the name of the current deployment.

    2. If you are upgrading from a compact deployment, select a deployment type for your new deployment in the Deployment type drop-down menu.

      During the upgrade process, you can change a compact deployment to an HA deployment if desired.

    3. Click Next, review the upgrade configuration, and click Finish

    The status of the current deployment is Running, and the status of the new deployment is Provisioning.

  10. After the status of the new deployment changes to Prepared, right-click the name of the old deployment and select Migrate Data.
    Important:

    This action will stop OpenStack services. Services will be down until the upgrade finishes.

    When the migration process finishes, the status of the new deployment changes to Migrated.

  11. Right-click the name of the old deployment and select Switch to New Deployment.

    When the migration process finishes, the status of the new deployment changes to Running, and the status of the previous deployment changes to Stopped.

Results

OpenStack services are now provided by the new deployment.

What to do next

  • Upgrade your license key in My VMware. See KB 2006974.

  • Update any DNS entries to use the IP addresses of the new VMware Integrated OpenStack deployment.

  • For NSX-T deployments, update the metadata proxy configuration in NSX Manager to use the IP address of the new OpenStack Management Server.

  • If you have integrated your deployment with vRealize Automation, perform the integration procedure after upgrading VMware Integrated OpenStack. See Integrate VMware Integrated OpenStack with vRealize Automation.

  • If you integrated your deployment with VMware Identity Manager using the custom.yml file, reconfigure integration after upgrading VMware Integrated OpenStack. See Configure VMware Identity Manager Integration.

If the upgrade is unsuccessful or you do not want to use the new version, you can revert to your previous VMware Integrated OpenStack deployment. See Revert to a Previous VMware Integrated OpenStack Deployment.

If the upgrade is successful, you can delete the old VMware Integrated OpenStack deployment. See Delete the Old VMware Integrated OpenStack Deployment.