Virtuozzo Application Platform 5.8.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.8.2 release.

Container Types in Wizard

PaaS is an extremely versatile platform that supports multiple solutions for application development and hosting that will suit even the most demanding clients. However, it may not be obvious (especially for the new customers) which deployment options are available on the platform, so a dedicated list with explanations was added to the topology wizard.

By default, the wizard provides a categorized list of platform-managed stacks (the ones in the Java, PHP, Ruby, etc. tabs) that are already pre-configured and optimized for you in the most beneficial way. Additionally, such managed containers are fully compatible with the platform functionality (scaling, automated deployment, redeployment, SSL, etc.).

In case of switching to the Docker tab, you can review other deployment options available on the platform. Herewith, all the variants listed below are utilizing the basic system container, which makes them compatible with most of the platform-distinguishing features (e.g. vertical and horizontal scaling):

• Custom Docker Containers - any Docker image (based on the supported OS) deployed into the system container, which provides access to a great variety of solutions. However, the software operability and compatibility with the platform cannot be guaranteed (as the content is managed by respective image maintainers).
• Docker Engine - a Docker Engine CE deployed into the system container. It provides access to all the Docker native functionality, including deployment, scaling, and management of multiple application containers inside.
• Kubernetes Cluster - ready-to-go Kubernetes cluster with preconfigured master and worker nodes created based on the system containers. Microservices deployment, scaling, and orchestration are handled by Kubernetes control units, while the platform manages control plane and worker nodes as a whole.

More info

Back to the top

Tasks Panel Amendments

A new Tasks panel, that was introduced in the previous release, obtained additional tuning for better user experience:

• In order to provide better clarity, the Copy and Send Report buttons were moved to the left part of the panel. Also, they will be displayed only upon hovering over the appropriate Params and Response sections.
• A new Copy error text button was added to get an error without the necessity to expand the corresponding task.
• The Params section was extended with a complete list of parameters used in the request (instead of just the main ones). Herewith, all the sensitive data (passwords, tokens, SSH keys, etc.) is automatically masked for security reasons.
• An internal actionkey parameter was removed from the tasks' response.
• Automatic sorting of the fields in the Params and Response sections was implemented. Herewith, the result and error (if present) responses are always displayed first.
• An ability to expand on-going tasks was added to get additional details on the action immediately after the start.

More info

Back to the top

Container Reboot via SSH

In the present 5.8.2 PaaS release, the ability to reboot a server via SSH without additional permissions was implemented. Such an operation may be required in case of some major issue on the container, which cannot be resolved via service restart, e.g. the jem service restart command hangs. For now, it is possible to reboot the whole operating system of the container via the following new commands:

1

reboot

or

1

/usr/sbin/reboot

With such an improvement, it’s no longer necessary to stop-start the whole environment so that only a problematic container will be affected by the reboot.

Back to the top

Isolation Timeout

Network Isolation is an important feature of the platform that allows managing groups of environments separately (by denying unintended connections via the internal network). Usually, all the isolation operations, such as group creation, nodes addition/removal, etc., are quick and need just a few seconds. However, in some cases (high platform load, network issues), these processes can require more time than the 30 seconds reserved by default. Thus, in the current 5.8.2 release, the timeout for isolation operations was increased to one minute.

More info

Back to the top

API Changes

Below, you can find a list of all changes to the public API in the 5.8.2 platform version (compared to the preceding 5.8 ones):

• added two optional parameters for the stopEvent action to provide notification after the event interruption:
  • type - the notification type based on the specified value: success (the default behavior without notification), info/warning/error (pop-up style as described in the CS documentation)
  • message - a text that should be displayed in the pop-up (if not specified, the default notification is provided)
• improved the domains parameter description for the AddDomains method
• the actionkey parameter became optional for the ChangeTopology method

More info

Back to the top

Fixes Compatible with Prior Versions

Below, you can find the fixes that were implemented in PaaS 5.8.2 release and also integrated into previous platform versions by means of the appropriate patches.

Back to the top

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.

More info

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.8.2 release:

Back to the top