Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am thinking of using VirtualBox to create a couple of vms to host webistes. The best setup I can work out at the moment is as follows:
1) User request comes into port 80 or 443 at the router;
2) Router forwards to host machine;
3) Host machine is running apache, which picks up the request, and proxies it out to the vm;
4) Vm is responsible for the SSL.
My main problem seems to lie in the fact that the router can only forward to one machine, that would then need to forward to the correct VM based upon the request.
Are there going to be any problems if the vm handles the SSl after the proxy request?
My other concern is, how to back up the vm's. With VirtualBox the vm needs to be stopped in order to perform the backup. Is there a better solution - maybe not using VirtualBox?
Is there a better way of doing it all-together? My way seems a little convoluted, and I can't help thinking that I am missing something.
Thanks for any tips.
Click here to see the post LQ members have rated as the most helpful post in this thread.
That does seem a lil odd that you would want to use a router to redirect requests, when that's the sort of thing DNS could help you out with.
Here's how I would suggest going about it;
You manage you're own DNS. Be it an /etc/hosts file, or a BIND instance somewhere, or your router's a WRT54G that has a full-blown DNS service built in.
1) Build a "main" VM to handle all requests on Port 80 or 443 via apache. 2) Setup redirects in the httpd.conf for the URLS and have them point to certain VMs. Be sure to setup a rewrite rule that redirects them to 443
(Because I'm assuming you want all VMs to just do SSL traffic) 3) Setup a VM per URL that hosts the page via SSL. 4) If you're going to use VirtualBox for the VMs, setup LVM and snapshot the logical volumes the VMs live on.
(You might wanna go one-VM-per-logical-volume if you do this)
(If this solves your question, please use "Thread Tools" to mark the thread as solved.)
Distribution: Debian Lenny, Squeeze, Ubuntu Various
I have been pursuing the same goal, and I've been leaning toward a Debian host reverse proxy for VirtualBox VM servers. It seems like a good direction but this is at least the second time I've heard people recommending a DNS solution. Can we elaborate on the pro's and con's?
Distribution: Debian Lenny, Squeeze, Ubuntu Various
I need a 'virtual machine' approach. I use Debian for local hosting. Years ago I created a ColdFusion (Windows) website and I need it online again. I don't have time available to translate it to LAMP. My goal is a Win2K VM for anything requiring Windows, while the host or other vm's handle my other needs. I've been reading about reverse proxy as a solution.
I could just throw additional hardware at the problem, but I am on an island with unreliable power - things blow up or burn out frequently.
What's wrong with a single OS running Apache running Virtual Hosts? Same external IP, same port forwarding, Apache displays the site associated with the DNS name included in the HTTP request ...
In the end, this is the way I am going to go.
For me, the reason to look at a VM, was that it would be easier to re-configure the box is it had a hardware failure such as main hard drive or motherboard. If the VM could be backed up, then all you need to do is copy the .ovf file back into a new install of VirtualBox and all the servers are restored. VM's should also improve the security of the box as well. However, with VirtualBox it doesn't appear possible to backup up a running VM (it needs to be shut down first, which takes the servers offline). I could only backup up the necessary files (/boot, /etc, /var/www , /opt etc.) which is just the same as not using a VM. Therefore using a VM doesn't make things any easier for me. I think Apache 2.12 and OpenSSL's, Server Name Identification functionality will handle the multiple SSL hosts OK, so that makes it the easiest solution.
Thanks for the advice so far, it has been useful to get clarification that there isn't a better way to go. Although I haven't really looked at QUMU, VMWare etc - maybe another day.