View Single Post
Old 27th February 2013, 15:07
MaddinXx MaddinXx is offline
Senior Member
Join Date: Jul 2011
Location: Switzerland
Posts: 200
Thanks: 26
Thanked 65 Times in 48 Posts

Originally Posted by darinpeterson View Post
How is the script envoked, when performing certain activities within ISPConfig 3? Does it automatically take care of setting quotas via settings in ISPConfig 3?
It runs on the HW node, not within the virtual containers. You do not have to do anything special within the VE, just use ISPConfig/quota as usual. The OpenVZ quota system will take care of the rest.

Originally Posted by darinpeterson View Post
Sounded like maybe the kernel I would be stuck with after installing would be Redhat, so I didn't even try it. Not to mention that I don't understand what ploop is or does.
It's safe to go that way - and like the easiest to get current versions of the kernel/tools (which include swap support, ploop etc.). Of course you'll have "RHEL based" kernel afterwards, but you won't notice that.

PS: ploop is a new format/layout like: 1 container = 1 file. A lot of virtualization plattforms tend to go that way since it will reduce disk i/o problems.

Originally Posted by darinpeterson View Post
I would prefer not to run an additional web server on the base system, if I can get that type of install to work. It has been painful trying to get it to work though.
OVZ Web Panel uses built-in Webrick server - consumes nearly nothing. Make sure to edit the file /etc/owp.conf to enable SSL (config within OVZ dir will be ignored)

Originally Posted by darinpeterson View Post
I don't really care for the multi-server setups due to all of the resource sharing as well as the added work to keep everything up-to-date. I want to minimize the resource load on my server, have one single database to backup, one web server to manage, which means I don't have to have an additional web server for the mail server, which is a pain when it comes to managing the certificates and making everything work.
You will not get the same performance within virtualized servers as with "native" ones (what I guess, have read etc.) - and if you really don't see great benefits for your backup strategy etc. then I'd not go with containers and use the HW node. But I'd think once more about it...

There are great ways to centralized manage your servers (like Rexify framework) that allows you to fire 1 command that gets executed on all connected servers (e.g. you upgrade all servers at once).

To summarize, it's definitely up to you. Me however, I will never leave my VEs anymore. I already had enough situations where I was more than happy to be able to restore the whole server with just a few clicks - or migrate to another server with more power because the current one wasn't strong enough anymore.

For backup, I primary backup the VEs on a daily base. If you ever need to restore some single files, I unpack the backup of create a temporary virtual container where I can do all backup jobs as usual (e.g. MySQL dump).

but again, it's true - if you have software (like DBs) that have millions of queries and you already encountered boatnecks, a VE might not be the best solution. But as long as you have "common" hosting, this won't be the case.
And to get best/better performance, it's more a question of good configurations (apache, nginx etc.) rather than: Native vs. virtualized.

Hope this helps.

Reply With Quote