Skip to content

Release 2.0.2 - Release Notes (5 March 2019)

New Features

  1. Manually full stack Upgrade (by support staff)
  2. Enhanced error responses to the UI

Improvements

  1. Change the IP of a VM from the UI
  2. Add an extra virtual interface to a VM from the UI
  3. Remove an existing virtual interface from a VM from the UI
  4. Upload an SSL from the UI

In Development - targetted for an upcoming release

  1. Backup and restore of VM data to a remote storage target.
  2. Automated failover of the Sunlight controller service in an event of failure.
  3. Disaster recovery procedure.
  4. NexVisor automatic failover.
  5. NexVisor discovery mode and auto addition to a cluster.
  6. Manual placement and motion of VMs between different NexVisor nodes from the UI
  7. Multi-user support with Role Based Access Control.
  8. Striping of volumes across multiple physical NVMe drives to enable larger volume capacity and for enhancing single drive performance to 1 Million IOPs and above.
  9. Increased NIC speed support to 25/50/100gbit support. Supported Hardware revisions are planned in 2019 to accommodate faster NIC speeds. Sunlight will be releasing a custom 100gbit/s acceleration card that will significantly enhance virtualised NIC performance.
  10. Online Upgrade Support. This has taken priority in our dev cycle.
  11. Multi-LUN aggregation support (creating super LUNs made up of many smaller LUNs that can span physical NVMe drives for increased capacity)

Known Issues

  1. When power cycling the Sunlight cluster, even with a Fault Tolerance policy configured, automatic VM start-up is not currently supported when the cluster comes online. Fault Tolerance policy is only currently executed when the controller node stays online.
  2. 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.
  3. Multi-user and RBAC support is not supported in this version.
  4. During this phase, all upgrades will require controller and slave nodes to be powered down. Upgrade/install is achieved via the boot configuration option.
  5. We suggest that the maximum number of instances created in a cluster (in one go) is limited to less or equal than 8. We are investigating an issue relating to large scale clusters.
  6. To enable windows support in this version it is necessary for a support engineer to connect and install the windows template as it is not available from the installer by default. Please contact your sunlight sales rep to enable this.
  7. Windows VMs can not be reboot from inside the guest machine (Windows VM) and this action must be performed only from the UI, executing a stop / start.
  8. In order to create a Windows VM we advise to choose the flavour named windowsFLV, which is specifically optimised with sufficient resources for the windows VM.
  9. To configure and access the Windows instances properly, it it required to execute the procedure of following attached link: Windows VM instance Configuration . Please pay attention in Step 4 regarding to Network configuration of VM instance.
  10. In the event of a manual master failover, the process of initialising Windows support must be done again by a support engineer.
  11. Note ! While user is connecting to Windows VM via VNC access, sometimes the remote connection does not respond randomly.In this case "connect-disconnect" switches are demanded repeatedly.This phenomenon does not come up if user is connected to Windows via RDP interface.
  12. Adding multiple virtual network interfaces (VIFs) of the same subnet currently is not supported. We are working on this issue to solve it as soon as possible.

Breaking Changes

  • N/A