This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

 

VMware Integrated OpenStack 6.0.0.1 | 13 FEB 2020 | Build 15475612

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 that runs as a virtual appliance in vCenter Server.

Compatibility

See the VMware Product Interoperability Matrices for details about the compatibility of VMware Integrated OpenStack with other VMware products, including vSphere components.

Upgrading to Version 6.0.0.1

You can upgrade directly to VMware Integrated OpenStack 6.0.0.1 from VMware Integrated OpenStack 5.1 or 6.0.

If you are running VMware Integrated OpenStack 5.0 or an earlier version, first upgrade to version 5.1 and then upgrade to version 6.0.0.1.

Deprecation Notices 

  • The following networking features have been deprecated and will be removed in a future version:
    • The NSX Data Center for vSphere driver for Neutron.
    • The NSX-T Manager driver for Neutron. In the future, the NSX-T Policy Manager driver will be used.
    • The TVD plugin, which allows a single VMware Integrated OpenStack deployment to use an NSX Data Center for vSphere back end and a NSX-T Data Center back end.
  • Neutron LBaaS has been deprecated and will be replaced in a future version by the OpenStack Octavia project.

Internationalization

VMware Integrated OpenStack 6.0.0.1 is available in English and seven additional languages: Simplified Chinese, Traditional Chinese, Japanese, Korean, French, German, and Spanish.

The following items must contain only ASCII characters:

  • Names of OpenStack resources (such as projects, users, and images)
  • Names of infrastructure components (such as ESXi hosts, port groups, data centers, and datastores)
  • LDAP and Active Directory attributes 

Open Source Components for VMware Integrated OpenStack

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

Resolved Issues

  • For NSX Data Center for vSphere deployments, load balancers fail after an upgrade to VMware Integrated OpenStack 6.0.

    If your VMware Integrated OpenStack 5.1 environment with NSX Data Center for vSphere has load balancers in the ACTIVE state, these load balancers will enter the ERROR state after you upgrade to VMware Integrated OpenStack 6.0.

    This issue has been resolved in this release.

  • For NSX Data Center for vSphere deployments, a route cannot be added to a distributed router.

    When you attempt to manually add a route to a distributed router, the following error message is displayed:

    Invalid input for operation: Cannot specify router-size for distributed router.

    This issue has been resolved in this release.

  • RabbitMQ may fail to start.

    Incoming messages may consume all disk space assigned to RabbitMQ, making it unable to start normally. For more information about this issue, see KB 76392.

    This issue has been resolved in this release.

  • VMware Integrated OpenStack cannot be deployed on a vSphere data center named in a certain format.

    If the name of your data center contains a period (.) followed by an uppercase letter (for example, DC.Test), VMware Integrated OpenStack will fail to deploy.

    This issue has been resolved in this release.

  • VMware Integrated OpenStack cannot connect to a vCenter Server instance whose hostname includes uppercase letters.

    If you specify a vCenter Server instance by an FQDN that includes uppercase letters, VMware Integrated OpenStack is unable to obtain credentials to access the vCenter Server instance.

    This issue has been resolved in this release.

  • Migrating an instance with an attached volume may cause the volume to be deleted.

    If an instance and its attached volume are located on different datastores, and you migrate the instance to the datastore currently containing the volume, the volume will be deleted.

    This issue has been resolved in this release.

Known Issues

  • Public API rate limiting is not available.

    In VMware Integrated OpenStack 6.0, it is not possible to enforce rate limiting on public APIs.

    Workaround: None. This feature will be offered in a later version.

  • If the image metadata vmware:extra_config has been configured, the flavor extra spec vmware_extra_config does not take effect.

    If you set the vmware:extra_config metadata on an image, the vmware_extra_config extra spec on the flavor will be ignored even when the specific extra_config values of the image metadata and flavor extra spec do not conflict.

    Workaround: Configure all desired extra_config values either in the image metadata only or in the flavor extra spec only.

  • The log analytics server information may be displayed after the server has been removed.

    If you configure a log analytics server when deploying OpenStack and later remove the server from your deployment, the log analytics IP address may still be displayed on the Integrated OpenStack Manager web interface.

    Workaround: None. Although the IP address is still displayed, the server has been removed from your deployment.

  • Removing a compute cluster with instances and later adding it again may fail.

    If you remove a compute cluster from your deployment without first deleting all instances from that cluster, stale entries remain in the Nova database. If you then add the cluster under a different name, the operation may fail. Due to differences in naming conventions, this issue will occur if you delete a compute cluster added in a previous version of VMware Integrated OpenStack and re-add it to your deployment in VMware Integrated OpenStack 6.0.

    Workaround: Remove all instances from a compute cluster before removing the cluster from your deployment.

  • Snapshots on a controller node prevent the node from being migrated properly.

    The persistent volume on a controller node cannot be moved if a snapshot of the controller node exists. Taking a snapshot of a controller is not supported.

    Workaround: Delete all snapshots on controller nodes.

  • For NSX-T Data Center deployments, a maximum of 125 allowed IP address pairs can be updated in a single operation.

    The NSX-T Data Center back end supports a maximum of 128 IP addresses on a single port, including fixed IP addresses and allowed IP address pairs. When you use the Neutron command-line interface to update a port, entering more than 125 allowed IP address pairs in a single operation is not supported.

    Workaround: None.

  • vCenter Server instances that contain no compute clusters are not retained during upgrade.

    If your existing deployment includes vCenter Server instances from which no compute nodes have been added to your deployment, the settings for those vCenter Server instances are not retained after you upgrade to VMware Integrated OpenStack 6.0.

    Workaround: Add the desired vCenter Server instances to your VMware Integrated OpenStack 6.0 deployment after the upgrade is finished.

  • Log files may not be retained when pods are restarted.

    If you perform an operation, such as a configuration change, that results in pods restarting, the log files from those pods may be deleted.

    Workaround: Use VMware vRealize Log Insight or another compatible log analytics platform to ensure log persistence.

  • For NSX-T Data Center deployments, Layer 7 polices for LBaaS may not be enforced.

    NSX-T Data Center does not support per-pool session persistence profiles. The Layer 7 policy of any pool other than the default pool of the target server does not take effect.

    Workaround: None.

  • If incorrect credentials are entered when deploying OpenStack, the wizard may fail to recognize correct credentials.

    During the OpenStack deployment process, if vCenter Server or NSX Manager credentials are entered incorrectly, the wizard may fail to recognize correct credentials. Even if you remove the incorrect information and enter the correct credentials, the wizard may fail to validate them.

    Workaround: Close the deployment wizard and open it again.

  • Volumes created from images are always bootable by default.

    If you include the --non-bootable parameter when creating a volume from an image, the parameter does not take effect.

    Workaround: After the volume has been created, update it to be non-bootable.

  • After you upgrade to VMware Integrated OpenStack 6.0, a default pool cannot be added to existing LBaaS listeners.

    VMware Integrated OpenStack 5.x does not support changing the default pool of an LBaaS listener. This feature is supported in VMware Integrated OpenStack 6.0. However, if you create an LBaaS listener in VMware Integrated OpenStack 5.x that does not have a default pool, you cannot add a default pool to the listener even after upgrading to VMware Integrated OpenStack 6.0.

    Workaround: Delete the affected listener and create it again.

  • For NSX Data Center for vSphere deployments, session persistence settings cannot be modified for LBaaS pools with multiple listeners.

    If you attempt to modify the session persistence settings for an LBaaS pool with more than one listener attached, the load balancer will enter the error state.

    Workaround: None.

check-circle-line exclamation-circle-line close-line
Scroll to top icon