Skip to content

Release 2.1.0 - Release Notes (13 May 2019)

New Features

  1. We have added Template management and the ability to Download, Enable/Disable and Delete approved image templates via the UI. For further information you can visit the following attached link : Instance Template Management
  2. We have enabled the ability to resize an instances according to a given flavor. Users are able to increase or decrease the number of cores and the memory size of an instance. They can also increase the size of the available root partition and ephemeral disks attached to a single VM instance. We do not plan for the immediate future to support decreasing the size of a vdisk. Check this link for extra feature info : Instance Resize
  3. Dedicated Network Setup. Network controller uses two Ethernet interfaces. The user can configure one of them to become dedicated port. That means this port will allow only dedicated data traffic to pass through and excludes all management traffic flow. For further details on this feature, you can visit the following attached link: Dedicated Ethernet Networking

Improvements

  1. Statistics of VM instances were not always displayed properly. This issue has been fixed entirely in this version.
  2. Users are able to check the status of physical devices. Installation, SSDs reserved disks and partitions are not visible in the UI anymore.
  3. More informative messages are displayed in case of a VM instance migration on the UI.
  4. Switch VLAN ID can be configured by the user during the installation procedure.
  5. The expiration of the time period of a session has been extended so that the user does not need to make repetitive page refreshes during use.
  6. Windows VMs can now be rebooted from inside 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 to enable larger volume capacity and for enhancing single drive performance to 1 Million IOPs and above.
  3. 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.
  4. Multi-LUN aggregation support (creating super LUNs made up of many smaller LUNs that can span physical NVMe drives for increased capacity)
  5. User will able to better handle 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. In the creation of a new VM or during a start/stop action of an existing VM with XFS root file system, sometimes the corresponding instance, even though it is in an active 'green' state on the UI, it could not be reached. We suggest that you proceed with rebooting the instance until it becomes reachable again.
  3. 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.
  4. Multi-user and RBAC support is not supported in this version.
  5. During the upgrade phase, master and slave nodes are required to be powered down as well as the already existing VM instances will be deleted in the end of the procedure. Upgrade is achieved manually by the support team at the moment.
  6. 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.
  7. Adding multiple virtual network interfaces (VIFs) of the same subnet currently is not supported.
  8. The initialization of separate partitions on a physical disk is not supported.
  9. After a node reboot, the user should manually repair vdisks from the UI, if such vdisks exist in a replicated datastore. Also if any of nodes becomes powered off suddenly, there is no support for automatated repair of existing vidisks at this moment.

FAQs

  1. 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.
  2. In the event of a manual master failover, the process of downloading and initializing Windows image can be done from the instance template management repository as it is described in the following document : Instance Template Management
  3. 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.

Breaking Changes

  • N/A