VMware Integrated OpenStack 1.0.3 Release Notes

VMware Integrated OpenStack 1.0.3 | 23 OCTOBER 2015 | BUILD 3170584

What's in the Release Notes

The release notes cover the following topics:

About VMware Integrated OpenStack

VMware Integrated OpenStack greatly simplifies deploying an OpenStack cloud infrastructure by streamlining the integration process. VMware Integrated OpenStack delivers out-of-the-box OpenStack functionality and an easy configuration workflow through a deployment manager vApp that runs directly in vCenter.

All information about this release is highly confidential and subject to the non-disclosure terms and conditions in the Master Software Beta Test Agreement that your company has already agreed to.

Updated Feature Improvements in this Release

VMware Integrated OpenStack enables the rapid deployment of OpenStack on a VMware vSphere virtual platform. This release provides the following new features and enhancements.

  • Improved optional log collection services:

    • Option to collect only non-rolled logs.

      viogetlogs -nrl


      viogetlogs --non-rollover-log-only

    • Option to collect logs of specific services.

      viogetlogs -svc [nova|database|heat|keystone|ceilometer|cinder|glance|neutron|horizon|memcached|messagequeue|vio|loadbalancer]


      viogetlogs --service-only [nova|database|heat|keystone|ceilometer|cinder|glance|neutron|horizon|memcached|messagequeue|vio|loadbalancer]


The VMware Product Interoperability Matrix provides details about the compatibility of the current version of VMware Integrated OpenStack with VMware vSphere components, including ESXi, VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install VMware Integrated OpenStack or other VMware products.

Applying the Version 1.0.3 Patch

You upgrade to version 1.0.3 by installing a patch (1.0.3 Build 3170446) on version 1.0.0, version 1.0.1, or version 1.0.2.

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

  1. Obtain the patch (Build

    • Log into the VMware Integrated OpenStack management server.

    • Download the debian file for the patch.

      NOTE: An existing Adobe bug might prevent downloading the file using Firefox. For more information, see Problem uploading patch file in Firefox Web Browser below.

    • 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-3

  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-3 --version

      The patch installation takes up to 10 minutes to complete.

      NOTE: During the patch installation, the API endpoint is automatically turned off. As a result, any API calls during installation will return a 503 error.

  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 an earlier patch version by uninstalling Patch 3.

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

      viopatch uninstall --patch vio-patch-3 --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.

  • An existing Adobe bug may affect performing the update using Firefox. For more information, see Problem uploading patch file in Firefox Web Browser below.

  • 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.3 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.

Open Source Components for VMware Integrated OpenStack 1.0.3

The copyright statements and licenses applicable to the open source software components distributed in VMware Integrated OpenStack 1.0.3 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.

Updated Known Issues

VMware Integrated OpenStack 1.0.3 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.

  • Unable to modify syslog setting post deployment in VIO Manager interface

    After deploying VIO, you cannot modify the syslog server configuration using the setting in the VIO Manager interface (VMware Integrated OpenStack >Management Server > Edit Settings > vApp Options).

    Workaround: Modify the configuration here: VMware Integrated OpenStack>OpenStack Cluster > Manage > LogInsight.

  • 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.

  • Long image upload times cause NotAuthenticated failure.
    This is a known OpenStack issue (https://bugs.launchpad.net/glance/+bug/1371121), first reported in the Icehouse release.

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

  • OpenStack Management Service does not restart after vSphere HA event.
    If vSphere experiences an HA event (for example, the ESXi host hosting the OpenStack Management Server), when vSphere HA restarts, the OpenStack Management Service remains is not restarted. Observed in vCenter Server 5.5.

    Workaround: If a vSphere HA event occurs that affect the OpenStack deployment, ensure that the OpenStack Management Service has restarted. Restart manually if necessary.

  • 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. Specifically, the following characters are not permitted in Glance datastore names because their use is reserved for other purposes and therefore can interfere with the configuration: : , / $ (colon, comma, forward slash, dollar).This issue has been fast-tracked for resolution.

  • Nova boot creating a new volume from OVF fails.
    OVF is an unsupported format.

    Workaround: Convert the OVF to an OVA using the appropriate VMware tool or use another supported format.

  • VMware Integrated OpenStack dashboard (Horizon) throws a 504 Gateway Timeout.
    After approximately 1500 networks have been configured, clicking Networks in the dashboard navigation panel might result in a 504 error.

  • If either controller VM reboots, high availability might be compromised.
    When a controller fails, the other controller continues to provide services. However, when the initial controller reboots, it might no longer provides services, and thus is not available if the other controller also fails. This issue has been fast-tracked for resolution.

    Workaround: If a controller fails and HA is invoked, review your deployment to ensure that both controllers are providing services after the failed controller reboots.

  • vSphere Datacenter Names with Commas Prevent Deployment.
    If the VMware vSphere Datacenter name has a comma in it (for example: "Palo Alto, CA"), you will be unable to deploy VMware Integrated OpenStack. The deployment wizard displays an invalid parameter error.

    Workaround: If possible modify datacenter names to be used for VMware Integrated OpenStack deployments to omit the "," character.

  • Images inaccessible from Glance datastores.
    If you change the name of your data center, images on the Glance data center become inaccessible. Future OpenStack development is planned to make such accessibility less sensitive to data center name changes.

    Workaround: If you have changed the name of your data center, change it back.

  • Adding new tenant logical router to shared Edge breaks static route.
    When a static route is added to a shared Edge VM for one router, there is no check for a conflict on the shared Edge VM on another router. This issue is fixed for version 2.0. but not this patch.

  • Problem uploading patch file in Firefox Web Browser.
    If you are using Firefox to update the patch for VMware Integrated OpenStack, the upload will fail if Firefox is using version 19 of the Adobe Flash plugin. Per the Adobe Bug Base (https://bugbase.adobe.com/index.cfm?event=bug&id=4037494), this issue affects only the Firefox browser. VMware has tested the Chrome browser; it is not affected by this issue.

    Workaround: You can work around this issue by using an alternative browser, such as Chrome, or restoring the Flash plugin in your Firefox browser to an earlier version (15,16,17 of 18.)

Resolved Issues

  • Volume extend fails if a shadow VM has a disk chain.
    The extend volume feature is not supported when the volume contains one or more snapshots. Fixed in VMware Integrated OpenStack 1.0.3.

  • 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. Fixed in VMware Integrated OpenStack 1.0.3.

  • Nova component is choked and becomes unreachable and times out.
    When Nova is choked for a long time, the master message queue becomes unreachable under the benchmark "NovaServers.boot_and_delete_servers". Fixed in VMware Integrated OpenStack 1.0.3.

  • Database node failure might block access to the dashboard for up to thirty minutes.
    If the master database node fails and restarts, users may not be able to log in to VMware Integrated OpenStack dashboard (Horizon) for up to thirty minutes. Observed in vCenter Server 5.5. Fixed in VMware Integrated OpenStack 1.0.3.

  • 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. Fixed in VMware Integrated OpenStack 1.0.3.

  • Connection to Neutron fails for specific operations.
    Observed in VMware Integrated OpenStack deployments with NSX-V 6.1.3. When creating security groups or rules or attaching floating IP, the connection to Neutron timed out. Fixed in VMware Integrated OpenStack 1.0.3.