Chapter 6. RHSA-2013:0888 — Red Hat Enterprise Virtualization Manager

Certain GWT application resources did not have the appropriate caching headers applied due to Apache or JBoss configuration issues. Consequently, the browser could not cache resources that rarely (if ever) changed, and had to request them from the server each time the page was loaded. The proper caching policy is now defined in both the Apache and JBoss configuration, so the browser can properly cache the necessary resources, which results in fewer requests to the server.

The validation of virtual machine memory size used an obsolete value, so users could not assign more than 256 GB memory to a virtual machine. The validation now uses the supported value of 2 TB. Users can assign maximum 2 TB memory for 64-bit virtual machines.

The columns for the tabs in the details pane can now be resized, so all information displays as required.

A new Disks tab has been added under the Storage resource tab. This tab lists the disks associated with each storage domain, and simplifies disk management operations such as storage domain detachment.

Support has been added for extending the administration portal user interface with custom plugins. This includes a dedicated API for discovering and loading plugins, and providing notification of the plugin's key events to the administration portal.

Previously, the snapshot creation dates displayed wrongly in the administration portal. This has been fixed, so the snapshot creation dates are correctly synced between the REST API and the administration portal.

Previously, when a user tried to remove a host which contained bricks of one or more gluster volumes, or all the Hosts in the cluster are in maintenance mode(or not up), the 'Host Remove' operation will fail with an error.
This has been fixed by adding a 'Force Remove' to the 'Remove Host' confirmation dialog. This enables the user to  remove the hosts even if the host contains bricks or is in non-responsive state. The corresponding brick entries will also be removed while removing the host. The 'Gluster Peer Detach Force' command will also be executed in one of the UP Hosts of the cluster.

When a gluster volume is started or stopped from the CLI, the Manager detects this change, updates the database, and creates an event log. However, the event log message remained static, that is, it was not printing the names of the cluster and volume which were started/stopped. This meant that the audit log message was not very useful for the user, as it didn't show the names of the affected entities.
The audit log message now includes names of the cluster and volume, making it more informative and useful.

Previously, there was no simple way to copy messages from the Events tabs to the client's clipboard. Now, from the Events tab users can double click an event to invoke an Event Details window, which allows users to copy messages using the Ctrl+C key combination or by right-clicking and selecting the text.

Support has been added for importing existing Gluster supported clusters to the Manager. When all hosts in the cluster are imported, and the bootstrap script installs all necessary VDSM packages on the hosts.

The Cluster tab did not display the cluster CPU type, a user had to edit a cluster to get this information. A new column has been added to the Cluster tab which now displays the CPU type of the cluster.

The Volumes tab is now visible in the resource tabs. Users can create and manage volumes using this tab, and search for volumes using Search bar.

Users can now invoke a virtual machine console without requiring an installed browser plugin. Instead of using the plugin, the engine provides a file containing connection information that can be registered and opened by a console client application installed on the client's system. 

This feature can be configured using the ClientConsoleMode option set by engine-config: 
* If the option is set to Plugin (the default option), the browser plugin is used.
* If the option is set to Native, the invocation via a browser plugin is disabled.
* If the option is set to Auto, the browser plugin is used if it is installed, otherwise the console client application is used.

Previously any edits made to configuration settings in the  'edit console' dialog had to be re-entered when operating in a browser. This meant double entry of configuration settings for users. A new feature  ensures that any changes made to configuration settings in the edit console are persisted through to the browser, meaning that the changes to the configuration settings only have to be entered once.

The data center name for each cluster now displays in the results list for the Clusters resource tab.

Previously If the SPICE proxy was globally enabled, the user may have needed to turn this off per Virtual Machine to connect directly. An option has been added to the 'Edit Console Dialog' to turn off the globally configured SPICE proxy. This option only turns it off only for the current browser, other clients using the same Virtual Machine may still use the proxy.

Due to an RPC serialization error caused by the 'final' keyword in the 'diskList' field, the engine could not remove auto-generated snapshots created as part of the live storage migration operation. The 'final' keyword has been removed, so auto-generated snapshots can now be removed.

English was defined as the default locale, which worked if the browser's locale was English, but users with a browser locale other than English were unable to select the English locale. Now, English is defined as a fallback, so users in all locales can select English regardless of their default locale.

The correlation ID of local storage creation flow was mistakenly translated in non-English locales, so local storage could not be created on non-English locales. The correlation ID is no longer translated, as a result local storage creation works as expected.

Tool-tips now appear when you hover your mouse over a column header which cannot display the entire text due to space limitations.

The Navigation Tree in the Management graphical user interface (GUI) was erroneously labeled  'Tree'. This has now been changed to 'System'.

When in tree view, clicking 'expand all' would expand the entire tree and not just the nodes under the selected node. This was not the expected behaviour.  This has been changed so that  when 'expand all' is now clicked, only the nodes under the selected node are expanded, and the other unselected nodes remain untouched.

Incorrect usage of the GWT EditorDriver framework caused obsolete information to be shown in the Virtual Machines or Templates General tab. The static EditorDriver usage has been replaced with instance-specific usage, so the Virtual Machines and Templates General tabs now show accurate and updated information.

The ability to mount an ISO from a Windows SPICE client was removed from version 3.1, but it has been restored to version 3.2.