Pre-Sales (Softaculous) <![CDATA[Two Virtualizor servers behind NAT]]>
You can install panel on them and after that you can ask for desktop license on the installed license key of your panels.]]>
Thu, 23 Jan 2020 15:21:09 GMT
<![CDATA[Two Virtualizor servers behind NAT]]> Tue, 21 Jan 2020 08:36:52 GMT <![CDATA[CentOS v8 KVM]]> Sun, 29 Dec 2019 20:32:35 GMT <![CDATA[How can I try virtualizor ?]]>
Sometimes, mistakes are made, and you provision 2TB when 50GB will do.  :P]]>
Tue, 15 Oct 2019 20:17:50 GMT
<![CDATA[Minimum Hardware requirements of Virtualizor]]>
Minimum 16GB for a small starter server, but that won't last very long if you have big plans for it.

Storage is not that critical...  Our dom0 hosts are under 100GB each, and VMs can be as small as 5-20GB each, so a pair of 500GB drives is probably fine to get started, unless your usage requires more.
RAID everything, or one day you'll be sorry.

Bare minimum of 4 core hyper-threaded CPU (8 threads).

KVM or OpenVZ might have slightly different requirements, but we use Xen and I can't imagine those would be much different.

SSDs will speed things up dramatically, but remember to RAID those as well, and get server-grade SSDs - consumer SSDs do not have a good lifespan.  We made that mistake, and had to replace both within several months.

As with all things server-related, more is better, enterprise-grade is better, but you can get started with a very basic machine.  RAM is king - leave room to upgrade that, because you will want more later.]]>
Tue, 15 Oct 2019 19:59:59 GMT
<![CDATA[Setting up storage, get it right form the start]]> If you would like for that storage space to be shared by each server, then you would need to make sure that file path on each server is pointing to a shared resource, such as NAS storage, glusterFS etc.

As for "what is best", it really depends on what you are trying to achieve with your Virtualizor platform. Shared storage is great if you are looking to run a HA Cluster, but depending on your method of sharing storage space, you may lose some disk speed performance.
For individual storage per slave, I set aside 150GB for the host OS and templates etc which has worked fine for me so far. Add on top of this however much storage for VPS' you will want/need. That said, if you are looking to use LVM storage, it is recommended you use a seperate volume group to your host OS. If you want to thin provision your storage, you would need to use thin LVM. In any case, you should have a read of the Storage Page in the Manual.
Mon, 07 Oct 2019 22:57:02 GMT
<![CDATA[Setting up storage, get it right form the start]]>
For each slave I add, I will also add the space on the server as storage. However, will this storage be shared among all slaves or only be used by the VPS on the slave server?

Is it recommended to just have enough storage on each slave for the OS, and then have all storage for all slaves/vps on a seperate DAS or NAS, or perhaps have it all on the master?

If it's best to have all storage on a dedicated storage server, what is the minimum HDD size I will need on each slave?

Looking forward some help with this.

Mon, 07 Oct 2019 16:54:47 GMT
<![CDATA[Quick setup guide]]> Will proceed with correspondence as per instructions]]> Fri, 13 Sep 2019 12:50:31 GMT <![CDATA[Quick setup guide]]>
No, we do not have any shortcut or quick setup guide.
Are you going to use Kvm Virtualizor without any public ips for vps ?
Would you be using LVM based storage ?]]>
Fri, 13 Sep 2019 12:31:18 GMT
<![CDATA[Quick setup guide]]> ]]> Fri, 13 Sep 2019 09:18:25 GMT