Product release: Virtuozzo Hybrid Infrastructure 3.5 (formerly Virtuozzo Infrastructure Platform 3.5)

Issue date: 2020-01-22

Applies to: Virtuozzo Hybrid Infrastructure 3.5

Virtuozzo Advisory ID: VZA-2020-005

1. Overview

In this release, Virtuozzo Hybrid Infrastructure offers a wide range of new features that enhance the experience of users working with compute virtualization and software-defined networking functionalities. Additionally, the update delivers stability improvements and addresses bugs found in previous releases.

2. New Features

  • Kubernetes as a service. With Kubernetes as a service, end users can easily deploy ready-to-use Kubernetes clusters with pre-integrated persistent storage and load balancing for their containerized applications in production. This feature is available in the self-service panel.

  • Load balancing as a service. Load balancing as a service simplifies and automates load balancer deployment in highly available high-load cloud infrastructures. Load balancing is also enabled automatically for Kubernetes as a service. This feature is available in the self-service panel.

  • VM placement rules. Placements allow administrators to group compute nodes by traits and place virtual machines on required nodes. Placements are offered as an additional service to end users in the self-service panel. There are several use cases when this feature is essential:

    • Efficient per-host licensing management (Windows Server or SQL Server licensing).

    • Placing VMs according to hardware features they require.

    • Placing tenants on dedicated nodes.

  • Maintenance mode. Enables field technicians to perform maintenance operations on physical nodes while keeping workloads online. When a node enters the maintenance mode, the platform attempts to migrate running workloads to other nodes with available resources.

  • Non-disruptive rolling updates. Cluster updates or upgrades that require node reboots can now be performed without workload downtime.

  • Automatic storage role assignment for replacement disks. It is now possible to automatically assign the storage role to replacement disks. When an administrator replaces a storage drive, it is formatted, assigned the storage role, and added to the cluster. This feature is disabled by default.

  • Other enhancements:

    • New erasure coding schemas for small clusters: 1+1 and 3+1. They offer redundancy against the failure of a single node.

    • Compute resources usage metering per project.

    • Grafana performance and statistics charts for the block storage service.

    • Signature Version 4 support by the S3 service.

    • Object locking API support by the S3 service.

    • Signed URLs support by the S3 service.

    • vinfra commands for the Backup Gateway service.

    • Support for migration from VMware with virt-v2v.

    • Backup Gateway presets for Cloudian and Wasabi.

    • User interface localized into German, Brazil Portuguese, and Spanish.

3. Bug Fixes

  • [Core Storage] Storage cluster names must not exceed 50 characters. (VSTOR-17902)

  • [Core Storage] Improved RAM consumption and memory management for nodes with more than 100 drives. (VSTOR-23586)

  • [Block Storage] The Active/Optimized path is normally chosen by the initiator (Explicit ALUA). If the initiator cannot do so (either does not support it or times out), the path is chosen by the storage itself (Implicit ALUA). (VSTOR-25145)

  • [Compute Service] No information shown in Overview while a node is being added to an existing compute cluster. (VSTOR-15978)

  • [Compute Networking] It is now possible to create bond and VLAN connections on network interfaces with the “VM public” traffic type. (VSTOR-6664)

  • [High Availability for the Admin Panel] In some cases, a node could be treated as offline for a while after the HA cluster had been created. (VSTOR-16823)

  • [High Availability for the Admin Panel] It is impossible to add a node to the HA cluster if one of the nodes included in HA cluster is offline. (VSTOR-10950, VSTOR-16716, VSTOR-17690)

  • [High Availability for the Admin Panel] Improved retention policy for admin panel backups: one per day for the last week, one per week for the last 45 days. (VSTOR-26560)

  • [High Availability for the Admin Panel] Improved management node HA for a faster reaction to disasters. (VSTOR-21012)

  • [High Availability for the Admin Panel] Other high availability improvements. (VSTOR-10950, VSTOR-16716, VSTOR-17690, VSTOR-18730, VSTOR-21170)

  • [Monitoring and Alerting] Physical space on the storage dashboard and compute overview might differ, because the compute overview also takes into account licensed space. (VSTOR-17297)

  • [Networking] Networks renamed to a predefined network name (e.g., “Private” or “Public”) cannot be renamed again. (VSTOR-20281)

  • [Networking] The maximum transmission unit (MTU) value set for network bonds cannot be modified from the admin panel. (VSTOR-22388)

  • [Networking] DHCP settings do not apply to virtual machine’s second interface. (VSTOR-25575)

  • [Object Storage] Support multiple object deletion in the S3 service. (VSTOR-27176)

  • [Updates] Monitoring of storage services may get stuck in some cases during the update. (VSTOR-26431)

  • [User Interface] Used space on software RAID volumes is incorrectly reported in the admin panel. (VSTOR-23861)

  • [User Interface] ED25519 SSH keys are not supported. (VSTOR-26405)

  • [User Interface] Trusted S3 self-signed certificate does not work for specified domain names but only for subdomains. (VSTOR-23790)

4. Known Issues

  • [Compute Service] There is no “crashed” state for virtual machines in the admin panel. Such VMs are displayed as “Paused” in CLI and as “ACTIVE” in the admin panel. (VSTOR-18054)

  • [Compute Service] When two nodes are powered off at once, VMs from the second node are not evacuated. (VSTOR-21316)

  • [Compute Service] [VM] Shelve: There is no message about insufficient resources when the user clicks “Unshelve”. (VSTOR-20652)

  • [Core Storage] Unable to release a disk with the role “MDS+cache” even if there is another disk with the same role on the same node. You need to release and re-join the node to free the unnecessary “MDS+cache” disk. (VSTOR-11567)

  • [Monitoring and Alerting] Cannot reset zoom on disk performance charts. (VSTOR-13622)

  • [Object Storage] The ostor-s3-admin list-all-buckets command reports wrong bucket sizes. (VSTOR-27096)

  • [User Interface] Unable to hide the progress bar window while uploading an ISO image to VM images. (VSTOR-19970)

  • [User Interface] Admin panel shows wrong statistics for the logical space used by VMs. (VSTOR-19699)

  • [Virtual Machine Migration] There is no ‘Cancel migration’ operation when migrating virtual machines in the user interface and ‘vinfra’ command line interface. (VSTOR-19733, VSTOR-14487)

  • [Virtual Machine Migration] No error thrown on a failed attempt to migrate a VM. (VSTOR-18053)

5. Obtaining the Release

You can upgrade Virtuozzo Infrastructure Platform 3.0 to Virtuozzo Hybrid Infrastructure 3.5 in the SETTINGS > UPDATE section. A reboot is required to complete the upgrade. Upgraded nodes will be rebooted automatically, one at a time. During the reboot, the storage service and the admin panel might be unavailable on cluster configurations without the redundancy of services or data.

The JSON file with the list of new and updated packages is available at