After you obtain and install the upgrade patch, you install it as a separate deployment and migrate your data.
About this task
If you upgrade from VMware Integrated OpenStack 2.x or 3.0 deployment to 3.1, you won't need to configure the public VIP settings for the load balancer service, as this configuration is now automated.
The upgrade process also allows you to switch from a 3.0 compact mode deployment to 3.1 HA deployment.
- If you are logged in to the vSphere Web Client, log out and log back in.
This refreshes the interface so the newly installed patch is accessible through the vSphere Web Client.
- In the vSphere Web Client, select , and click the VMware Integrated OpenStack icon.
- Click the Summary tab to confirm that the VMware Integrated OpenStack manager is upgraded.
The new version appears next to the vApp.
- Click the Manage tab and click the Upgrades tab.
The Upgrades tab lists the current VMware Integrated OpenStack deployment.
- Right-click the deployment name and select Upgrade from the pop-up menu.
- Enter the name for the new deployment.
This name must be different than the name of the existing deployment.
- If you are updating from 3.0 compact mode deployment to 3.1, in the Deployment type drop-down menu, select type for the updated deployment.
If your VMware Integrated OpenStack 3.0 is deployed in compact mode, you can change to HA mode during the update or stay in compact mode.
- Click Next.
- If upgrading to version 3.0, configure the public VIP settings for the load balancer service.
This value serves as the temporary VIP configuration. When you migrate from the existing deployment to the upgraded deployment, the new deployment uses the existing VIP configuration, and the old deployment uses the temporary deployment.
Public Virtual IP
This value should be on the same subnet as the OpenStack API Access network, and should be outside the IP range specified for the OpenStack API Access network.
- Click Next.
- Review the upgrade configuration, and click Finish.
The new deployment is up and running, but it is using a temporary public IP. Users can access it, but only using this temporary public VIP. Only after completion of the following step, is the original public VIP configured on the new deployment. The Upgrades tab now lists the current VMware Integrated OpenStack and new deployments. The current deployment shows a status of Running and the new, upgraded deployment shows a status of Provisioned.
- On the Upgrades tab, right-click the name of the old deployment, and select Migrate Data.
You are prompted to confirm this action because during data migration, the VMware Integrated OpenStack services stop and downtime incurs until the upgrade process finishes.
When the migration process finishes, the status for the updated deployment on the Upgrades tab changes to Migrated.
- On the Upgrades tab, right-click the name of your previous deployment, and select Switch to New Deployment.
When the deployment switching process finishes, the status for the updated deployment on the Upgrades tab changes to Running. The previous deployment shows a status of Stopped.
What to do next
If the deployment process is unsuccessful, you can revert to your previous VMware Integrated OpenStack deployment. See Revert to a Previous VMware Integrated OpenStack Deployment.
If the deployment process is successful, you can delete the previous VMware Integrated OpenStack deployment.