Skip to content

Release 4.6.4 - Release Notes (10 April 2023)

Information

This is our newest release (release 4.6.4) with major changes. You need to have at least version 4.2.0 to be able to upgrade to this atest release.

Additional instructions would be published as far as the upgrade procedure is concerned.

New Features

  • Allow a single Ansible execution of a recipe for different VMs that belong to different clusters.
  • Added the Cloudbase-init service for Windows VMs.
  • Forced the execution of Ansible from the NexCenter VM in order to increase execution security.
  • Added time and date configuration for the Controller VM.
  • Removal of a Physical Node from a cluster, automatically configures the FT rules.
  • Added all the available physical NICs (network interfaces) to the VNC and Cloud-Init management networks.
  • Added Bring your own recipe to the NexCenter that enables the creation and editing of recipes inside the NexCenter.
  • Provide hyperlinks in NexCenter for the created assets associated with the execution of a recipe.

Improvements

  • Remove the cluster creation and docker provisioning functionality from the virtupian API and UI.
  • Provide information about the user-data required for the cloud-init scipts via the UI.
  • Added functionality to designate/reassign a FOPrimary Node to Primary.
  • Configure storage drives post-install from the NexCenter.
  • Support Recipe execution for non-cloudInit Linux distros.
  • Support the PCIe devices with FT.
  • Added support for multiple PCIe devices for VM creation.
  • Merged cloud and on-premise Cluster tabs in NexCenter infrastructure UI.
  • Added power actions for VMs in the NexCenter UI.
  • Generate random credentials for Windows VMs.
  • Whitelabel functionality for the recipes Logos.
  • Enhanced the automated VM IP searching procedure by incorporating additional subnets, which expands the scope of IP address discovery.
  • Specify the PCIe devices of the Recipes, using model name, device id etc.
  • Implemented an automated validation process for inspecting the infrastructure and JSON configuration files of a Recipe prior to its execution.
  • Added Virtupian Request ID in the NexCenter logs. Also provide the NexCenter request ID to the installed recipes.
  • Renamed the Master and Slave Nodes to Primary and Secondary.
  • Single nexvisor API command to get multiple VMs, reducing the response time of the GET instances API call.
  • Enhanced HA failover and repair functionality of clusters.
  • Updated the maintenance mode for the VirtupianAPI service.
  • Single arp-scan command to indentify the IPs of multiple VMs.
  • For Private and Internal DHCP networks, IPs of the VMs or obtained from the lease file of the Internal DHCP server instead of using arp-scan.
  • Improved the info provided about the Recipes creation failure.

Bug Fixes

  • Fixed the upload Recipe/File, using HTTPs protocol, on the NexCenter.
  • Fixed an issue regarding NexVisor crash after aborting resync in the repair procedure.
  • Removed a required field during the cluster form fucntionality, causing issues.
  • Removed rack and blade fault tolerance settings from the RG creation.

AWS product updates

  • BUGFIX for low performance NVMe drives.
  • Expose NVMe serial number to the higher stack.
  • Added support for EBS storage volumes, for AWS clusters.
  • Improvements on displaying network information in the VM details.
  • The Management VM of the AWS cluster, is now an Ubuntu18.04.
  • Removed the unlimited license key for the AWS clusters.
  • Hide the Physical Nics 0,1 from the VirtupianUI. Remove these NICs from the RG and VM creation.
  • Create Recipes with already created Datastores, using the Datastore name.
  • Added support for the EBS volumes.
  • Create 2 datastores (Persistent/Non-persistent) automatically, upon AWS cluster creation.
  • Permit the creation of 1-Node cluster only for the AWS cluster creation.
  • Export the serial number of integrated NVME and EBS storage devices.
  • Delete Manager VM automatically, after the creation of the AWS cluster.
  • Make the disk and the Datastore calls unlicensed.
  • Fetch Node types per availability zone and use it on cluster creation.
  • Refactored the AWS cluster deletion procedure, reporting the deletion process with states.
  • Let the user decide to keep or release the EBS volumes, after the deletion of the AWS cluster.

In Development - targeted for an upcoming release

  • Striping of volumes across multiple physical NVMe drives, in order to enable larger volume capacity and enhanced single drive performance to more than 1 Million IOPs.
  • Revisions of supported hardware are planned, in order to accommodate faster NIC performance.
  • Multi-LUN aggregation support (creating super LUNs, consisting of many smaller LUNs that can span physical NVMe drives for increased capacity).
  • Physical NVMe drive hotplug removal/addition.
  • NexCenter enhancements towards added VM actions.
  • Advanced recipe marketplace management with easier UI components.
  • The SAUS service, is under development towards the API automated upgrade. Next iterations will focus in providing NexCenter functionality towards the lower NexVisor stack.
  • Manage the Sunlight Clusters licensing via the NexCenter UI.
  • The latest distro versions are currently in testing.

Supported Features

For additional information on supported features, please visit the following link : Supported Features for version 4.6.4.

Compatibility and Limits Matrix

Please visit the following link for further information on compatibility and limits: Compatibility and Limits Matrix for version 4.6.4

Current list of supported Network Adapters

Please visit the following link for further information on supported Nics: supported Network adapters

Known Issues

  • In order for the GPU device to be assigned to a different VM, the persistence mode should be disabled. For more information, please refer to the section "Disable NVIDIA GPU Persistence mode" in the following document: Disable NVIDIA GPU Persistence mode
  • Occasional connection issues to PV guest console. Suggested mitigation solution is to reboot the VM.
  • The automated installation of PV drivers for MS Windows ISO images is not currently supported. An end-to-end functional solution is currently in the development process.
  • Editing an existing VLAN network is not currently supported. In order to edit the VLAN, you must delete and recreate the network.
  • It is not possible to edit the network configuration of a VM in the case the instance boots from an CD/ISO.
  • For a VM instance that is booted from CD/ISO, Sunlight does not initialize the cloud init logic. Network configuration must be applied on the VM by the user.
  • The maximum supported virtual disk size which is currently tested in the system is up to 2TB. Larger size vdisk deployments are currently under test.
  • NexCenter simultaneous resizing of multiple VM instances is not currently supported.
  • During the upgrade phase, primary and secondary nodes will be required to be booted down. Currently, the upgrade is performed manually by the Sunlight support team.
  • It is recommended that the maximum number of instances created in a cluster (all at once) should be limited to less or equal than 8.
  • Please use “SHIFT”, instead of the “CAPS LOCK” button, for capital letters, when typing the login/password of an instance through the VNC console. Using the “CAPS LOCK” button currently results in misspelled username/password.
  • Instances that will be moved and/or backed up in the NexCenter dashboard should have only one root disk. The existence of extra disks is currently not supported in this case.
  • The "Create snapshot" action currently does not support massive parallelism. We are currently testing to lift the limitations.
  • There is a caveat in using all physical NICs on an AWS cluster. Physical NICs 0,2,3 should be used only for private networks. Physical NIC 1 should not be used at all. The rest of the physical NICs, 4 to 15 should be used only for public access networks. In future releases this will be handled automatically via the virtupian UI.
  • Currently we do not support VMs using the UEFI bootloader.
  • We have noticed an issue when using large NVMe drives, larger than 2TB, during the installation process. We suggest that the NVMes are completely zeroe'd out before starting the installation.

PV images

PV images are be deprecated - Our suggestion is to use a new template repo that does not include PV images, Please use HVM.

Supported Versions

You can visit the Release notes of the previous versions in the archive section. Please be reminded, versions prior to 4.2.0 are not supported.

GPL Code Patches

The modified GPL code patches used in this release are available at: GPL Code Patches Release 4.6.4