Release 2.2.4 - Release Notes (20 July 2020)
- A new more informative status of each NexVisor node is now available in the Infrastructure tab of the UI dashboard. The user is now able to check the current status of each node by hovering the mouse cursor over the node icon, as depicted in the following link : Physical Blade status
- The user is able to search for an available distro image from the list of the local downloaded or snapshotted templates during the creation of an Instance: Step 3 of 7: Select the Image template type
- Displaying the extra disk virtual disks attached on a created or resized Instance. Create a new flavor with the preferable extra disk storage (20GB)
- Added installation date for each template which is downloaded into the local repository, in the 'Image Templates' tab.
- Added ID number for each template which is located in a repository, in the 'Image Templates' tab.
- Added a proactive license expiration warning notification on the UI dashboard.
- Improved the system resources calculation methodology.
- Improved the displaying format of the general validation error messages.
- Improved the validation errors, regarding the resource availability of any Instance/Cluster creation.
- The user is now able to delete an uploaded image from its Sunlight template portal account. Please visit the following link for more information: Delete an image from the Sunlight template portal
- Sunlight provides the option of downloading image files from the Sunlight template portal account. The user can check the downloading process by hovering the mouse cursor over the selected image file : Download an image from the Sunlight template portal
- Updated the "upload template form" in the Sunlight template portal, with new enhancements (required fields, validation messages etc)
- Added a profile image icon in the Sunlight template portal, for each user account.
- Fixed the displayed status during the deletion process of a cluster.
- Fixed the management of the expiration session in a SIM connection.
- Fixed the Sunlight template portal validation errors.
- Fixed the web access issue, related to the gateway setup of an internal/static routable NAT forwarding network.
- Fixed the authentication issue, for connecting a cluster to a SIM.
- Fixed the creation of a virtual disk (vDisk) snapshot, in case the instance of the attached vDisk is in shutoff state.
- Fixed the internal DHCP server to provide the same IP address, after rebooting an Instance.
- Fixed the VNC console connection issue, related to the ports that remain reserved after multiple (connect/disconnect) VNC actions.
- Fixed the VNC console connection issue, after attaching/detaching the network interface of an Instance.
- Fixed the displaying statistics feature, following the rebooting of nodes.
- Fixed the displaying of IPv6 address range, during the creation of a network.
For more information on supported features please visit the following link : Supported Features for version 2.2.4.
In Development - targeted for an upcoming release
- GPU passthrough functionality. This allows the user to attach a GPU (PCI device) and run workload in a guest instance.
- The user is able to configure a DNS server IP address in the network configuration, during the creation of a network.
- Multi-user support with Role Based Access Control on the upcoming SIM v2.
- 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.
- Increased NIC speed support to 25/50/100Gbit. Revisions of supported hardware are planned throughout 2020, in order to accommodate faster NIC performance. Sunlight will be releasing a custom 100Gbit/s acceleration card, aiming at a significantly enhanced virtualised 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.
Compatibility and Limits Matrix
Please visit the following link for further information: Compatibility and Limits Matrix for version 2.2.4
- The VNC console for PV guests is not fully functional in the 2.2.4 release. This issue is currently being investigated in order to be fixed in the next release.
- The 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.
- The IP address x.x.x.254 of an internal routable DHCP network is reserved by the system and cannot be allocated by the user.
- Editing VLAN Network configuration is not currently supported. Once a VLAN Network is created, it cannot be edited again.
- The user is not able to attach multiple network interfaces in an instance at the same time. These interfaces should be added only one after the other.
- The operation of 'Add/Remove Virtual Network Interface', which refers to the option of attaching or deleting a virtual network interface (VIF) from the UI, is temporarily disabled, in case a user creates a VM instance booting from CD/ISO.
- A validation error is wrongly reported as "Image not found" on the UI, when a user creates a VM instance with the option of booting from CD/ISO and chooses to detach this CD/ISO after the installation process.
- The network cannot be auto configured for a VM instance booted from CD/ISO, in case this network is assigned as static or internal DHCP. This custom configuration should be performed during the installation process of the VM by the user.
- The instance should be shutdown before proceeding with any attach/detach action (i.e. attach/detach virtual network interface, attach/detach cdrom, etc.).
- The maximum virtual disk size supported by the system is 2TB.
- Simultaneous resizing of multiple VM instances is not currently supported.
- Resizing an instance at the maximum allowable memory size limits is not currently supported.
- Centos-6 hvm template image is not currently supported in this version (2.2.4).
- The option 'External', referring to the DHCP type during the configuration of a virtual private network (VIF), is not currently supported.
- During the upgrade phase, master and slave nodes will be required to be rebooted 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 existance of extra disks is currently not supported in this case.
- Create snapshot action is not supported simultaneously for multiple vdisks.
- In order to properly configure and access the Windows instances, it is required to execute the procedure described in the following link: Windows VM instance Configuration. Please pay particular attention to Step 4, regarding the Network configuration of the VM instance.
- In the event of a manual master failover, the process of downloading and initializing the Windows image can be performed through the instance template management repository, as it is described in the following document: Create Template Repository.
- In order to create a Windows VM, it is advised to choose the flavour named 'windowsFLV', which is specifically optimised for the Windows VM, with sufficient resources.
- All of the 10GBit LOM NICs on the blades should be cabled together into a single logical Layer 2 ethernet network segment. For redundancy reasons and in order to ensure that the high availability algorithms work correctly, we strongly recommend using separate switches.
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
Τhe modified GPL code patches used in this release are available at: GPL Code Patches Release 2.2.4