Using Hypervm with DA and centos?

ozgurerdogan

Verified User
Joined
Apr 20, 2008
Messages
343
I have been playing with Hypervm for couple days and it seems great software for vps service. It has backup and restore feature and also some security stuff.
So how about using centos and da with hypervm for better backup and pre-security tools comes with hypervm. I mean instead installing centos on a server, how would it be using centos and da on a vps with hypervm for backup and security and quick integration and also migration?
Do you think it will cause performans issue or something?

Thanks
 
Using a virtual machine limits your system's configuration. The server will take a small performance hit.

Why would you want to do this? It may be a good idea for your situation, but I'm curious as to what you'll gain by using virtualization. Are you using openvz or xen?
 
Not meant to use system with vps only. I mean to use hypvervm but seperating a whole physical server not seperating a physical into vpses and using of them.
I am wondering such thing because things are much easier especially migrating system to an other box, clustering system, schedule bare backup and restore, easier managability, update process of software.
http://lxlabs.com/software/hypervm/full-feature/

I know it is not a good idea but just wondering about disadvantages...
 
Do you have a few servers handy? Why not give it a try and see how well hypervm handles a 250GB vps transfer from one server to another? If you do try, please let us know the results.
 
You would not be the first to virtualize servers 1:1 per physical box. There are several advantages. One is the ease of backup of a running virtual machine. Another is the ability to move a virtual machine to a larger (or smaller) physical machine as necessary. And yet another is the ability to do almost instant builds on new physical servers.

We're going to install a new server at our new datacenter specifically for running testbed servers at the datacenter with ease of restore as required.

We're looking at both Xen and OpenVZ. Our main interest is to be able to run DA testbed servers out of the datacenter yet still control them from the office. We want more bandwidth at the office but high bandwidth along with static IP#s at our office gets very expensive fast; we can do much better if we give up static IP#s at the office, but then we'll need to run testbed servers from the data center.

We haven't made a final decision on this; there are other advantages to having local static IP#s.

I'm not sure what HyperVM is. Is it a control system for third-party VPS installations? Or is it a VPS system?

Jeff
 
Jeff,

Have you considered Proxmox ? http://pve.proxmox.com/wiki/Main_Page

Its still beta but it looks promising.

Some of the good features are that it supports Full Virtualization (KVM) as well as Container Virtualization (OpenVZ).

I have a test server with it on and already installed FreeBSD 7.0, Windows XP, and Knoppix on it (KVM).
 
So now you've told me bout something else I don't know what it is...

I presume this is something I can use to control OpenVZ. Is that correct?

Since I only need VPS to run my own testbeds, why can't I just use command line tools to set up my VPS ?

I suppose if I decide to sell VPS solutions I'll want something like this to allow my customers to manage their own VPS instances, but I have no idea how to do that and allow customers to only lmanage the VPS instances for which they have rights.

Anyone can clarify?

Jeff
 
HyperVM is software that provides a nice web-based GUI for OpenVZ or XEN. Its key selling point is that licenses are only 50 cents. It serves as an inexpensive alternative to Parallels Virtuozzo. HyperVM has received a lot of negative press because its support is almost non-existent and the key developer is rather rude.

Edit: Just thought I'd add: Virtuozzo licenses get down to $3 each or lower when you buy in bulk.

You can provide VPS's to your clients with either Virtuozzo or HyperVM and they get a nice, web-based GUI. Also check out FluidVM, or the open source WebVZ.
 
Last edited:
Thanks, littleoak. perhaps when we're ready we'll just hire you ;).
Just thought I'd add: Virtuozzo licenses get down to $3 each or lower when you buy in bulk.
Yeah, but then I'd be supporting Parallels :D.

Jeff
 
Hımm. So using vps is not a bad idea? But still worried about performance difference with real box and vps based real box.
 
Does openvz support windows os's ? I have customers that want windows based vps.
 
Does openvz support windows os's ? I have customers that want windows based vps.

Xen supports windows. But there are some differences between those:

The primary differences that YOU have to be aware of is this:

OpenVZ:
Advantages: allows overselling. Very light weight. Can accommodate more Virtual Machines in a server.

Disadvantage: There is no per vps swap.

Why this is important:

OpenVZ will KILL your application if it goes beyond the limit, and this can cause some trouble. There are people out there who want to host oracle on a 64MB vps, and with such customers, using openVZ will lead to constant application crashes, which ultimately will be blamed on the provider. (This is actually something that is common with openvz/virtuozzo hosting in general; you can check some threads at wht).

With Xen, each vps has its own swap, and thus you get an EXACT dedicated server like environment, but with lesser resources. So here, the customers applications will NOT crash, but rather it will become slower. Also, majority of the applications, like apache, spamassassin expects a lot of memory, and openVZ makes memory a very valuable commodity.

So generally my recommendation is that: For friendly customers use openVZ, and use a lot of burst memory. For not-so-friendly customers, use Xen. And that is why we are providing transparent migration. You can start a customer on openVZ, and see how it works out, and if he is getting too many application crashes, you can move him to the SAME configuration on Xen, and he should be able to do fine, though his application would be slower.
 
Back
Top