Virtuozzo Application Platform 5.9
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.9 release.
Restrict Node Access via Shared Load Balancer (SLB)
Added ability to close external access to nodes via Shared Load BalancerLearn more
Ability to Remove Any Container
Advanced nodes management during horizontal scalingLearn more
Ubuntu 20.04 OS Template Support
Implemented support for the containers based on the Ubuntu 20.04 OS templateLearn more
API Changes
Listed all the changes to the public platform API in the current releaseLearn more
Software Stack Versions
Actualized list of supported OS templates and software stack versionsLearn more
Fixes Compatible with Prior Versions
Bug fixes implemented in the current release and integrated to the previous platform versions through the appropriate patchesLearn more
Bug Fixes
List of fixes applied to the platform starting from the current releaseLearn more
Restrict Node Access via Shared Load Balancer (SLB)
Each node at the platform can be accessed immediately after its creation without any additional configurations via its unique hostname. The connection is ensured with the help of the Shared Load Balancer - an NGINX resolver for the whole platform. Although beneficial in most cases, such access may not be needed in some specific scenarios. For example, you may want to close public access to nodes intended for internal access only (e.g. databases) or forbid direct access via SLB to nodes with public IP address attached and custom domain configured.
In order to fulfill such a need, an option to control Access via SLB was implemented. It is located in the topology wizard and can be configured for each layer separately.
The option is enabled by default, which ensures the same behavior as before the PaaS 5.9 upgrade - nodes are accessible from the SLB via environment domain names using the default ports (80, 8080, 8686, 8443, 4848, 4949, 7979). If disabled, the nodes within the layer are inaccessible via SLB (including the Open in Browser button in the dashboard) and return the 403 Forbidden error instead of the intended service. Herewith, access via SSH and through endpoints is not affected.
In general, we recommend to use the Access via SLB option for your development and testing environments and disable it for the application in production (use public IP with custom domain instead).
Ability to Remove Any Container
By default, the platform provides a simplified nodes management, where you just need to specify the required number of containers in a layer. However, in some cases, you may want to remove a specific container instead of deleting the most recent one. Such a possibility was implemented in the current 5.9 PaaS release, allowing to manage nodes via:
the Horizontal Scaling section in topology wizard - accessible using the Change Environment Topology button next to the required environment
the dedicated Scaling Nodes form in the dashboard - accessible using the Additionally > Scaling Nodes option next to the layer or Additionally > Delete next to the particular node
It is possible to add new nodes and remove any particular container (except the initial “master” one) using these forms. Also, the confirmation form when applying changes to the environment was extended with notification about nodes to be removed and recommendations to back up any crucial data from these containers.
Ubuntu 20.04 OS Template Support
The support of the custom Docker images based on the Ubuntu 20.04 OS template was implemented for all the PaaS installations regardless of their current version. It is an LTS (long term support) release that will be maintained for five years. Compared to the preceding LTS version (18.04), it offers an updated kernel, optimized security and performance, as well as several new features (e.g. native ExFAT support, X11 fractional scaling, etc.). For more information on Ubuntu 20.04, refer to the official release notes.
API Changes
Below, you can find a list of all changes to the public API in the 5.9 platform version (compared to the preceding 5.8.2 ones):
- added a new SetSLBAccessEnabled method to the environment.Control service to support the Access via SLB feature implementation
Fixes Compatible with Prior Versions
Below, you can find the fixes that were implemented in the PaaS 5.9 release and also integrated into previous platform versions by means of the appropriate patches.
| PaaS 5.9 | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
Software Stack Versions
The software stack provisioning process is independent of the platform release, which allows new software solutions to be delivered as soon as they are ready. Herewith, due to the necessity to adapt and test new stack versions, there is a small delay between software release by its respective upstream maintainer and integration into the platform.
The most accurate and up-to-date list of the certified software stack versions can be found on the dedicated documentation page.
Bug Fixes
In the table below, you can see the list of bug fixes applied to the platform starting from PaaS 5.9 release:
| PaaS 5.9 | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
