Skip to content

Release 2.2.0 - Release Notes (20 November 2019)

New Features

  1. The number of used installation images limited to a single one. The nodes are classified as master/slave at installation time via the nv-configure process. Please visit the following attached link : Install on premise
  2. Sunlight offers redundancy into VLAN networks. In case one of the available NICs attached to a VLAN virtual network fails, an alternative one will be automatically available to take over the connectivity. For further information you can follow the attached link : VLAN Network Redundancy.
  3. Automatic Master Failover. In case the master node fails, one candidate passive slave node called failover master starts to provide services by recovering the failed node. In order to enable this feature, please visit the following instructions : Automatic Master Failover.

Supported Features

For more information on supported features please visit the following link : Supported Features for version 2.2.0.

Improvements

  1. VM instances attached to a custom vitual internal routable NAT forwarded netwok are able to get access on the internet properly.
  2. Automated degraded vdisk repairing. Degraded virtual disks are repaired after nexvisor reboot.
  3. Supported NVMe physical drives can be used as well as installation disk.
  4. Added UI splash page informing the user that the fault tolerance activated and it is in progress before logging into to dashboard in case of automatic master failover.
  5. Added UI informative form validation errors in case of the user would like to use a template that has not been already downloaded locally(e.g CD/ISO, docker/swarm cluster images et).
  6. Added validation messages for required fields on the 'Upload form' of Sunlight template portal.
  7. Improved the UI deletion of a virtual custom network.
  8. Fixed Release information session on administration page
  9. Fixed accurate statistics reporting (disk IO, network IO, CPU utilisation reporting) for instances.

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 consisting of many smaller LUNs that can span physical NVMe drives for increased capacity).
  5. 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.2.0

Known Issues

  1. Automatic Master Failover is not supported for more than 2 (master/slave) nodes.
  2. The IP address x.x.x.254 of an internal routable DHCP network is reserved by the system and cannot be allocated from the user.
  3. Editing VLAN Network configuration currently is not supported. Once a VLAN Network created , it cannot be edited again.
  4. The total memory usage is miscalculated in case of the automatic master failover has been activated and has taken place.
  5. The operation of 'Add/Remove Virtual Network Interface' which refers to the ability of the user to attach or delete a virtual network interface (VIF) from the UI is disabled temporarily in case of a user creates a VM instance booting from CD/ISO.
  6. A validation error is wrongly reported as "Image not found" in the UI when a user creates a VM instance with option boot from CD/ISO and chooses to detach this CD/ISO after installation process.
  7. The network cannot be auto configured for a VM instance booted from CD/ISO in case of this network is assigned as static or internal DHCP. This custom configuration should be done during the installation process of the VM by the user.
  8. In order to change the state from "Detach Cd Rom" to "Attach Cd Rom" in the actions menu, when the user detaches a CD/ISO from an instance, a webpage refresh is required. There is no need for a page refresh when the "Attach Cd Rom" action is performed.
  9. The instance should be shutdown before proceeding with any attach/detach action (i.e. attach/detach virtual network interface, attach/detach cdrom, etc.)
  10. The maximum virtual disk size supported by the system is 2TB.
  11. Simultaneous resizing of multiple VM instances is not currently supported.
  12. Support for adding multiple NICs to a VM is provided only in Windows instances.
  13. Centos-6 hvm template image is not currently supported in this version (2.2.0).
  14. The option 'External', referring to the DHCP type during the configuration of a virtual private network (VIF) is not currently supported.
  15. During the upgrade phase, master and slave nodes are required to be powered down. Currently, upgrade is performed manually by the Sunlight support team.
  16. Failover of regular network traffic between physical ethernet ports is not currently supported in this release. All 10 GBit ethernet ports must be connected for optimal product performance. Multi-user and RBAC are not supported in this version.
  17. 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.
  18. The implementation of separate partitions on a physical disk is not supported.
  19. 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.
  20. 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 address, a newly created VM instance will fall into an error state.

FAQs

  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: Create Template Repository.
  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

Supported Versions

You are able to visit the Release notes of the previous versions in the archive section. Please mind, versions prior to 2.1.6 are not supported.