Release 2.2.1 - Release Notes (12 February 2020)
- New enhanced usb installation procedure. The installation procedure inspects the system hardware, in order to decide if the system meets the requirements for running the Sunlight Enterprise Software platform. Please visit the following link for additional information : Install on premise
- Sunlight offers network path redundancy for directly attached clusters. This ensures network availability in case of path failure and unavailability. The Sunlight cluster availability is guaranteed in the event of losing less or equal than 50% of the physical network paths. For further information please visit the following link : Network Path Redundancy.
- Automatically activated support session: Enable/Disable the automated support session activation/deactivation.
- Capability of renaming an instance, following an instance creation. The user is able to rename the instance once it is created. Instance Rename.
For more information on supported features please visit the following link : Supported Features for version 2.2.1.
- Improved UI dropdown menus.
- Updated real time charts of the dashboard, following a refresh of the browser page.
- Fixed dashboard miscalculation issues and formatting of the available physical and virtual resources.
- Improved automated repair of the DB-Metadata.
- Supported NVMe physical drives can also be used as installation disk.
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.1.1
- In rare occasions, during the creation of a parallel instance, the user is not redirected to the 'Instances' page after clicking on the finish button.
- Automatic Master Failover is not supported for more than 2 (master/slave) nodes.
- 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.1).
- 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.
- Multi-user and RBAC are not supported in this version.
- 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.
- The implementation of separate partitions on a physical disk is not supported.
- 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.
- We suggest users to create as many VM instances as the range of the IP addresses that can be provided in the network configuration. In case there are no available IP addresses, a newly created VM instance will fall into an error state.
- 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 are able to visit the Release notes of the previous versions in the archive section. Please be reminded, versions prior to 2.1.6 are not supported.