Migrate to the New VMware Integrated OpenStack Deployment

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

Prerequisites

• Install the VMware Integrated OpenStack 6.0 virtual appliance. 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

1. Log in to the old OpenStack Management Server as viouser.
2. Switch to the root user.

   sudo su -

3. Decompress and run the upgrade conversion script.

   tar -xzf vio-upgrade-6.0-build-number.tar.gz
   cd upgrade
   ./upgrade.sh
   

   Before running the script, you must change the current working directory to the directory containing the script.

   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)
4. Stop the old VMware Integrated OpenStack deployment.

   sudo viocli deployment stop

   Note: OpenStack services will be unavailable until the migration process is finished.
5. In the vSphere Client, create a content library named VIO.
6. 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.
7. Transfer the cluster.yaml and restore.yaml files to the new Integrated OpenStack Manager.
8. Log in to the new Integrated OpenStack Manager as the root user.
9. Apply the cluster configuration file to the new VMware Integrated OpenStack deployment.

   kubectl -n openstack create -f cluster.yaml

10. 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.
• For VDS deployments, update the Neutron configuration to create four DHCP agents per network.
  1. Log in to the new Integrated OpenStack Manager as the root user.

  2. Modify the Neutron configuration.

     viocli update neutron

  3. In the conf section, create the neutron section. In the neutron section, create the DEFAULT section.

  4. In the DEFAULT section, add the dhcp_agents_per_network parameter and set its value to "4".

     The configuration file now looks similar to the following:

     conf:
       plugins:
         [...]
       neutron:
         DEFAULT:
           dhcp_agents_per_network: "4"
     manifests:
       [...]

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.