Skip to content

Release 2.1.1 - Release Notes (20 May 2019)

New Features

  1. Users are now able to Create/Delete their own repository, in order to upload a custom image template via the UI Instance Template Management. For further information please visit the following link: Instance Template Management


  1. Statistics of VM instances were not always displayed properly. This issue has been entirely fixed in this version.
  2. Users are now able to review the status of the physical devices. Installation, SSDs reserved disks and partitions are not visible on the UI anymore.
  3. More informative messages regarding VM instance migration are now available, displayed on the UI.
  4. Switch VLAN ID can be configured by the user during the installation procedure.
  5. Sessions' time frame until expiration has been extended, so that users do not need to constantly refresh pages during use.
  6. Windows VMs can now be rebooted through the guest machine (Windows VM).

In Development - targetted for an upcoming release

  1. Multi-user support with Role Based Access Control.
  2. 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.
  3. Increased NIC speed support to 25/50/100gbit. Supported Hardware revisions are planned during 2019 to accommodate faster NIC speeds. Sunlight will be releasing a custom 100gbit/s acceleration card aiming at significantly enhanced virtualised NIC performance.
  4. Multi-LUN aggregation support (creating super LUNs made up of many smaller LUNs that can span physical NVMe drives for increased capacity)
  5. Improved handling of open VNC connections to a VM instance.

Known Issues

  1. The operation of 'Add/Remove Virtual Network Interface' which refer to the ability of the user to attach or delete a virtual network interface (VIF) from the UI is disabled temporarily for Windows Instances in this Release 2.1.1.
  2. During the process of creating a new VM or a start/stop action of an existing VM with XFS root file system, sometimes the corresponding instance might not be reached, even though it is in an active 'green' state on the UI. The recommended solution is to proceed with rebooting the instance until it becomes accessible again.
  3. VM instance cannot be properly resized while the user is trying to add a new volume or expand a previous one.
  4. Failover of network traffic between physical ethernet ports is not currently supported in this release. All 10 GBit ethernet ports must be connected for proper product behaviour.
  5. Multi-user and RBAC are not supported in this version.
  6. During the upgrade phase, master and slave nodes are required to be powered down, while the existing VM instances will be deleted at the end of the process. Currently, upgrade is performed manually by the Sunlight support team.
  7. 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.
  8. Adding multiple virtual network interfaces (VIFs) of the same subnet is not currently supported.
  9. The initialization of separate partitions on a physical disk is not supported.
  10. Following the reboot of a node, vDisks should be manually repaired from the UI, in case these vDisks exist in a replicated datastore. In addition, if any of the nodes is suddenly powered off, please note that currently there is no support for automated repair of existing vDisks.


  1. 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.
  2. 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: Instance Template Management
  3. In order to create a Windows VM it is advised to choose the flavour named 'windowsFLV', which is specifically optimised with sufficient resources for the windows VM.

Breaking Changes

  • N/A