Skip to content

Release 2.1.4 - Release Notes (09 July 2019)

New Features

  1. A Template portal has been implemented, providing the functionality of uploading own custom images. Please visit the following link for more details: Sunlight Template Portal

  2. Users are now able to create an individual repository on the platform, including templates that are already uploaded on the Sunlight.io Portal or located at a private repository. Please visit the following link for further information about this feature: Create a new platform repository

Improvements

  1. Following the reboot of a node, vdisks can be automatically repaired without the need of an interaction from the UI. That applies in the case of a replicated datastore.

In Development - targeted 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. Revisions of supported hardware are planned throughout 2019, in order 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. Windows VM support is considered to be a preview feature.
  2. Centos-6 hvm template image is not currently supported in this 2.1.4 version.
  3. The MySQL Database of the system may be corrupted in the case of an unexpected power failure. We are doing whatever is required to address this issue as a priotity. The immediate solution for this is to have the system setup with replicated datastore and db_metadata enabled, and in the case of such failure to manually fail over the master to a slave node.
  4. During the process of creating a new VM or a start/stop action of an existing VM with XFS root file system, in some cases 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.
  5. The option 'External' referring to the DHCP type during the configuration of a virtual private network (VIF) is not supported.
  6. During the upgrade phase, master and slave nodes are required to be powered down. Currently, upgrade is performed manually by the Sunlight support team.
  7. Failover of network traffic between physical ethernet ports is not currently supported in this release. All 10 GBit ethernet ports must be connected for optimum product performance. Multi-user and RBAC are not supported in this version.
  8. 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.
  9. Adding multiple virtual network interfaces (VIFs) of the same subnet is not currently supported.
  10. The initialization of separate partitions on a physical disk is not supported.

FAQs

  1. We suggest users to use 'SHIFT' instead of 'CAPS LOCK' key due to this does not work properly typing the login password of an instance via the VNC console.
  2. We suggest users to create as much VM instances as the range of the IP addresses that can be provided in the network configuration. In case of there are no available IP address, a new created VM instance will fall into in error state.
  3. 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.
  4. 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
  5. 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