VMware Integrated OpenStack 1.0 Release Notes
VMware Integrated OpenStack 1.0 | 12 MARCH 2015 | ISO Build 2567172
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 and cover the following topics:
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.
Installation Notes for This Release
Read the VMware Integrated OpenStack documentation for step-by-step
instructions on installing and configuring VMware Integrated OpenStack.
VMware Integrated OpenStack 1.0.0 is available in the English language only. ASCII characters must be used for any input and naming conventions of OpenStack resources (such as project names, usernames, image names, and so on) or the underlying infrastructure (such as ESXi hostnames and datastore names).
vSphere version requirements vary.
For deployments using NSX-V for networking, you require vSphere 5.5 Update 2 Enterprise or vSphere 6 Enterprise.
For deployments using VDS for networking, you require vSphere 5.5 Update 2 Enterprise Plus or vSphere 6 Enterprise Plus.
If you installed the Beta edition of VMware Integrated OpenStack, you cannot upgrade to the released version.
You must install the new version of the software.
After you deploy the OVA for the VMware Integrated OpenStack Manager, the OpenStack icon might not appear in the Inventories panel in the vSphere Web Client. Log out of vSphere and log in again. The icon should now appear.
Insufficient heap size can cause your deployment to fail. Heap size is affected by many factors. Read VMware KB 2021302 to determine the best heap size configuration for your system.
Open Source Components for VMware Integrated OpenStack 1.0
The copyright statements and licenses applicable to the open source software components distributed in VMware Integrated OpenStack 1.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.
VMware Integrated OpenStack 1.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.
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.0
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.
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 is preferred, 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.