Release 2.4.0 - Release Notes (30 March 2021)
- Sunlight releases NVIDIA GPU support for Sunlight NexVisor. Sunlight’s NexVisor drives millions IOPS per second per virtualized instance, supporting 100% GPU utilization with high-density and high-performance. This feature allows the user to attach a GPU (PCI) device and run workloads on a guest instance. For further details please visit the attached link : Sunlight GPU passthrough support
- The new SIM (Sunlight Infrastructure Manager). A major advancement on the previous SIM containing a large number of new features.
- RBAC on the new SIM. Multi-user support with Role Based Access Control (RBAC) is currently available with the new SIM.
- Snapshot scheduler. A fully fledged scheduler to allow planning of snapshotting is currently available with the new SIM.
- Instance management feature with the new SIM. Users are now able to create VMs directly from inside the SIM.
- The Sunlight Marketplace. A tool provided via the SIM, to enable automation of resource configuration and on-demand application deployment onto the Sunlight platform.
- The deletion of a network from a resource group is now supported.
- The template size is now reported in the UI dashboard. Please check the attached link : Instance Template Management
- Enhanced license expiration date is reported in the UI dashboard. For further details, please visit the following link : Dashboard
- User can now provide a custom name for the new template. Please visit the following link for further details : Local Template Server
- Improved functionality of the notification messages sidebar.
- Enhanced node data during instance migration. You can check the attached link : Instance migration
- Fixed a network issue related to the false DHCP IP address input, while editing or creating an internal virtual network.
- Fixed an issue in the storage optimized resource group, for allowing the user to select cores from a node, with a datastore composed of remote physical disks.
- Fixed the support session connectivity issue.
- Fixed the memory corruption issue, observed after a memory boundary resize of an instance launched on an AWS cluster.
- Fixed instance state failure, following an external and internal restart process of an instance launched on an AWS cluster.
- Fixed an issue related to instance crashing, after detaching the network interfaces of that instance.
- Fixed an instance migration issue relating to CentOS 7 VM guests.
- Fixed the external UI power on/off issue in Windows HVM instances.
- Fixed an issue related to the inconsistent instance creation time, reported in the instance logs tab.
- Fixed the instance boundary cores resizing issue, on an AWS cluster.
- Fixed AWS cluster reachability issue, caused by a memory leak on the Sunlight controller.
- Fixed volumes repair issue due to degraded disks, following the VM reboot process.
- Fixed invalid RAM memory issue after VM resize operation.
- Fixed the flavour update issue after instance resize.
- Fixed the network path redundancy leftover on the networks section, after reconfiguring the NexVisor and disabling the default VLAN feature.
- Fixed validation banner for expirations of authentication cookies. The validation banner message 'No authorized user’ is no longer displayed when the cookie is expired.
- Fixed enable/disable and opt-in/opt-out support session malfunctions.
For additional information on supported features, please visit the following link : Supported Features for version 2.4.0.
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.
- SIM enhancements towards added VM actions.
- Advanced recipe marketplace management with easier UI components.
- SIM ability to upgrade using the new Sunlight automated upgrade system.
Compatibility and Limits Matrix
Please visit the following link for further information on compatibility and limits: Compatibility and Limits Matrix for version 2.4.0
- 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 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.
- Simultaneous resizing of multiple VM instances is not currently supported.
- During the upgrade phase, master and slave 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 SIM 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.
You can visit the Release notes of the previous versions in the archive section. Please be reminded, versions prior to 2.2.0 are not supported.
GPL Code Patches
The modified GPL code patches used in this release are available at: GPL Code Patches Release 2.4.0