The Virtualizor Team has released Virtualizor 2.1.6
This version has some cool new features and also some bug fixes.
Below is a list of changes:
1) The Admin Index has been refurbished to give a better overview of the Resources and Current Usage.
2) Added a Manage Server module where an Admin can see the free resources, allocated resources, change settings, etc of a particular NODE.
3) Added the Reboot Option in the Manage Server module to reboot a Node.
4) The List Virtual Server page has been improved. It will load much faster then previously and sports a new look.
5) Added the feature to cache the Available Resources of a particular NODE. Hence the Available Ram and Disk Space will be available in the API.
6) On a Xen Node, only the Domain-0 Ram usage was shown. We have now modified it to show the Ram Utilization of all – VMs and Domain-0
7) Added code for better debugging.
8 ) Added support for VSwap in OpenVZ.
9) The Admin UI has been improved and it will load faster.
10) Netfront is now the default in Xen.
11) Added a feature where the Admin will get emails if the Load is high or Disk usage exceeds a LIMIT set by the Admin.
12) OS Templates will now download in the background so that the download is completed without any interruption.
13) Bug Fix: KVM VNC password when changed wasnt coming into effect. This is now fixed.
14) Bug Fix: The List IPs page showed the IPs in a random manner. This is now changed and will be ordered as per the IP Pool.
15) Bug Fix: In OpenVZ space of a VPS was not allowed to be reduced while editing. This is now fixed.
16) Bug Fix: The Site Name setting converted values to HTML entities while saving. This caused Emails to have the wrong Site Name. This is now fixed.
17) Bug Fix: During VPS Delete, the Slave server wasnt synching with the master for the updated list of VPS. This is now fixed.
Virtualizor supports OpenVZ, Xen and Linux-KVM and they all can be managed from the Master. We are adding more features and if you have any suggestions, do let us know. We hope you enjoy this version of Virtualizor.
Regards,
The Virtualizor Team