As part of the autoscaling feature, the control tab has been improved. The Task schedules tab has been replaced with the Triggers tab, which is at the virtual appliance level.
In Abiquo 4.0, there are changes to the main virtual machine icon, which is now larger to accommodate the scaling group functionality. Abiquo has added new symbols to the virtual machine icon for scaling groups, and for backups enabled on the virtual machine. In the image, you can see the symbols for Virtual machine error, Chef virtual machine and VM with backup.
If the virtual machine were persistent, the persistent symbol would be shown in the second slot.
There have been several changes to branding in Abiquo 4.0 to simplify configuration and improve upgrades.
The most important changes affect the CSS files. Each Abiquo theme now has only one CSS file called theme.css that contains all CSS elements. And you can brand the WMKS vCloud Director remote access web console with the theme_wmks.css file, in addition to noVNC with the theme_novnc.css file.
The basic steps to upgrade branding are as follows:
Create a main theme.css file and copy inside it the content of theme_unsecured.css and theme_secured.css in that order
Set the new theme.css as the default theme. The default theme configuration will persist after Abiquo upgrades
Create enterprise theme.css files for individual tenants by renaming the theme_secured.css files to theme.css
Abiquo 4.0 also supports a persistent name for the client window, using the new client.window.title property in the custom client configuration file.
The version of noVNC incorporated into Abiquo has been upgraded for Abiquo v4.0. As in previous versions, you can brand the noVNC interface.
After every Abiquo upgrade, users must refresh their browser cache to work with the latest version of the Abiquo user interface. Abiquo v4.0 checks the version of key user interface files and enforces the clearing of the cache if necessary.