Virtuozzo Application Platform 5.6.1/2
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.6.1 / 2 releases.
Multi-Region Deploy of Packaged Applications
An ability to receive and work with multiple environment regions in the JPS packagesLearn more
Custom IPv6 Firewall Rules
Implemented possibility to provide custom IPv6 firewall rules for the containersLearn more
GitLab Deploy Tokens Support
Changed validation on the VCS deployment form to support logins generated by GitLab for deploy tokensLearn more
Data Sharing: Export Config Validation
Automatic validation of the export file when sharing data with the external NFS storageLearn more
Container Redeploy with Automatic Backups and Rollback on Failure
Improved reliability of the redeployment process through creating container backups and implementing automatic rollback on failureLearn more
API Improvements
- optional parameter for the AddMountPointById and AddMountPointByGroup methods to mount data by IP address
- detailed error description upon the BindSSL API method failure
Installation Package with Limited Resources
Listing resources on the package installation frame, which will be downscaled due to insufficient account quotasLearn more
UI/UX Improvements
- renovated functional icons for the dashboard
- simplified environment group selection flow
- restyled button for automatic custom SSL dependencies appliance
Extended Description for the Unreachable NFS Error
The unreachable NFS error was supplemented with the Server IP and Client IP detailsLearn more
Software Stack Versions
Actualized list of supported OS templates and software stack versionsLearn more
Bug Fixes
List of fixes applied to the platform starting from the current releaseLearn more
Multi-Region Deploy of Packaged Applications
In the current 5.6 PaaS release, the regionlist field was provided with a possibility to select multiple environment regions, when preconfiguring a package installation. The following new optional parameters were added to support such integration:
- multiSelect - allows selecting multiple regions (false by default)
- min - sets the minimum number of regions required for the package installation (0 by default)
- max - sets the maximum number of regions required for the package installation
- required - makes the field obligatory for the provisioning (false by default)
- delimiter - defines a delimiter for the multi-select (, by default)
With such an improvement, it is possible to automate installations across multiple regions in a single package. For example, you can prepare a solution, which will create instances of your application in different regions, negating risks of unavailability.
Container Redeploy with Automatic Backups and Rollback on Failure
Container redeploy is a powerful tool to keep your software solutions up to date. Howerer, there are always risks of your application or some specific configs incompatibility with the new container version. As a result, your project can become partially or entirely unavailable till the problem is resolved.
Aiming to eliminate even such a slight possibility, the platform developed a new algorithm for containers redeploy with the main innovation of creating a backup. In such a way, if an error occurs during container update, the platform automatically and painlessly restores node’s previous version, displaying the appropriate action in the dashboard task manager.
Here are some other specifics of the implementation:
- you are not charged for the redeployment backups created by the platform
- failure during the sequential redeployment interrupts the process so that it won’t be initiated on the remaining containers; the appropriate warning will be shown in the dashboard
- if faced some problems after successful redeploy, contact your service hosting provider support team to restore the previously used container version (usually, only the latest redeploy operation can be reverted)
Custom IPv6 Firewall Rules
Most of the firewall configurations can be performed via the dedicated user interface, which allows configuring the inbound and outbound rules. Herewith, for more flexible management (for example, to configure NAT redirects), you can set custom firewall rules for your container.
In the current 5.6 platform release, the possibility to create custom rules for the IPv6 connects was implemented. Similarly to the flow implemented for IPv4, you need to define the required rules in the dedicated /etc/sysconfig/ip6tables-custom file (using the iptables-save tool format) and apply changes with the sudo /usr/bin/jem firewall fwstart command.
[Back to the top](#back)
API Improvements
Adding Mount Point by IP Address
To support various project requirements, the platform implemented a possibility to add mount points via IP address instead of the domain name. The appropriate AddMountPointById and AddMountPointByGroup API methods were supplemented with the optional sourceAddressType parameter, which can be set as either DOMAIN (by default) or IP. The first option corresponds to the mount point binding by the domain name, while the second one - by IP address. Additionally, for the convenience of these methods usage, the protocol parameter was redefined as optional one and set to NFS by default.
Also, the GetMountPoints method was adjusted to return the appropriate sourceAddressType value in the response.
Back to the list of API Improvements
BindSSL Error Response Clarification
The BindSSL API method allows securing connection to an environment with a custom SSL certificate. As the task is not trivial, in the current PaaS 5.6 upgrade, the error response was provided with the additional clarification details to simplify the debugging process for developers. For now, if a problem with custom SSL certificate addition occurs, the root cause can be discovered much quicker, and the whole issue resolved faster.
Back to the list of API Improvements
GitLab Deploy Tokens Support
The validation of the Login field in the deployment form was adjusted to provide the support of the Gitlab deploy tokens and allow quick and simple deployment from the repository without the necessity to configure authentication based on SSH key. Namely, the “+” and “-” special symbols, which are used in the generated by GitLab tokens (e.g. gitlab+deploy-token-1), were allowed.
Data Sharing: Export Config Validation
The platform allows you to share data between containers by exporting it on one node and mounting on the other using the NFS protocol. Herewith, if files should be exported to the external server, the appropriate /etc/exports configuration file should be manually adjusted. The automatic validation of the file content was implemented in the 5.6 platform upgrade to simplify the process for you. Namely, the duplicated records and the lines without options are commented by during a new export addition/removal. Also, the backup file of the original exports configurations is saved in the same /etc folder with the .backup-{date} extension.
Installation Packages with Limited Resources
The platform allows to proceed with the package installation (for example, from Marketplace or imported form JPS Collection) even if some of the account limits are lower than the ones stated in the manifest. Herewith, the appropriate notification is displayed on the installation frame:
Starting with the current 5.6 platform release, you can proceed with installation even if the package requires Built-In SSL, which is not available for your account. Also, all of the cut resources are listed explicitly within the warning message at the bottom of the install confirmation frame.
In case any of the package requirements cannot be downscaled to match resources available for your account, the appropriate button to contact support is displayed (or the Upgrade now one for trial users).
UI/UX Improvements
- Dashboard Functional Icons Renovation
- Microservices Packages in Marketplace
- Environment Groups Selection
- Custom SSL Dependencies Configuration
Dashboard Functional Icons Renovation
Platform dashboard is a powerful GUI panel for the environments hosting and management. It provides access to the main functionality of the platform, allowing to comfortably manage all the aspects of your application lifecycle directly in the browser without the necessity of additional software installation. The most common operations are available through the context menu (displayed upon hovering over the environment, layer or node), where each element is presented in the form of the appropriate functional icon.
In the present 5.6 PaaS release, these icons were restyled making them larger and more distinguishable.
Back to the list of UI/UX Improvements
Microservice Packages in Marketplace
The platform provides numerous pre-packaged solutions based on the microservices architecture, which are globally available via the Marketplace. In the present 5.6 platform release, the new Microservices section was added to the platform Marketplace to group all of the relevant solutions (for example, Spring Boot Fat/Thin Jar Builder, Vert.x Fat/Thin Jar Builder, Docker Swarm Cluster).
Back to the list of UI/UX Improvements
Environment Groups Selection
Environment groups functionality allows organizing projects within your dashboard. Herewith, often you need to assign environment to just a single group, so, for now, the list is automatically collapsed after selecting an option. To choose multiple groups straight away, click on the required items while holding the Ctrl or Cmd key on the dashboard (the appropriate tip was added at the bottom of the form).
Back to the list of UI/UX Improvements
Custom SSL Dependencies Configuration
To secure an application with custom SSL, you need to correctly configure your environment topology and attach the appropriate custom domain (the one SSL certificate is issued for). The platform can automatically fulfill the topology requirements by including the certified application server or load balancer with the attached public IP. Just access the SSL section in the wizard and click the Enable button (is hidden if no reconfiguration is required).
In the present PaaS release, this button was visually upgraded to match the latest dashboard style. Also, the appropriate hint in the environment settings about custom SSL usage was updated as well.
Back to the list of UI/UX Improvements
Extended Description for the Unreachable NFS Error
The “Destination NFS server is not reachable” error was supplemented with the additional details to simplify analysis of the NFS related issues (i.e. with mount points and data export). Namely, the information on the target Server IP and the source Client IP was added to the response, allowing jump immediately into the investigation.
Software Stack Versions
Check out the list of the most accurate software stacks for the current platform version:
| Stack | PaaS 5.6.1 / 2 |
|---|---|
| Apache Balancer | 2.4.37 |
| Apache PHP | 2.4.37 |
| Apache Python | 2.4.37 |
| Apache Ruby | 2.4.37 |
| CentOS (VPS) | 6.8; 7.2 |
| Couchbase CE | 5.1.1; 6.0.0 |
| CouchDB | 1.6.1 |
| Docker Engine CE | 17.12; 18.09 |
| GlassFish | 3.1.2.2; 4.1.2; 5.0 |
| Golang | 1.11.4 |
| HAProxy | 1.8.14 |
| IIS | 8 |
| Jetty | 9.4.12 |
| MariaDB | 5.5.62; 10.3.12 |
| Maven | 3.6.0 |
| Memcached | 1.5.12 |
| MongoDB | 2.6.12; 3.6.8; 4.0.2 |
| MSSQL | 2012 |
| MySQL CE | 5.7.24; 8.0.13 |
| NGINX Balancer | 1.14.2 |
| NGINX PHP | 1.14.2 |
| NGINX Ruby | 1.14.2 |
| NodeJS | 6.16.0; 8.15.0; 9.11.2; 10.15.0; 11.6.0 |
| Payara | 4.1.2.181; 5.184 |
| PerconaDB | 5.6 |
| PostgreSQL | 9.6.11; 10.6; 11.1 |
| Redis | 4.0.11; 5.0.3 |
| Spring Boot | 2 |
| Tomcat | 7.0.92; 8.5.37; 9.0.14 |
| TomEE | 7.1.0 |
| Ubuntu (VPS) | 16.04 |
| Varnish | 4.1.8; 5.2.1; 6.1.1 |
| WildFly 10 | 10.1.0; 11.0.0; 12.0.0; 13.0.0; 14.0.1; 15.0.0 |
| Windows (VPS) | 2012 |
| Engine | # |
|---|---|
| JDK | 6.0_45; 7.0_79; 8.0_201; 9.0.4; 10.0.2; 11.0.1 |
| Open JDK | 7.0_201; 8.0_191; 10.0.2; 11.0.1; 12.ea-b28; 13.ea-b4 |
| OpenJ9 | 0.9.0-8u181-b13; 0.9.0-9.0.4.12; 0.9.0-10.0.2; 0.11.0-8u192-b12; 0.11.0-11.0.1 |
| PHP 5 | 5.3.29; 5.4.45; 5.5.38; 5.6.40 |
| PHP 7 | 7.0.33; 7.1.26; 7.2.14; 7.3.1 |
| Ruby | 2.2.10; 2.3.8; 2.4.5; 2.5.3; 2.6.0 |
| Python 2 | 2.7.15 |
| Python 3 | 3.4.9; 3.5.6; 3.6.7; 3.7.1 |
| Node.js | 6.16.0; 8.15.0; 9.11.2; 10.15.0; 11.6.0 |
| .NET | 4 |
| Go | 1.11.4 |
Bug Fixes
In the tables below, you can see the list of bug fixes applied to the platform starting from PaaS 5.6.1 / 2 releases:
| PaaS 5.6.1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PaaS 5.6.2 | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
