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.
Highlights
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
| Type | Key | Release Notes |
|---|---|---|
| OnApp Cloud | ||
| CORE-16462 | Now 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-17513 | Added the ability to clone a default role to a new user. | |
| CORE-10822 | Improved the charts for instant and hourly CPU utilization. | |
| CORE-12469 | Updated the design for the 500 Server Error landing page. | |
| CORE-12470 | Updated the design for the 404 Not Found page. | |
| CORE-13654 | Now you can set the value for RabbitMQ continuation timeouts. | |
| CORE-15356 | Improved the appearance of Features at the Compute Resources page. | |
| CORE-16636 | Now you can use one of the default OnApp roles as a template to create a new custom role. | |
CORE-16940 CORE-16941 CORE-16942 CORE-16943 CORE-17268 | 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-17324 | Now you can start the virtual server with the compute resource having more than 240 vCPUs. | |
| CORE-17606 | Improved OnApp daemon to accelerate auto-backup jobs processing. | |
| CORE-17702 | Improved the color of the placeholder and inputted texts. | |
vCenter and vCloud | ||
| CORE-15703 | Now you can import your vSphere Standard Switches (VSS) from vCenter to OnApp, and use OnApp for vCenter with basic licensing. | |
| CORE-16648 | Now you can use the vCenter resource pools to delegate control over the resources of a host (or a cluster). | |
| CORE-17158 | Now 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-17256 | Added an ability to delete a vCenter server from Control Panel. | |
CORE-17338 | Now you can change the owner of the vCenter resource pool. | |
| CORE-17510 | Now you can view the activity logs at the vCenter servers view page. | |
| CORE-17022 | Improved the process of vCenter integration. | |
| CORE-17780 | Provided the ability to GET additional info relating to NSX Edges via API. | |
Fixes
Type | Key | Release Notes | Affected Versions |
|---|---|---|---|
| CORE-14229 | The sidebar menu items were not aligned properly. | 6.1 Edge 1 - 6.3 |
| CORE-15710 | After you clicked the Apply button at the Usage Statistics page, the page layout became distorted for a few seconds. | 6.2 - 6.3 |
| CORE-17170 | The ImportvCloudToControlPanel transaction was shown as successful but contained an error. | 6.2 Patch 4 - 6.3 Edge 1 |
| CORE-17291 | It was not possible to copy the CNAME URL from the DNS Settings section at the CDN Resource Details page. | 6.2 |
| CORE-17348 | Sliders in the Add new NSXEdge Resource pop-up window were not aligned properly. | 6.3 |
| CORE-17389 | The IP Addresses icon at the Virtual Server Details page was not aligned properly. | 6.3 |
| CORE-17390 | If you tried to add events at the Edit Service Add-ons page, the + button did not respond to clicking. | 6.3 |
| CORE-17545 | The vCenter synchronization worked only for the first vCenter added to the Control Panel. | 6.4 Edge 1 |
| CORE-17548 | It wasn't possible to create a federated VS in the Riverside and Dallas (US) locations. | 6.2 - 6.3 |
| CORE-17575 | The connection with RabbitMQ was breaking periodically with the notification RabbitMQ is unavailable. | 6.0 - 6.3 |
| CORE-17576 | The navigation buttons at the Add New CDN Resource page were misplaced. | 6.2 - 6.3 |
| CORE-17578 | GET SDN nodes API request returned incomplete output. | 6.0 - 6.3 |
| CORE-17627 | The progressbar was shown incorrectly at the New vApp Template page while uploading '.ova' image file. | 6.4 Edge 1 |
| CORE-17631 | The rake task failed to clean all vCenter related entities from the Control Panel. | 6.4 Edge 1 |
| CORE-17652 | 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-17662 | The 500 Internal Server Error appeared at All Templates page while trying to view the vCenter template list. | 6.4 Edge 1 |
| CORE-17692 | The networks were not syhchronized with all clusters in OnApp after creation of the port group on the vCenter. | 6.4 Edge 1 |
| CORE-17693 | Data stores were not synchronized with all clusters in OnApp side after rake vcenter:resync task completion. | 6.4 Edge 1 |
| CORE-17697 | The Statistics tab of the Dashboard displayed incorrect memory usage due to memory overcommitment. | 6.4 Edge 1 |
| CORE-17705 | Compute 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-17715 | It was impossible to install/deinstall the attributes in system applications of the application server. | 6.3 - 6.4 Edge 1 |
| CORE-17771 | After 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-17772 | Trying to delete the default resource pool via API, you saw an unclear error message. | 6.4 Edge 1 |
| CORE-17786 | The virtual server backups value was not shown correctly in the dropdown at the Disk Backup Images page, Storage tab. | 6.4 Edge 1 |
| CORE-17793 | The warning message had the different length than the others at the Add a New Compute Zone page. | 6.3 Stable |
| CORE-17796 | There was an incorrect value at the Target column for the vCenter server deletion at the Activity log. | 6.4 Edge 1 |
| CORE-17804 | Notification with wrong text appeared at the New vCenter Server page after you did not fill IP address/Hostname filed. | 6.4 Edge 1 |
| CORE-17808 | The 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-17841 | The dropdown at the Edit Network Zone page did not contain correct data center. | 6.4 Edge 1 |
| CORE-17851 | After clicking Change Owner button for the vCenter resource pool, you were redirected to the wrong page. | 6.4 Edge 1 |
| CORE-17857 | The chart of CPU usage for the vCenter virtual server showed CPU cores instead of CPU percentage. | 6.3 - 6.4 Edge 1 |
| CORE-17873 | The rake vcloud:link_vms_to_vcente task failed with an error. | 6.3 - 6.4 Edge 1 |
| CORE-17881 | It was impossible to attach Veem backup resource to the vCenter virtual server. | 6.4 Edge 1 |
| WIZ-23 | The 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-24 | It 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 |