## Virtuozzo Infrastructure 7.3 Update 1 ### Overview This update introduces a new service for virtual machine migration between infrastructures, read-only project access, and support for additional guest operating systems. It also includes improvements to platform stability and reliability and addresses issues identified in previous releases. ### What's new #### User management - Read-only project access. Added support for read-only access for self-service users. Administrators can manage view-only permissions via the admin panel and the vinfra command-line tool to enable secure troubleshooting and monitoring without granting full access. #### Compute - Migration service (early access). Introduced a migration service that enables moving virtual machines and workloads between infrastructures. This feature is intended for evaluation purposes only and is not recommended for use in production environments. The feature is available in both the admin and self-service panels. The initial release provides the following capabilities: - Migration of virtual machines from VMware vSphere - Agentless virtual machine migration - Changed Block Tracking (CBT) support - Operating system morphing - IP and MAC address preservation - Parallel migration support To perform migrations, you must provide your own VMware Virtual Disk Development Kit (VDDK). For details, refer to the product documentation. If you do not have access to a Broadcom account, contact our support team for assistance. To provide feedback about this feature, contact your account manager or email info@virtuozzo.com. - New guest OS support. Added support for Debian 13 and CentOS Stream 10. ### Improvements - Improved reliability of week-long testing. The updated testing framework provides enhanced system load analysis, improved consistency and leak detection, better failure handling, scalable guest loaders, and more reliable long-duration test execution through automated log rotation and cluster state preservation. ### Fixed issues - [VSTOR-118159] A VM could fail to start or migrate after an NFS snapshot deletion timeout left inconsistent volume metadata. - [VSTOR-119720] Failed live migrations could leak compute placement reservations under heavy load. - [VSTOR-121112] A false low-disk alert could appear when several policies share the same erasure-coding scheme. - [VSTOR-126176] Chunked S3 uploads without a Content-Length header could return HTTP 400. - [VSTOR-126598] NetApp ONTAP volume scheduling could fail near LUN limits. - [VSTOR-128162] The PCI-enabled flag could remain after a cold resize to a flavor without PCI devices. - [VSTOR-128551] The Pure Storage driver could return empty volume statistics on new or lightly loaded arrays. - [VSTOR-128693] Fixed the limited-use text in the UI. - [VSTOR-128762] Incorrect physical core count could be reported on asymmetric NUMA hosts. - [VSTOR-129264] Archive migration via ARP with redirects could fail during upstream authentication for pull operations. - [VSTOR-130186] The Cinder default scheduler could omit the driver filter and goodness weigher during volume placement. - [VSTOR-130609] Live resize could be unavailable when the Nova API ran only on controller nodes without the compute role. ------------------------------------------------------ ## Virtuozzo Infrastructure 7.3 (7.3.0-185) ### Overview This update provides stability fixes. ### Fixed issues - [VSTOR-128568] Backend initialization could fail when more than one project used the name 'admin'. - [VSTOR-129614] The Backup Gateway service could crash when removing an empty file. - [VSTOR-130137] Collecting a problem report could temporarily consume significant root disk space. - [VSTOR-120606, VSTOR-129333, VSTOR-129336, VSTOR-129974] Stability fixes for the hypervisor. - [VSTOR-128142, VSTOR-128767, VSTOR-129393, VSTOR-129499] Stability fixes for object storage. ------------------------------------------------------ ## Virtuozzo Infrastructure 7.3 (7.3.0-177) ### Overview This update provides stability fixes. ### Fixed issues - [VSTOR-127496] Improved error messages for QEMU updates. - [VSTOR-128436] Creating a load balancer could fail with "Unable to find security_group". - [VSTOR-129065] Neutron could consume excessive memory when listing networks with a large number of RBAC rules. - [VSTOR-129274] Gnocchi could be overloaded by repeated PATCH requests. ------------------------------------------------------ ## Virtuozzo Infrastructure 7.3 (formerly Virtuozzo Hybrid Infrastructure) ### Overview This release focuses on technical improvements, user experience enhancements, storage performance, and S3 protocol capabilities. It also introduces the product rename from Virtuozzo Hybrid Infrastructure to Virtuozzo Infrastructure. Additionally, this release delivers stability fixes and addresses issues identified in previous releases. ### New features #### Compute - VM migration management. System administrators can monitor migration progress, cancel or retry migrations, and view the history of migration tasks. For failed migrations, the system shows the exact step where the failure occurred. - GPU metering. Added support for creating custom metrics and mapping GPU-enabled flavors to these metrics, enabling GPU usage tracking in GPU-hours. #### Object storage - S3 storage multitenancy. Introduced initial support for aligning S3 storage with the compute tenancy model (project-based isolation). In this release, the functionality is available via the command-line interface. Further enhancements are planned in future releases. ### Improvements - Updated S3 API schemas to support protocol extensions, including Object Tagging. - Improved performance for workloads using small block sizes (for example, 8 KB) with erasure coding, resulting in better storage efficiency and responsiveness. - Introduced a Grafana dashboard that provides improved visibility into the data healing (replication) process, including preliminary estimated completion times (ETAs). ### Fixed issues - [VSTOR-96428] Unsupported baseline CPU models could be offered for a cluster, preventing some VMs from being created. - [VSTOR-102166] License alerts did not respect the automatic license renewal period. - [VSTOR-104120] Deleting a volume snapshot could block the UI until the operation completed. - [VSTOR-104559] Creating a load balancer could fail when Proxy Protocol was enabled together with a UDP listener. - [VSTOR-106595] The CS service could enter a failed state if its repository directory remained locked for too long. - [VSTOR-119967] Upgrade eligibility checks and upgrade tasks could start before update packages were downloaded. - [VSTOR-120417] CSD services with RDMA enabled could fail to recover automatically after a network restart. - [VSTOR-120792] Backup storage throttling could be configured on a node that did not run backup storage services, causing the operation to fail. - [VSTOR-121082] The S3 ACC service could indefinitely retry requests to the name service. - [VSTOR-121148] Stale shaman_node_crash_threshold metrics could remain after a node was released from the cluster. - [VSTOR-121204] A node could remain stuck in the 'Entering maintenance' state. - [VSTOR-121404] Removing a compute VLAN network could fail if the VLAN interface was already absent. - [VSTOR-121409] A conflict could occur when resuming a virtual machine that had already been resumed. - [VSTOR-121454] Clients could continue to be redirected to an old upstream for too long after a redirect policy was changed. - [VSTOR-121902] The nova-compute service could get stuck while running nova-qcow2-backup if a required public key was missing. - [VSTOR-122298] More PCI devices than requested could be reserved during VM rescheduling. - [VSTOR-122354] The qemu-img check could fail to repair a corrupted QCOW2 image. - [VSTOR-122521] Object storage alerts did not correctly distinguish between S3 and NFS volumes. - [VSTOR-123125] Downloading updates could fail when /tmp was mounted as tmpfs. - [VSTOR-123203] The system could report an unmount error for a mount point that was already unmounted. - [VSTOR-123871] Users could not dismiss the telemetry consent banner. - [VSTOR-124089] Prometheus 3.3.1 could not collect metrics when Consul was still running an older version. - [VSTOR-124852] The load balancer backend could set an incorrect session persistence type for HTTP cookie-based persistence. - [VSTOR-124904] A race condition could occur in hostd while resolving the current host name. - [VSTOR-125086] VM live resize was not fully restricted in unsupported scenarios. - [VSTOR-125304] Incorrect metadata tier information was displayed in settings after configuring an S3 cluster. - [VSTOR-125509] Incremental backups could fail on heavily loaded clusters. - [VSTOR-125563] The public Barbican endpoint could be used instead of the internal endpoint during load balancer creation. - [VSTOR-125622] A KeyError could occur during live migration after a failed live NIC detach operation. - [VSTOR-125693] The backend could resume Shaman too early during a node update. - [VSTOR-125836] OpenStack Watcher audits could remain pending after a node stopped acting as a controller. - [VSTOR-126349] VM live migration could fail after increasing the number of vCPUs using live resize. - [VSTOR-126413] Node registration settings could be removed even if registration did not complete successfully. - [VSTOR-126426] Flavor lists were not paginated in the Kubernetes worker edit dialog. - [VSTOR-126928] Load balancer 'Overview' charts showed incorrect throughput units (traffic displayed in bit/s instead of bytes/s).