6.4 Stable Release Notes

17 December 2020

We are happy to introduce OnApp 6.4 (6.4.0-23). This document lists features, improvements, and fixes implemented for all available OnApp components within the 6.4 Edge 1 and 6.4.  

Before You Upgrade

You can update to OnApp 6.4 Stable from OnApp 6.3 or 6.4 Edge 1. For details, refer to the Upgrade Guide

To test the upgrade, you may first simulate the upgrade process on the test environment. For the instructions, refer to the Configuring Control Panel Environment for Simulation Purposes page. 


Here you can find the key features that we deliver as a part of OnApp 6.4. You can also check other features and improvements and see the list of issues that were fixed in OnApp 6.4.

VSS Network Management for vCenter

To use OnApp vCenter with vSphere Standard licensing, you may now import existing vSphere Standard Switches from vCenter to OnApp and use them instead of vSphere Distributed Switch, which requires Enterprise Plus licensing.

vCenter Resource Pools

Resource pools allow you to delegate control over resources of a host (or a cluster) so that you can use them to divide into sections all resources in a cluster.

vCenter Cluster as Compute Resource

Now you can create compute resources using clusters, imported with the vCenter server. To connect to vCenter, you can create a vCenter server logical point on the OnApp side and then, add each cluster from the vCenter side as a compute resource on the OnApp side separately. Accordingly, you can create your VS based on the compute resource (cluster) and resource pool that you select on VS creation wizard.

TOTP Authentication

If you would like your users to utilize Google Authenticator or any similar application with their OnApp account to enhance security, you may now enable TOTP authentication for two-factor authentication (2FA).
TOTP stands for Time-based One-time Password algorithm, a common form of Two-factor Authentication, which, offers increased security for 2FA.

Updated UI

In OnApp 6.4, we updated the user interface with the new look and feel for all UI components, including:

  • 505 and 404 Error landing pages

  • tree structure; the status icons and other service icons on the tables and table content
  • the Buckets menu
  • placeholders and inputted texts

User Role Creation

In OnApp 6.4, we improved the user role creation process by introducing the role templates. Now you can create new role based on the default roles (Administrator or User), as well as clone a role and assign it to a new user.

Below you can find a demo video of OnApp 6.4.

The following table lists all the features, improvements, and fixes included into OnApp 6.4 for all available components. 

Features & Improvements

TypeKeyRelease Notes
OnApp Cloud


CORE-16462Now you can enable the TOTP Authentication option for your users to enhance account security by using time-based two-factor authentication for logging in.


CORE-17513Added the ability to clone a default role to a new user.


CORE-10822Improved the charts for instant and hourly CPU utilization.


CORE-12469Updated the design for the 500 Server Error landing page.


CORE-12470Updated the design for the 404 Not Found page.


CORE-13654Now you can set the value for RabbitMQ continuation timeouts.


CORE-15356Improved the appearance of Features at the Compute Resources page.


CORE-16636Now you can use one of the default OnApp roles as a template to create a new custom role.







Updated the icons on the tree structure and the Buckets menu and the status icons and other service icons on the tables and table content.


CORE-17324Now you can start the virtual server with the compute resource having more than 240 vCPUs.


CORE-17606Improved OnApp daemon to accelerate auto-backup jobs processing.


CORE-17702Improved the color of the placeholder and inputted texts.

vCenter and vCloud


CORE-15703Now you can import your vSphere Standard Switches (VSS) from vCenter to OnApp, and use OnApp for vCenter with basic licensing.


CORE-16648Now you can use the vCenter resource pools to delegate control over the resources of a host (or a cluster).


CORE-17158Now you can add and bill for each cluster from the vCenter side as a compute resource on the OnApp side separately. 


CORE-17206 Now you can automatically migrate from old compute resources to the newly introduced vCenter server resources. Accordingly, a cluster is treated as compute resource and named after it, placed in separate compute zone, also named after cluster.


CORE-17256Added an ability to delete a vCenter server from Control Panel.



Now you can change the owner of the vCenter resource pool.


CORE-17510Now you can view the activity logs at the vCenter servers view page.


CORE-17022Improved the process of vCenter integration.


CORE-17780Provided the ability to GET additional info relating to NSX Edges via API.




Release Notes

Affected Versions

CORE-14229The sidebar menu items were not aligned properly.6.1 Edge 1 - 6.3

CORE-15710After you clicked the Apply button at the Usage Statistics page, the page layout became distorted for a few seconds.6.2 - 6.3

CORE-17170The ImportvCloudToControlPanel transaction was shown as successful but contained an error.6.2 Patch 4 - 6.3 Edge 1

CORE-17291It was not possible to copy the CNAME URL from the DNS Settings section at the CDN Resource Details page. 6.2

CORE-17348Sliders in the Add new NSXEdge Resource pop-up window were not aligned properly.6.3

CORE-17389The IP Addresses icon at the Virtual Server Details page was not aligned properly. 6.3

CORE-17390If you tried to add events at the Edit Service Add-ons page, the + button did not respond to clicking. 6.3

CORE-17545The vCenter synchronization worked only for the first vCenter added to the Control Panel.6.4 Edge 1

CORE-17548It wasn't possible to create a federated VS in the Riverside and Dallas (US) locations.6.2 - 6.3

CORE-17575The connection with RabbitMQ was breaking periodically with the notification RabbitMQ is unavailable.6.0 - 6.3

CORE-17576The navigation buttons at the Add New CDN Resource page were misplaced.6.2 - 6.3

CORE-17578GET SDN nodes API request returned incomplete output. 6.0 - 6.3

CORE-17627The progressbar was shown incorrectly at the New vApp Template page while uploading '.ova' image file.  6.4 Edge 1

CORE-17631The rake task failed to clean all vCenter related entities from the Control Panel. 6.4 Edge 1


ProvisionVirtualServer transaction failed for the VS if you tried to build it with an ephemeral distributed port group created on the vCenter side and then synchronized with CP.

6.3 - 6.4 Edge 1

CORE-17662The 500 Internal Server Error appeared at All Templates page while trying to view the vCenter template list.

6.4 Edge 1

CORE-17692The networks were not syhchronized with all clusters in OnApp after creation of the port group on the vCenter.6.4 Edge 1

CORE-17693Data stores were not synchronized with all clusters in OnApp side after rake vcenter:resync task completion.6.4 Edge 1

CORE-17697The Statistics tab of the Dashboard displayed incorrect memory usage due to memory overcommitment.6.4 Edge 1

CORE-17705Compute resources assigned to a zone, which is not in a bucket, were listed in the New Resource Pool page dropdown.6.4 Edge 1

CORE-17715It was impossible to install/deinstall the attributes in system applications of the application server.6.3 - 6.4 Edge 1

CORE-17771After you reconfigured vCenter VS by removing/adding NIC or Disk via UI, the vcenter_cluster_id and vcenter_resource_pool_id values were incorrect.6.4 Edge 1

CORE-17772Trying to delete the default resource pool via API, you saw an unclear error message.6.4 Edge 1

CORE-17786The virtual server backups value was not shown correctly in the dropdown at the Disk Backup Images page, Storage tab.6.4 Edge 1

CORE-17793The warning message had the different length than the others at the Add a New Compute Zone page.6.3 Stable


There was an incorrect value at the Target column for the vCenter server deletion at the Activity log.

6.4 Edge 1

CORE-17804Notification with wrong text appeared at the New vCenter Server page after you did not fill IP address/Hostname filed.  6.4 Edge 1

CORE-17808The magnifying glass icon did not display properly at the Global Search page.6.4 Edge 1 

CORE-17840 Datastore and network labels were reset from custom to default after rake vcenter:resync task execution.6.4 Edge 1

CORE-17841The dropdown at the Edit Network Zone page did not contain correct data center.6.4 Edge 1

CORE-17851After clicking Change Owner button for the vCenter resource pool, you were redirected to the wrong page.6.4 Edge 1

CORE-17857The chart of CPU usage for the vCenter virtual server showed CPU cores instead of CPU percentage.6.3 - 6.4 Edge 1

CORE-17873The rake vcloud:link_vms_to_vcente task failed with an error.6.3 - 6.4 Edge 1

CORE-17881It was impossible to attach Veem backup resource to the vCenter virtual server.6.4 Edge 1

WIZ-23The Infrastructure mode slider in the vCenter Beta VS Creation wizard was misplaced, and the redundant Encrypt Password slider was displayed at the Properties step with the Infrastructure mode enabled.6.3 Edge 2
WIZ-24It was impossible to pick if a new vCenter virtual server should be built on the custom resources or instance packages at the Properties page.6.3 Edge 2