VMware Cloud Director App Launchpad 22.214.171.124 | 18 JUN 2020 | Build 16408912
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
App Launchpad 126.96.36.199 includes a number of resolved issues.
You can use the RPM package file to install or upgrade App Launchpad.
To install App Launchpad, see Installing and Configuring App Launchpad.
To upgrade your App Launchpad 1.0 instance to version 188.8.131.52, see Upgrade.
You can perform an in-place upgrade directly to App Launchpad 184.108.40.206 from App Launchpad 1.0.
To upgrade to App Launchpad 220.127.116.11, do the following.
- Download the App Launchpad RPM package file.
- Open an SSH connection to the App Launchpad machine.
- Stop the App Launchpad service by running the
systemctl stop alpcommand.
- Replace the RPM package by running the following command:
rpm -Uvh path-to-new-RPM/vmware-alp-version_number-build_number.x86_64.rpm
- If the version of VMware Cloud Director that you run supports NSX-T, add the Organization vCD Gateway: View right to the App-Launchpad-Service role.
- Log in to the VMware Cloud Director Service Provider Portal as a system administrator.
- Navigate to Administration > Roles.
- Select the App-Launchpad-Service role and click Edit.
- Navigate to Networking > Gateway and select View Gateway.
- Click Save.
- To update the App Launchpad user interface, run the
alp connectscript. For more information about the command, see step 3a in Install App Launchpad.
- Start the App Launchpad service by running the
systemctl start alpcommand.
In addition to the current release notes, you can use the App Launchpad documentation set at https://docs.vmware.com/en/VMware-Cloud-Director-App-Launchpad/index.html.
- Launching an application fails when you use routed networks with no DNAT rules defined in the Edge gateway
If there are no defined DNAT rules in the Edge gateway, you cannot launch applications using routed networks.
- App Launchpad cannot work with RabbitMQ if RabbitMQ is configured to use an SSL port
If you configure the AMQP extensibility of VMware Cloud Director with only an SSL port, you cannot register App Launchpad as a service extension.
- If you set a firewall rule (HTTP_HTTPS or NONE) by using the advanced deployment options of App Launchpad, the rule has no effect on the network access of the application
Firewall rule settings apply to the vApp network. However, a deployed application might not have vApp networks, so the setting does not take effect.
- When you import applications from VMware Marketplace to App Launchpad, the logo and summary for the applications do not update after a successful import
After the completion of a successful import of an application from VMware Marketplace to App Launchpad, the logo and the summary of the application are not displayed in the App Launchpad user interface.
- When launching applications, to use a routed network that is backed by NSX-T, you must select it from the list of internal networks
To launch applications, you can use routed networks that are backed by NSX-T. Such networks are available for selection from the list of internal networks.
Workaround: Select a routed network from the internal networks list and use the Edge NAT settings to control the network access for the application.