Virtuozzo Application Platform 5.4.5/6/7

This document is preliminary and subject to change.

In this document, you will find all of the new features, enhancements and visible changes included to the PaaS 5.4.5/6/7 releases.

Container Provisioning Optimization

Within the current 5.4.5 PaaS release, a noticeable optimization was applied to the custom Docker container and certified dockerized templates creation process through refactoring and updating the platform internal scripts. The general performance boost is around 20%, with even greater results upon consecutive installation of the same image.

Back to the top

UI/UX Improvements

Starting with the PaaS 5.4.5 release, some visual updates were applied to the dashboard to provide the latest and most accurate icons for elements and stacks, improving their recognition:

• the environment Settings tab was provided with the wrench-style icon (the same one as on the appropriate Settings button)
• the Golang application server logo was replaced with its latest official design
• a dashboard icon for the Maven build node was renewed, and the outdated hint for the Maven template in topology wizard was removed

More info

Back to the top

Performance Improvements

• Environment List Lazy Loading
• Web SSH Optimization

  Back to the top

Environment List Lazy Loading

When hosting multiple environments, you can notice a slight slowdown of the environments > Control > GetEnvs API method. Such a delay is caused by the necessity to load all data for each environment. But usually you need to manage no more than just a few environments at a time.

So, within the PaaS 5.4.5 release, only the main environment metadata (e.g. name, alias, domain, etc.) can be loaded by setting a new optional lazy parameter as true. The complete info on a particular environment will be provided on demand, i.e. upon usage of the GetEnvInfo request. Also, using this improvement, the platform was able to notably speed up the first connection to SSH Gate.

Back to the list of Performance Improvements

Web SSH Optimization

With the current platform upgrade, some polishing was applied to the recently implemented Web SSH feature. As a result, the general performance and reliability of the web client was improved. Also, in order to provide better user experience, an automatic section focus was implemented. Namely, when you switch to the Web SSH tab in the dashboard, it will be automatically set as active, allowing to start typing commands immediately (i.e. without necessity to additionally click on the area within the section).

Back to the list of Performance Improvements

Deploying Application via SSH

The platform-specific deployment, which allows to automatically install application archive into environment compute node(s), was adjusted to be run under the jelastic user. With such implementation, it’s possible to call deploy action directly via SSH console by running the following command:

1

jem compute deploy -a  {atomicDeploy} -c  {context} -u {packageUrl}

where:

• {atomicDeploy} - allows to either enable (true) or disable (false) a zero downtime deployment mode for PHP
• {context} - sets a context name for the project
• {packageUrl} - provides link to the application archive to be deployed

  Back to the top

Domain Names for Node Group Layer

Starting with the 5.4.5 version, all new environments are provisioned with a dedicated hostname for a particular node layer:

${nodeGroup}.${envName}.${platformDomain}

where:

• ${nodeGroup} - denomination of the layer (e.g. cp, bl, storage, etc.)
• ${envName} - environment name (not an alias)
• ${platformDomain} - domain name of a hosting service provider
  Tip: While working inside the environment and referring to itself, just a short hostname (${nodeGroup}) can be used.

Each time a new container is created (or removed) a list of records for the appropriate layer is automatically updated.

More info

Back to the top

All Nodes Restart for Clusterized Solutions

Previously, only master node was restarted in the cluster. Starting with the PaaS 5.4.5 release, this flow was ceased for the platform-managed dockerized templates, allowing to call restart for all nodes or for specific one in the layer. And in order to keep the backward compatibility, this change was not applied to the platform certified templates (e.g. GlassFish).

Back to the top

Decreasing Delay for Logs Display

While viewing a log file, the platform allows to automatically update a displayed content (the Tail mode) to keep you up-to-date with the ongoing operations. Rarely, in case of a great amount of logged data, it can temporarily fall behind of the actual actions occurred on the node. So, in the current platform release, a number of new lines, which can be displayed per update (i.e. every 3 seconds) was increased from 249 up to 999. This change helps to be always provided with the most recent data in log files.

More info

Back to the top

Favourites.conf File Alias for JPS Packages

While setting up a JPS package, you can manually define a default list of folders and files that will be displayed as Favorites for your instances in the configuration file manager. For this, you need to adjust the appropriate /etc/jelastic/favourites.conf file in the following format:

1
2
3
4

[directories]  
{directories_list}  
[files]  
{files_list}

For example, the next command can be used:

1

cmd [cp]: echo -e "[directories]\n/home" >/etc/jelastic/favourites.conf

Starting with the PaaS 5.4.5 release, an alternative /etc/jelastic/favorites.conf name can be used for this file. Herewith, if both favorites.conf and favourites.conf configs are provided, only the latter one will be considered.

More info

Back to the top

Software Stack Versions

Check out the list of the most accurate software stacks for the current platform version:

Back to the top

Bug Fixes

In the table below, you can see the list of bug fixes applied to the platform starting from PaaS 5.4.5/6/7 releases:

Back to the top