Product release: Virtuozzo Infrastructure Platform 3.0¶
Issue date: 2019-07-02
Applies to: Virtuozzo Infrastructure Platform 3.0
Virtuozzo Advisory ID: VZA-2019-055
1. Overview¶
In this release, Virtuozzo Infrastructure Platform 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¶
[Compute Virtualization] Self-service panel. A separate, completely customizable interface allows end customers to manage their own compute resources.
[Compute Virtualization] Tenant management. Service providers can now manage the projects and resource quotas of their end customers in the admin panel. Quotas for the following resources are supported: vCPUs, RAM, storage for volumes and snapshots (per storage policy), floating IP addresses.
[Compute Virtualization] Application-consistent snapshots. Ability to create snapshots of virtual machine volumes compatible with Linux and Windows deployments.
[Compute Virtualization] Virtual routers. Service providers can now configure flexible virtual networking environments. Includes support for virtual routers, Source Network Address Translation (SNAT) and static routing.
[Compute Virtualization] Floating IP addresses. Self-service panel users can now expose their virtual machines on public networks.
[Compute Virtualization] SSH keys. Self-service panel users can now enable secure access to their virtual machines.
[Compute Virtualization] High availability for virtual machines. Automatic workload restoration in case of node failure.
[Compute Virtualization] Initial customization of virtual machines. Initial guest OS customization with cloud-init scripts is now available when creating virtual machines.
[Compute Virtualization] More guest operating systems. Added support for Microsoft Windows Server 2019 and Red Hat Enterprise Linux 8.
[Compute Virtualization] Advanced memory management. Improved performance thanks to dynamic balancing of virtual machines between NUMA nodes on the host.
[Compute Virtualization] Virtual machine shelving. End customers using the self-service panel can release vCPU/RAM resources in their projects. Virtuozzo partners can free up reserved vCPUs/RAM on their hosts.
[Storage] Persistent reservations for iSCSI. Full functionality is enabled for Microsoft Hyper-V, VMware ESXi and Linux initiators.
[Installer] Improved installer. The installation program has been overhauled for a better user experience.
[UI and UX] Improved navigation for the compute service and settings.
Other enhancements. Better overall stability and performance.
3. Bug Fixes¶
In some cases, the DHCP address is not obtained by a virtual machine from a network that is not assigned to the adapter. (VSTOR-16839)
“Network has undefined speed” alert is displayed for network interfaces with unplugged links. (VSTOR-17286)
Need to manually clean browser cache and cookies after destroying the compute cluster. Otherwise the newly created compute cluster will have empty compute dashboard. (VSTOR-17752)
User cannot release the master management node from the high availability configuration. (VSTOR-17852, VSTOR-18259)
Unable to release a node from the compute cluster if it is included in the management node high availability configuration. Release the node from the management node high availability cluster first before releasing it from the compute cluster. (VSTOR-18299)
Resetting network services might result in node reboot. (VSTOR-19962)
Chunk service (CS) journals are not resized to fit caching SSD drive size and might be implicitly placed on the same disk with the CS itself. (VSTOR-20209)
Caching the value of free space on the management node might lead to unsuccessful software update. (VSTOR-20279)
Self-signed certificates for S3 are not valid for Google Chrome. (VSTOR-21670)
After node reboot, the state of the target portal groups may be lost, preventing access to some of the LUNs. (VSTOR-22386)
Network names shorter than three characters are not valid. (VSTOR-22389)
Sometimes valid target names are not usable when creating iSCSI targets. (VSTOR-22407)
Errors in chunk services alert collector might result in loss of results on subsequent alert collectors. (VSTOR-22891)
iSCSI target daemon does not provide Prometheus support. (VSTOR-23545)
Redis lock might not be deleted automatically, leading to inability to login to the backend. (VSTOR-24064)
4. Known Issues¶
25 Gbit network cards are shown as 10 Gbit ones in the admin panel. (VSTOR-9422)
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)
It is not possible to release a disk with the role “MDS+cache” on a node even if there is another disk with the “MDS+cache” role on the same node. You need to release and re-join the node to free the unnecessary “MDS+cache” disk. (VSTOR-11567)
It is not possible to cancel virtual machine migration. (VSTOR-12379)
In some cases, node failure may cause I/O to hang or cluster performance to degrade on iWARP cards. (VSTOR-12872)
Cannot reset zoom on disk performance graphs. (VSTOR-13622)
Need to manually refresh page after admin panel HA creation. (VSTOR-14800)
Need to manually refresh page after flavor creation to update list of flavors on Compute > Flavors. (VSTOR-15252)
No information shown in Overview while a node is being added to an existing compute cluster. (VSTOR-15978)
In some cases, a node could be treated as “offline” for a while after creating the HA cluster. (VSTOR-16823)
Physical space on the storage dashboard and compute overview might differ, because the compute overview also takes into account licensed space. (VSTOR-17297)
Storage clusters with names over 50 characters are not created correctly and fail. Storage cluster names must not exceed 50 characters. (VSTOR-17902)
The admin panel allows migrating a virtual machine with a public NIC to a node that is not connected to the underlying public network. (VSTOR-17921)
No error thrown on attempt to migrate a virtual machine to a node with insufficient RAM or a different CPU compared to the source node. The virtual machine shuts down and then starts again on the same node. (VSTOR-18053)
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)
No error message thrown when creating NFS cluster on a node without the “NFS” traffic type. (VSTOR-18068)
Unable to change Compute Private/Compute API roles from a private to public network after deploying the compute cluster. (VSTOR-18491)
If only one network, “Private”, is used in a cluster, need to uncheck “Admin panel” from the “Public” network before creating management panel HA. (VSTOR-18730, VSTOR-21170)
Admin panel shows wrong statistics for the logical space used by VMs. (VSTOR-19699)
It is not possible to hide the progress bar window while uploading an ISO image to the VM images. (VSTOR-19970)
The maximum transmission unit (MTU) value set for network bonds cannot be modified from the admin panel. (VSTOR-22388)
Used space on software RAIDs is incorrectly reported in the admin panel. (VSTOR-23861)
Attempting to download selected files from the S3 bucket opens them in new browser tabs instead. Affects files of certain types, including PDF, JPG and PNG. (VSTOR-24244)
5. Installing the Update¶
You can update Virtuozzo Infrastructure Platform in the SETTINGS > UPDATE section of the admin panel. A reboot is required to complete the update. Updated nodes will be rebooted automatically, one at a time. During the reboot, the storage service 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 https://docs.virtuozzo.com/vza/VZA-2019-055.json.