The Virtuozzo Application Management provides exceptionally detailed and granular information on all the consumed resources to ensure fair pricing. The platform’s database stores hourly data for every resource of each user, which can become a huge number of records over time. At a certain point, the performance of requests to this table can be affected. To avoid billing history performance degradation, an additional database with aggregated daily records for the most recent data was added. Such an aggregated database is enough to satisfy the most common billing history requests, while operating significantly faster (due to the smaller number of records) and decreasing load on the regular database with hourly data.
Some specifics of the implementation:
The new database does not provide access to the current day’s data.
If the current day is included in the request, data will be obtained from both databases (today’s data from regular/hourly and the rest from aggregated/daily). Such an approach is comparatively faster than using just the regular database.
All hourly requests will go to the regular database (no granularity loss).
In order to prevent problems during project deployment or update, the node restart and redeploy options are automatically locked in the dashboard. The improvement ensures that the application deployment process is finished before allowing further management, which reduces the risks of unintentional interruption.
Below, you can find a list of all changes to the public API in the 8.10 platform version (compared to the preceding 8.8 ones):
Removed the envName parameter from the GetGroups, CreateGroup, EditGroup, and RemoveGroup methods in the group service. The default appid parameter is now used for authentication.
Below, you can find the fixes that were implemented in the Virtuozzo Application Management 8.10 release and also integrated into previous platform versions by means of the appropriate patches.
Virtuozzo Application Management 8.10
#
Compatible from
Description
JE-67639
any
An error occurs when restarting the LLSMP node of the 6.0.12 version
JE-70954
any
The HTTP 404 error occurs when accessing the Liferay application after installation from the Marketplace
JE-71040
any
An error occurs when installing the Ametys application from the Marketplace
JE-71342
any
The test application from the compose.yml file is not working on the Docker Engine CE container
JE-71762
any
The MongoDB Encrypted Connection add-on should be available for the MongoDB 6/7 versions only
JE-72071
any
An error occurs when installing the Let’s Encrypt add-on due to outdated repo certificates
JE-72126
any
An error occurs when installing the Maian Cart application from the Marketplace
JE-72193
any
An error occurs when installing the Eclipse Vert.x Thin Jar Builder application from the Marketplace
JE-72314
any
The GlusterFS cluster becomes temporarily unavailable after the redeployment
JE-72551
any
The Let’s Encrypt add-on NFT rules are not removed if there are several load balancers in the environment
JE-72800
any
The Cyclos package is based on the non-supported Ubuntu 24.04 OS version
JE-36672
5.0.5
The parameter name in the php.ini configuration file is incorrect
JE-42272
5.0.5
Auto-redirection to non-standard ports is not working for the Node.js containers
JE-44633
5.0.5
Log file rotation is not working on the Varnish containers
JE-52045
5.0.5
The “permission denied” error occurs if the Env Start/Stop Scheduler add-on is installed by the collaboration member
JE-63662
5.0.5
An error occurs when accessing the MinIO cluster application with enabled built-in SSL
JE-72326
5.0.5
An incorrect password is sent via email after the Jitsi application installation
JE-72400
5.0.5
An error occurs when installing the Nexus Repository Manager application from the Marketplace
JE-72112
5.3.2
An error occurs when installing the OpenVPN Access Server package due to outdated CentOS 7 repositories
JE-69846
8.3.1
An error occurs when changing the language in phpMyAdmin for the MariaDB database
JE-70036
8.3.1
The HTTP 500 error occurs when submitting a POST request via HTTP/3 on the NGINX PHP application server
JE-71724
8.3.1
An error occurs when setting up the ModSecurity Web Application Firewall on the NGINX load balancer
JE-71863
8.3.1
HTTP/3 is not working on the NGINX 1.26.0 load balancer
JE-71936
8.3.1
Failover is not working for the PostgreSQL Cluster with the pgpool-II load balancer
JE-72055
8.3.1
Incorrect permissions for the configuration files in the /opt/jetty/etc/ directory on the Jetty application servers
JE-49037
8.4.1
Incorrect Env Start/Stop Scheduler add-on behavior if installed by the collaboration member
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. However, 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 Virtuozzo Application Management.
The most accurate and up-to-date list of the certified software stack versions can be found on the dedicated documentation page.
