You can your recover OpenStack deployment from disaster by using the Integrated OpenStack Manager web interface.

Prerequisites

  • Ensure that you have your networks, and vCenter Server environment ready. For more information, see section Preparing Your Environment.
  • Ensure that you have installed Install the VMware Integrated OpenStack Virtual Appliance.
  • In vSphere, take a snapshot of the Integrated OpenStack Manager virtual machine. You need this snapshot for deleting and recreating your deployment.
  • Verify that all required clusters and datastores are available. If you add any resources to your vSphere environment after starting the deployment wizard, for you to see the changes, you must close and reopen the wizard.
  • Verify that you have set the DNS server correctly and that the network gateway or the firewall forwards DNS requests on private networks.
  • For NSX-T Data Center deployments, obtain the values of the following parameters:
    • FQDN or the IP address of the NSX Manager.
    • User name and password to access the NSX Manager.
    • Overlay transport zone.
    • VLAN transport zone.
    • Tier-0 router.
    • DHCP profile.
    • Metadata Proxy Server and secret.
  • Ensure that the backup file exists in content library of target management vCenter server. Please do not rename the backup file during import and after it is imported.

Procedure

  1. Log in to the Integrated OpenStack Manager web interface as the admin user.

    You can access the web interface by opening the IP address of the Integrated OpenStack Manager in a web browser. To find the IP address, select the Integrated OpenStack Manager virtual machine in the vSphere Client and view the Summary tab.

  2. Select OpenStack Deployment, and click Recover from Disaster.
  3. Enter the FQDN or IP address of your management vCenter Server instance specify its administrator credentials. Also, enter the Content Library name, which must be Local content library type, Content Library Item name, and its description.
  4. Click Next.
  5. Check the deployment name, deployment mode, number of controllers, and controller size. These parameters are source system configurations, and any changes on them cannot affect the target system.
  6. Click Next.
  7. Under Management network, select the management network from the drop-down menu, select whether to enable DHCP, and specify an IP address for the private OpenStack endpoint.
    Note: If you disable DHCP, you must enter the details for the following options:
    • One, or more IP address ranges for the network .
    • Subnet mask for the range.
    • The gateway address.
    • One or more DNS servers .
    • You cannot include the IP address of the private OpenStack endpoint in any of the IP address range specified for the management network.
  8. Under API network, select the API access network from the drop-down menu, select whether to enable DHCP, specify an IP address for the public OpenStack endpoint and optionally specify a public hostname.
    Note: If you disable DHCP, you must enter the details for the following options:
    • One, or more IP address ranges for the network .
    • Subnet mask for the range.
    • The gateway address.
    • One or more DNS servers .
    • You cannot include the IP address of the private OpenStack endpoint in any of the IP address range specified for the API access network.
    • After the initial deployment, you cannot change the public hostname for the public OpenStack endpoint.
  9. Under Control plane resources, select the vSphere data center, resource pool, and datastore that you want to use for the OpenStack control plane.
    Note: You cannot change the datastore after you deploy the control plane.
  10. Under Persistent storage, select a datastore and click Next.
  11. Enter the parameters for your networking backend.
    1. Enter the FQDN, or IP address of the NSX Manager and its administrator credentials and click Validate.
    2. Select the default transport zones, tier-0 router, DHCP server profile, and Metadata Proxy Server from the drop-down menus.
    3. Enter the Metadata Proxy Server secret and click Next.
  12. Under Nova configuration, click Add and select the target vCenter Server instance containing your compute cluster which you must map to source Nova computes listed above target Nova compute.
  13. Enter the Nova availability zone for the instances in the target cluster.
  14. Select the desired cluster and datastore and click Submit. 

    You can click Add again to include multiple compute clusters in your deployment.
  15. Confirm compute setting and click Next.
  16. Under Glance configuration, click Add and select vCenter Server instance containing the datastore that you want to use to store images.
  17. Select one or more datastores and click OK.
  18. Confirm your image datastore settings and click Next.
  19. Under Cinder configuration, click Add and select the vCenter Server instance containing the cluster that you want to use for the block storage which you must map to source Cinder clusters listed on top of the target Cinder cluster.
  20. Select VMDK as the backend driver.
  21. Enter an Availability zone for the target cluster.
  22. Select one or more clusters and click OK.
  23. Confirm your block storage settings and click Next.
  24. Review your selected settings and click Finish.

Results

The Integrated OpenStack Manager begins to restore your OpenStack cloud, and the status of the deployment is displayed as Provisioning. When the status changes to Running, you can see the finished deployment.
Note: Do not scale out the deployment or add components (such as Designate) while the deployment is in the Provisioning state. For the multiple Neutron AZ, you must add the AZ manually after the management recovery is complete.