Migrate to the New VMware Integrated OpenStack Deployment

You run an upgrade conversion script on your old deployment to generate the files required for upgrade. Then you apply the upgrade files on your new deployment to complete the migration process.

Prerequisites

Install the VMware Integrated OpenStack 7.0 virtual appliance and apply the 7.0.1 patch. See Install the New Virtual Appliance.
Confirm that your existing VMware Integrated OpenStack deployment is running properly. On the old OpenStack Management Server, run the viocli deployment status command.
Verify that the backup functionality on the existing VMware Integrated OpenStack deployment works properly and that the disk is not full.
Transfer the upgrade conversion script to the old OpenStack Management Server.

Procedure

Log in to the old OpenStack Management Server as viouser.
Switch to the root user.
```
sudo su -
```
Decompress and run the upgrade conversion script.
```
tar -xzf vio-upgrade-7.0.1.0-build-number.tar.gz
```
Before running the script, change the current working directory to the directory containing the script.
```
cd upgrade
```
```
./upgrade.sh
```
When prompted, enter the password for the viouser account.
The script collects a support bundle, backs up the OpenStack database, and generates the following files:
- /tmp/pre_upgrade/upgrade.tar.gz
- ./cluster.yaml
- ./restore.yaml
- ./themes.tar (only if you have previously customized the VMware Integrated OpenStack dashboard theme)

(Optional) The upgrade migrates your old deployment to a new medium-sized deployment by default. To change the size of the new deployment, edit the cluster.yaml file and change the size of the VMware Integrated OpenStack manager and controller nodes.

The following example cluster.yaml file shows the size of the manager and controller nodes set to large.

apiVersion: vio.vmware.com/v1alpha1
kind: VIOMachineSet
metadata:
  labels:
    app: lcm
    clusterController: "true"
  name: manager1
spec:
  count: 1
  providerConfig:
    value:
      machineSpec:
        datacenter: sanity_dc
        datastore: datastore-nfs
        resourcePool: VIO_resource_pool
  size: large                                
  vmware_insecure: .VCenter:vcenter1:spec.insecure
  vmware_server_host: .VCenter:vcenter1:spec.hostname
  vmware_server_password: .VCenter:vcenter1:spec.password
  vmware_server_username: .VCenter:vcenter1:spec.username
---
apiVersion: vio.vmware.com/v1alpha1
kind: VIOMachineSet
metadata:
  labels:
    app: lcm
    clusterController: "true"
  name: controller1
spec:
  count: 3
  providerConfig:
    value:
      machineSpec:
        datacenter: sanity_dc
        datastore: datastore-nfs
        resourcePool: VIO_resource_pool
  size: large
  vmware_insecure: .VCenter:vcenter1:spec.insecure
  vmware_server_host: .VCenter:vcenter1:spec.hostname
  vmware_server_password: .VCenter:vcenter1:spec.password
  vmware_server_username: .VCenter:vcenter1:spec.username

Stop the old VMware Integrated OpenStack deployment.
```
sudo viocli deployment stop
```
Note: OpenStack services are unavailable until the migration process is finished.
In the vSphere Client, create a content library named VIO.
Upload the /tmp/pre_upgrade/upgrade.tar.gz file to the content library.
If the themes.tar file was generated, upload the file to the content library also.
Note: Before clicking Import, verify the names of the files that appear. If upgrade.tar.gz is missing the .gz extension, add it. If themes.tar is missing the .tar extension, add it.
Transfer the cluster.yaml and restore.yaml files to the new Integrated OpenStack Manager.
Log in to the new Integrated OpenStack Manager as the root user.
Apply the cluster configuration file to the new VMware Integrated OpenStack deployment.
```
kubectl -n openstack create -f cluster.yaml
```
Apply the upgrade configuration file to the new VMware Integrated OpenStack deployment.
```
kubectl -n openstack apply -f restore.yaml
```

Results

OpenStack services are now provided by the new deployment.

What to do next

Assign your VMware Integrated OpenStack license key to the new deployment. See Upgrade and Assign Your License Key.
Update any DNS entries to use the IP addresses of the new VMware Integrated OpenStack deployment.
For NSX-T Data Center deployments, update the metadata proxy configuration in NSX Manager to use the private OpenStack endpoint of the new deployment.

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.