VMware Integrated OpenStack 1.0.1 Patch Release Notes

VMware Integrated OpenStack 1.0.1 | 17 APRIL 2015 | Build 2668568

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes apply to VMware Integrated OpenStack 1.0.1 and cover the following topics:

Issues Resolved in this Patch

VMware Integrated OpenStack enables the rapid deployment of OpenStack on a VMware vSphere virtual platform. This release resolves the following issues.

  • Installer Improvements. The deployment wizard has been modified to provide clearer instructions to the user. This includes improvements to the screen titles, labels, and field names.

  • OpenStack Security Issue. Version 1.0.1 includes the OpenStack security patches that address a websocket hijacking vulnerability. Read OpenStack Security Advisory OSSA-2015-005 for more information.

  • Improved Keystone Token Generation. When creating approximately 50 or more concurrent VMs, version 1.0.1 improves performance by reducing the number of token requests generated by the Nova service.

Open Source Components for VMware Integrated OpenStack 1.0.1

The copyright statements and licenses applicable to the open source software components distributed in VMware Integrated OpenStack 1.0.1 are available on the Open Source tab of the product download page. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of VMware Integrated OpenStack.

Applying the Version 1.0.1 Patch

You upgrade to version 1.0.1 by installing a patch (1.0.1 Build 2668568) on version 1.0.0.

The following procedures assume you have installed version 1.0.0. This patch updates the product UI and therefore must be installed using the CLI instructions documented below.

  1. Updated Obtain the patch (Build

    • Log into the VMware Integrated OpenStack management server.

    • Download the debian file for the patch.

    • Add the patch with the following command:

      viopatch add -l [path to the debian file]

    • Confirm that the patch was successfully added:

      viopatch list

      This returns a list of available patches, their version numbers, their type, and current status. The list should include vio-patch-1

  2. Install the patch.

    • Ensure that VMware Integrated OpenStack service is either running or not yet deployed.

      If the VMware Integrated OpenStack service is in any other state, the upgrade will fail.

    • Log into the VMware Integrated OpenStack management server and run the following command:

      viopatch install --patch vio-patch-1 --version

      The patch installation takes 5 to 10 minutes to complete.

  3. To complete the update, log out of the vSphere Web Client and back in.

    You can ignore any error messages you encounter when logging back in.

  4. If necessary you can revert to version 1.0 by uninstalling Patch 1.

    • Log into the VMware Integrated OpenStack management server and run the following command:

      viopatch uninstall --patch vio-patch-1 --version

      The reversion process takes 5 to 10 minutes to complete.

    • After uninstalling the patch, you must restart the vSphere Web Client service on the vCenter Server to downgrade the VMware Integrated OpenStack plugin.

      Read VMware KB 2054085 to learn about restarting vCenter Server appliance services.

Troubleshooting the Patch Installation

The following list describes common problems you might encounter when installing the patch, and their solutions.

  • Updated Error returned when using the vSphere Web Client to add patch.

    Add and install the patch using the CLI method described in Applying the Version 1.0.1 Patch.

  • Patch installation fails.

    Ensure that the OpenStack deployment is either running or not yet deployed. If it is running, ensure that all the OpenStack management VMs (memcache, loadbalancer, and so on) are also running.

    If you restart any of the VMs, run the vioconfig configure command on the OpenStack management server CLI and apply the patch again.

Known Issues

VMware Integrated OpenStack 1.0.1 has the following known issues. If you encounter an issue that is not in this known issues list, search the VMware Knowledge Base, or let us know by contacting VMware Technical Support.

  • Dashboard might show a Volume as attached even if it failed to attach
    This is a known OpenStack issue, first reported in the Icehouse release.

  • Insufficient heap size can cause deployment to fail
    Heap size is affected by many factors. Read VMware KB 2021302 to determine the best heap size configuration for your system.

  • Clusters and datastores might not be selectable for the OpenStack deployment
    When selecting or adding a cluster or datastore, it might not be selectable for several reasons that are enforced by the VMware Integrated OpenStack Manager. Typically, the cluster or datastore is already configured or consumed by another resource.

    • The datastore is already configured for the current cluster.

    • The datastore is not mounted to the current cluster.

    • For Compute nodes: the cluster is already being consumed by another Compute node or NSX-V Edge node.

    • The cluster has no available datastores.

    • The cluster has no reachable host.

  • Host route injection doesn't work in VMware Integrated OpenStack 1.0.1
    This issue has been fast-tracked for resolution.

  • Deployment fails because no DNS addressing is configured
    The VMware Integrated OpenStack installer indicates in the Configure Networking screen that supplying DNS entries are optional. However, if you will use LDAP for authentication, the hostname for the LDAP server might require DNS.

    Workaround: Before you begin the installation process, check to see if the hostname for your LDAP server requires DNS.

  • OpenStack dashboard does not immediately reflect volume extension
    If you extend the size of a volume, the dashboard might still display the pre-extended size. Eventually, the correct size appears.

  • Cluster status might be inaccurate
    If some of the node VMs in a cluster are powered off but others are not, the cluster still shows a status of RUNNING in the vSphere Web Client.

    Workaround: If you suspect a cluster contains nodes that are not running, open the cluster and check the status of the individual nodes. You can also start all the nodes in the VMware Integrated OpenStack service by manually powering on each node, and then logging into the CLI and using the sudo vioconfig start command.

  • False error alert displays during provisioning
    When you accept the configuration settings and start the installation process, you might get an error alert even though the provisioning continues. This is a false error.

    Workaround: Refresh the browser.

  • Unable to create VSAN datastore
    You get an error message when you try to create a datastore in a nested ESXi instance using an OpenStack volume backed by VSAN. This is an ESXi issue related to SCSI reservations.

    Workaround: Log into the console for the ESXi VM and configure the VSAN to fake SCSI reservations by using the following command: esxcfg-advcfg -s 1 /Misc/VsanFakeSCSIReservations

  • CLI actions for stop/start not reflected in vSphere Web Client
    If you use the CLI commands to stop or start the VMware Integrated OpenStack service, the service might still appear to be running in the vSphere Web Client even though the command was successful. For example, if you stop the service using the CLI command (vioconfig stop), you will not be able to access the VMware Integrated OpenStack dashboard.

    Workaround: Use the vSphere Web Client GUI commands to stop or start the VMware Integrated OpenStack service.

  • Installer gives priority to local storage by default
    When provisioning datastores for the three database VMs, the VMware Integrated OpenStack installer automatically gives priority to local storage to improve I/O performance. For resiliency, users might prefer shared storage, but the installer does not make it clear how to modify this setting.

    Workaround: Before you complete the installation process, the VMware Integrated OpenStack installer allows you to review and modify the configuration. You can use this opportunity to change the datastore configuration for the three database VMs.

  • Special characters in datastore names not supported by Glance (Image Service)
    If a datastore name has non-alphanumeric characters like colons, ampersands, or commas, the datastore cannot be added to the Glance service. This issue has been fast-tracked for resolution.

  • Edge VMs require shared datastores
    When you configure your Edge VMs, ensure that the cluster you select for Edge VMs has shared datastores. Without configuring shared datastores for that cluster, all the Edge VMs attach to the same local datastore of one ESXi host, limiting host selection and negatively affecting performance.