Release 2.2.2 - Release Notes (14 April 2020)
- Sunlight Virtual Disk Manager has been released. This feature provides the functionality of copying and backing up vDisks, as well as creating new Sunlight templates based on them. Please visit the following link for further details: Sunlight Vdisks Management
- Create an AWS cluster with Sunlight Infrastructure Manager (SIM). Please visit the following link for guidelines: Create AWS cluster with SIM
- Connect an on premise Sunlight cluster through the Sunlight Infrastructure Manager (SIM). Please visit the following link for additional information: Connect on premise with SIM
- Manage the instances that are connected to the Sunlight Infrastructure Manager (SIM). More specifically, the user is able to move or backup an instance from an on-premise or AWS cluster. As an added functionality, the user is also capable to associate or disassociate an IP address to this instance. Please visit the following link for additional information: Manage SIM Instances
- Sunlight.io has developed a templates page on SIM. The templates that can be included are backed up VMs from AWS or on-premise clusters. You can have a view of this feature by visiting the following link: Templates Page on SIM
- Sunlight.io introduces the Sunlight Photon Chassis. This appliance provides hardware accelerated storage-over-network to Sunlight nodes. We recommend that you visit the following links for further information:
Photon System Overview and Installation and
Sunlight Photon Dashboard and Configuration
For more information on supported features please visit the following link : Supported Features for version 2.2.2.
- Fixed time synchronization issues related to storage management.
- Fixed the displaying status for an Instance during an inside reboot.
- Improved the flag indicator of an instance that belongs to a storage optimized resource group.
- Fixed UI dropdown menu issues.
- Added an extra validation process, in order to check if all the physical disks of the selected datastore are 'ACTIVE' before proceeding to an Instance creation/deletion.
- Added a validation error, in case the VNC console of a instance is reserved by another session. Please visit the following link for additional details : Reserved VNC session
- Fixed the splash screen issue, following a fresh installation.
- Added the functionality to force delete a template, even if it is used by instances.
- Improved the list of the available interfaces, during the attachment of a new network.
- Fixed validation error messages, during the migration of an Instance.
- Removed the dummy field of the license page list.
- Added validation error messages, in case of deleting a resource group that is used by at least one instance.
- Improved the validity of the vDisk repairing procedure.
- Fixed memory allocation miscalculation issues during the formatting process of the available physical resources.
- Improved the usb installation process.
In Development - targeted for an upcoming release
- Multi-user support with Role Based Access Control.
- 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.2
- 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 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 disabled temporarily, 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 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.
- Centos-6 hvm template image is not currently supported in this version (2.2.2).
- 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 are required to be powered down. Currently, 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. An issue related to large scale clusters is currently being investigated.
- 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.
- Existing Instances in the SIM dashboard should be comprised of only one root disk, with less than or equal to 10GB of size, in order to be moved or backed up.
- Create snapshot action is not supported simultaneously for multiple vdisks.
- In some cases if the user connects to the VNC console of a PV instance and then clicks to another tab without disconnecting first, any new VNC console will not work. This issue appears only to PV instances. The correct procedure will be to disconnect first before connecting to any new VNC console. In case of such issue appearing please contact the support team.
- 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.1.6 are not supported.
GPL Code Patches
Τhe modified GPL code patches used in this release are available at: GPL Code Patches Release 2.2.2