VMware Integrated OpenStack 3.0 Release Notes

Updated on: 28 FEB 2017

VMware Integrated OpenStack 3.0 | 15 SEPTEMBER 2016 | BUILD 4345506

Check for additions and updates to these release notes.

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.

Internationalization

VMware Integrated OpenStack version 3.0 is available in English and seven additional languages: Simplified Chinese, Traditional Chinese, Japanese, Korean, French, German, and Spanish. ASCII characters must be used for all input and naming conventions of OpenStack resources (such as project names, usernames, image names, and so on) and for the underlying infrastructure components (such as ESXi hostnames, vSwitch port group names, data center names, datastore names, vSwitch port group names, and so on).

New Features 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.

  • Seamless Upgrade to Mitaka release of OpenStack. VMware Integrated OpenStack 2.x was based on the Kilo release. By upgrading to 3.0, you skip the Liberty release.

  • Create a Volume from an Existing Virtual Disk. The Mitaka upgrade also enables this feature, which allows administrative users to create Cinder volumes from existing virtual disks that are attached to VMs in vSphere. The disk is detached from the vSphere VM before it is imported as a Cinder volume. For specific commands, see the OpenStack documentation. NOTE: For the identifier positional argument, use the format <vmdk_path>@<vm_inventory_path>.

  • New Compact Mode Deployment Option. VMware Integrated OpenStack 3.0 offers a compact-mode deployment option that installs OpenStack on a single physical node and offers real-time database backup. Compact mode is intended for multiple, small deployments. See the VMware Integrated OpenStack Installation and Configuration Guide for details.

  • Improved Deployment and Upgrade. The workflows for installation and upgrade have been improved to increase deployment success, reduce the need to start over in the event of an error, and to streamline the process. See the VMware Integrated OpenStack Installation and Configuration Guide for details.

  • Support for Importing vSphere VMs into OpenStack. VMware Integrated OpenStack 3.0 enables you to import vSphere VMs into OpenStack, where they can be managed like OpenStack instances. See the VMware Integrated OpenStack Administration Guide for details.

  • Multi-Domain Backend Support for Keystone. VMware Integrated OpenStack 3.0 includes multiple backend support for Keystone, allowing administrators to configure both local database and Active Directory resources simultaneously. In multiple domain mode, the local database is used for the local administrative user and the OpenStack service users; the Active Directory backend is used for OpenStack users and groups. See the VMware Integrated OpenStack Installation and Configuration Guide for details.

Compatibility

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.

Upgrading to VMware Integrated OpenStack 3.0

New Upgrade from VMware Integrated OpenStack 2.5.2 to VMware Integrated OpenStack 3.0 and 3.1 is not supported. 

You perform the upgrade procedure directly in the VMware Integrated OpenStack manager. The complete multi-step procedure is described in detail in the VMware Integrated OpenStack Administrator Guide.

Open Source Components for VMware Integrated OpenStack 3.0

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

Known Issues

VMware Integrated OpenStack 3.0 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 > Syslog Server.

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

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

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

  • Metadata service is not accessible on subnets created with the no-gateway option.
    Deployments using NSX 6.2.2 or earlier do not support no-gateway networks; Edges are used for edge-routed networks and DHCP is used for VDR networks. Deployments using NSX 6.2.3 or later do not support no-gateway or no-dhcp networks; DHCP is used for any DHCP network and Edges are used for non-DHCP networks. In 2.x, autoconfiguration is turned off for Edge VMs. When applicable, DHCP sets the gateway and metadata is served through this gateway Edge. As a result, when a subnet is created with the the no-gateway option, there is no router Edge to capture the metadata traffic.

    Workaround: For networks with the no-gateway option, configure a route for 169.254.169.254/32 to forward traffic to DHCP Edge IP.

  • Horizon dashboard shows error after switching projects as admin user
    If you are logged into Horizon as the administrative user and try to switch between projects using the drop-down menu in Horizon, the dashboard might begin returning errors. This is caused by an issue in OpenStack.

    Workaround: Log out of the Horizon dashboard and log back in to restore the dashboard.

  • Problem uploading patch file in Firefox 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.

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

  • OpenStack management service does not automatically restart.
    Under certain conditions, the OpenStack management service does not automatically restart. For example, after a failover event, all OpenStack services successfully restart but the management service remains unreachable.

    Workaround: Manually restart the VMware Integrated OpenStack vApp in the vSphere Web Client. Right-click the icon in the Inventory page and select Shut Down. After all the services shut down, power on the vApp. Check the OpenStack manager logs to confirm that the restart was successful.

    NOTE: Restarting interrupts services. This issue is fast-tracked for resolution in a future VMware Integrated OpenStack release.

  • Network creation sometimes fails when running Heat templates.
    Observed in VMware Integrated OpenStack deployments using NSX 6.2.2. When running multiple Heat templates, an iteration of a network creation sometimes fails at the backend.

    Resolved in NSX 6.2.3 and greater.

  • Recovery operation returns "Nodes already exist" error.
    Under certain conditions, running the viocli recovery - <DB name> command fails if the ansible operation is interrupted. As a result, the database nodes remain and causes the error.

    Workaround: Manually remove the nodes and run the viocli recovery command again.

  • LBaaS v2 migration: health monitors not associated to a pool do not migrate.
    In LBaaS v2, health-monitors are required to specify and be attached to a pool. In LBaaS v1, health monitors can be created without pool association, and associated with a pool in a separate procedure.

    As a result, when migrating to LBaaS v2, unassociated health monitors are excluded.

    Workaround: Before migrating to LBaaS v1, associate all health monitors with a pool to ensure their successful migration. The migration process is optional after installing or upgrading to VMware Integrated OpenStack 3.0. See the VMware Integrated OpenStack Administration Guide.

  • NSX LBaaS v2.0 tenant limitation.
    NSX load balancers support only one tenant per subnet. Under normal operation, this is not an issue because tenants create their own load balancers. If a user attempts to create and attach a load balancer to a subnet, the load balancer will be created in an ERROR state.

    Workaround: Allow tenants to create their own load balancers. Do not create and attach a load balancer to an existing subnet.

  • Operations times out with error "Connection reset by peer".
    Observed in VMware Integrated OpenStack 2.0.1 deployments using NSX 6.2.1. Sometimes the HA proxy will time out due to insufficient timeout configuration in the load balancer and controller node settings.

    Workaround: Edit the custom.yml to modify the timeout values. Add or modify the following parameters as shown.

    neutron_client_socket_timeout: 1500
    haproxy_neutron_client_timeout: 1500s
    haproxy_neutron_server_timeout: 1500s
  • Heat stack deletion fails with "Failed to publish configuration on NSX Edge" error.
    Observed in deployments using NSX v6.2.2. Under stressful conditions, the Heat stack or OpenStack API might fail at the backend.

    Workaround: Retry the failed operation.

    NOTE: This issue is fast-tracked for resolution in a future NSX release.

  • Online documentation: Some graphics might not display.
    If you use the Firefox or Internet Explorer browser to view the online documentation for VMware Integrated OpenStack, some graphics might not display. This does not affect the PDF documentation.

    Workaround: Use the Google Chrome browser. All graphics display without issue.

  • Images must be VMX version 10 or greater.
    This issue affects streamOptimized images and OVAs. For example, if an image is not VMX-10 or greater, it might import without difficulty but OpenStack instances created from the image will not function. This is typically experienced when OpenStack compute nodes are deployed on older ESXi versions, such as 5.5. You also cannot correct such an image by modifying the image metadata (vmware_hw_version) or flavor metadata (vmware:hw_version).

  • Recovery after vSphere HA event shows synchronization and process start-up failures.
    If vSphere experiences and HA event, it can affect your VMware Integrated OpenStack deployment. After the recovery, in VMware Integrated OpenStack, run the viocli deployment status -v command. If the resulting report shows any synchronization or process start-up failures, use the workaround below.

    Workaround: Use the viocli services stop command to stop all OpenStack services. Use the viocli services start command to restart all OpenStack services. After restarting, run the viocli deployment status -v command again. There should be no errors.

  • Interoperability with other VMware products with TLS v1.0 disabled.
    VMware Integrated OpenStack experiences interoperability issues with other VMware products when those products have disabled TLS v1.0 and SSL v3. Many clients are phasing out TLS v1.0 and SSL v3 because they are no longer considered secure by current revisions of the PCI Data Security Standard. Previous versions of VMware Integrated OpenStack disabled TLS v1.0 and SSL v3 on inbound public API connections. VMware Integrated OpenStack v2.5.1 and v3.0 fully interoperate with components that have disabled TLS v1.0 and SSL v3, including vSphere 6.0 update 2, NSX 6.2.4, and LDAP servers.

    Workaround: Disable TLS on the vCenter server where VMware Integrated OpenStack is running.

    1. Modify the /etc/vmware-rhttpproxy/config.xml file.
      <vmacore>
         <ssl>
            <doVersionCheck> false </doVersionCheck>
            <useCompression>true</useCompression>
            <libraryPath></libraryPath>
            <sslOptions> 117587968</sslOptions>
         </ssl>
      ...
    2. Modify the /etc/vmware-vpx/vpxd.cfg file.
      <vmacore>
         <cacheProperties>true</cacheProperties>
         <ssl>
            <useCompression>true</useCompression>
            <sslOptions> 117587968</sslOptions>
         </ssl>
      ...
    3. Restart the vpxd and rhttpproxy services on the vCenter server.
  • OpenStack recovery sometimes fails when starting RabbitMQ.
    In rare occurrences, VMware Integrated OpenStack recovery fails at the point where RabbitMQ initiates.

    Workaround: Repeat the recovery process. Recovery should succeed the second time.

  • Heat stack deletion fails to delete associated Cinder volumes.
    Under heavy loads, Cinder volumes sometimes fail to be deleted after their Heat stacks are deleted, resulting in database deadlock warnings and slower Cinder performance.

    This issue is fast-tracked for resolution in a future release.

  • SQL-configured users cannot be modified in dashboard.
    If your VMware Integrated OpenStack deployment is configured to use LDAP for user authentication, you cannot modify user definitions in the OpenStack dashboard (Horizon) even those that are sourced from a SQL database.

  • OpenStack dashboard: router-size drop-down menu is missing.
    In the OpenStack dashboard (Horizon), you can specify the size when you create an exclusive router. However when you modify a router from shared to exclusive, the router-size drop-down menu does not appear, preventing you from specifying the router size.

    Workaround: Restore the default value, modify type to exclusive again. The drop-down menu should appear.

  • After 3.0 upgrade, the vAPI service is not running.
    After upgrading to VMware Integrated OpenStack 3.0, the vAPI service might be in a failed state.

    Workaround: Manually restart the vAPI service. Use SSH to log into the VMware Integrated OpenStack server. Switch to root user. Run service vapi restart.

  • Backup NSX Edge nodes are not used after upgrade to 3.0.
    Due to changes in the OpenStack Neutron code in Mitaka, the backup Edge nodes are not recognized as available backups. The database column for the nsxv_router_bindings is set to null.

    Workaround: Modify the database column setting for the nsxv_router_bindings to default.

    mysql -D neutron -e "update nsxv_router_bindings set availability_zone='default' where availability_zone is null;"

    Restart the Neutron service.

  • VM import: Passing the root resource pool for tenant mapping fails.
    When importing all unmanaged VMs, the optional --root-resource-pool parameter does not function as expected and can cause the operation to fail.

    Note: This issue is already fixed for the next VMware Integrated OpenStack release.

    Workaround: Do not use this optional parameter.

Resolved Issues

  • Database node failure might block access to the dashboard for up to thirty minutes.
    If the master database node fails and restarts, users might 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 3.0.

  • WaitConditionHandle not working with current heat.conf.
    Using OS::Heat::WaitConditionHandle in a Heat Orchestration Template (HOT) template might generate the following error:

    Resource Create Failed: Error: Resources.Mysql.Resources.Wait Handle: Cannot Get Stack Domain User Token, No Stack Domain Id Configured, Please Fix Your Heat.Conf

    Fixed in VMware Integrated OpenStack 3.0.

  • Adding subnet returns error message.
    When adding a subnet interface to a private network, you receive this error: "Request Failed: internal server error while processing your request". This indicates that the subnet interface points to a router whose gateway network is an external network that does not have a subnet.

    Fixed in VMware Integrated OpenStack 3.0.

  • "nova list" command fails when password is manually entered.
    This is an OpenStack bug documented in detail here: https://bugs.launchpad.net/python-novaclient/+bug/1525378. This issue occurs when the OS_PASSWORD environmental variable for the Nova client is not specified.

    Fixed in VMware Integrated OpenStack 3.0. You are no longer prompted for a password. You can set the password using the OS_PASSWORD environment variable or --os-password CLI option.

  • Template import fails with "400 Bad Request: 10.0.0.1 must match with vcenter-host.example.com"
    Adding a VM template as a Glance image might fail if the location URI used to create the image refers to the vCenter server using IP address because VMware Integrated OpenStack requires the hostname.

    Fixed in VMware Integrated OpenStack 3.0.

  • Unable to select flavor with 0 root disk size.

    If you create a flavor where root_disk=0, that flavor might appears as disabled when a user tries to select it when creating an instance in the VMware Integrated OpenStack dashboard (Horizon).

    Fixed in VMware Integrated OpenStack 3.0.

  • AD/LDAP configuration validates but keystone fails to start.
    During the installation process, the Active Directory/LDAP configuration validates, but the Keystone service fails to start during actual deployment. This issue is caused because the common name of the certificate does not match with the hostname of the LDAP server.

    Fixed in VMware Integrated OpenStack 3.0.

  • Adding router interface fails with flush error.

    Adding router interface operation on a distributed router might fail due to a race condition with the error message "FlushError: New instance <xx>, with identity key <yy> conflicts with persistent instance <zz>".

    Fixed in VMware Integrated OpenStack 3.0.