Skip to content

Release 2.0.2 010319

New Features

  1. Manual full stack Upgrade (through Sunlight support)
  2. Enhanced error responses on 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 through the UI
  4. Upload an SSL from the UI

In Development - targetted for an upcoming release

  1. Backup and restore VM data to a remote storage target.
  2. Automated failover of the Sunlight controller service in case of failure.
  3. Disaster recovery procedure.
  4. NexVisor automatic failover.
  5. NexVisor discovery mode and auto addition to a cluster.
  6. Manual placement and transfer of VMs between different NexVisor nodes through the UI
  7. Multi-user support with Role Based Access Control.
  8. Striping of volumes across multiple physical NVMe drives, in order to enable larger volume capacity, as well as enhancing single drive performance to 1 Million IOPs and above.
  9. Increased NIC speed support to 25/50/100gbit. 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 is of high priority in Sunlight's 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 currently executed only when the controller node remains 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. Currenlty, all upgrades require controller and slave nodes to be powered down. Upgrade/install is performed via the boot configuration option.
  5. It is advised that the maximum number of instances created in a cluster (in one go) is limited to less or equal than 8. An issue related to large scale clusters is currently being investigated.
  6. In order to enable windows support in the current version, it is necessary for a support engineer to connect and install the windows template as it is not available be default from the installer. Please contact your Sunlight sales rep to enable this feature.
  7. Windows VMs can not be rebooted through the guest machine (Windows VM), this action must be performed only from the UI, executing a stop / start sequence.
  8. 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.
  9. In order to properly configure and access the Windows instances, it it 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 a VM instance.
  10. In the event of a manual master failover, the process of initialising Windows support must be performed once again by a Sunlight support engineer.
  11. In some cases, the remote connection does not respond while the user is connected to Windows VM via VNC access. “Connect – Disconnect” switches are required in a repeated way, in order to resolve this issue. This issue is not present in case the user is connected to Windows via RDP interface.
  12. Adding multiple virtual network interfaces (VIFs) of the same subnet is not currently supported. The Sunlight team is currently working on this issue, in order to be resolved as soon as possible.

Breaking Changes

  • N/A