How to choose a virtualization scheme in LINUX?

3

3ton2012-07-17 19:15:31

linux

3ton, 2012-07-17 19:15:31

there are 2 servers. 1 for work, 1 for development. The systems are debugged, and there are more iron resources than the system needs. in the process of work, it becomes necessary to use new software, and as often happens with an uninitiated user, this is done through trial and error, and therefore unnecessary garbage on the servers. the servers use Debian and Ubuntu, I would like to leave them as host systems with minimal gestures
in connection with the above, there are 2 tasks
1. divide several sites into virtual machines in order to give some of them safe access for the server outside this virtual machine
2. use a virtual machine for tests with software like Jabber, Mail, SQL, Phone servers without harming the main server (meaning that after tests and selection, demolish the virtual machine without leaving tails from the software under test), but also have it from the host machine or from virtual access to the same sql server or asterisk
, and as a bonus, it would not be bad to get an image that could be moved from the development server to the main one as a virtual machine in a couple of commands
Initially I thought Virtualbox is convenient to move between machines regardless of the hardware, but after reading what others write, I realized that this is far from the best choice in terms of virtualization and performance, and the presence of X does not suit me, I looked towards VServer, but as far as I understood - by compromising the container in it, we get a threat to the host system, I was interested in KVM and XEN, but the latter seemed too wise for the average user, correct me if I am misinformed and I will be glad to hear from gurus with experience in this area
PS In order to reduce the circle of suspects, I limit myself to considering 2 options for KVM and XEN (Kronos). The option with Proxmox has disappeared due to the fact that it is necessary to raise a server from scratch, and in fact it is the same KVM only with a Debian-based graphical interface that is not entirely clear how it is updated.

Reply

Answer the question

In order to leave comments, you need to log in

8 answer(s)

3

3ton, 2014-01-20
@3ton

In general, I did everything on the standard Debian KVM out of the box, for more than a year of use I am satisfied with almost everything

B

bdmalex, 2012-07-17
@bdmalex

Look in the direction of Proxmox (www.proxmox.org), this is actually the same Debian, only with a graphical shell for creating VMs and containers ...

A

amarao, 2012-07-18
@amarao

If we are talking only about “install / remove packages”, that is, the development environment is more or less sane, then a banal chroot and a separate ssh on a separate IP in it may be enough. It will not provide protection from villains, but it will provide minimal overhead and convenience in dragging data back and forth.

E

Evgeny Bezymyannikov, 2012-07-18
@psman

I recommend But in the free version, the limit is 32Gb of memory and 1 percent, there is also no automatic migration between servers, but if the disks with the machines are shared, then paying off on one sideboard and raising the machine on the other is not a problem.

R

rgaliull, 2012-07-18
@rgaliull

If I understand correctly, there is no external storage.
In your case, the virtualization system must be selected based on the possibility of live migration on local storage.
This can be built on redhat according to this manual: alteeve.com/w/2-Node_Red_Hat_KVM_Cluster_Tutorial
But I want to warn you, any home garden is guaranteed to add gray hair to you. At the deadline, everything will fall and not a single vendor will help you.

E

ergil, 2012-07-17
@ergil

XCP (Kronos project), in case you want to look towards Xen, google it.
If anything, knock on the PM, I'll tell you
Kronos - XAPI implementation compiled for Ubuntu / Debian

M

max_rip, 2012-07-18
@max_rip

The main problem is that you want to keep the current machine and make it a virtual server.
As far as I know, they are all designed for virtualization. To make a server for virtual machines from a regular server will simply not be effective. It is best to make an image of a virtual machine based on the current server, deploy the virtualization system that you choose from scratch on the main hardware. And work on.

A

Alexey Skobkin, 2012-07-20
@skobkin

It is possible to look at oVirt .