Re: Multiple websites on Virtualized Server
Re: Multiple websites on Virtualized Server
- Subject: Re: Multiple websites on Virtualized Server
- From: Pascal Robert <email@hidden>
- Date: Thu, 22 Dec 2011 07:53:24 -0500
Le 2011-12-22 à 07:40, Gino Pacitti a écrit :
> Ah... so there is 1 -2 ports in but the virtual space translates multiples IPs on the network?
They just translate to virtual port. Even without virtualization, you can put multiple IPs on the same network interface. For example, the new server for wocommunity.org have two network interfaces (ports) but the first port (eth0) also have 4 other IPs on virtual interfaces (eth0:0, eth0:1, eth0:2, eth0:3)
As for VM, the virtual network interface in the VM will probably (at least with VMWare and Xen) have 3 options: NAT, bridge, and private network. For hosting stuff, you should use bridge.
Also, you should have a firewall + router in front of your (hardware) server and that the server is using private IPs (192.168.x.x) and the router is the one who should handle the public IPs. So for example, if your ISP gave you 184.107.251.210 as a public IP, that should go in the firewall + router and the router will redirect traffic to your server and VMs. You have extra security like this.
But anyway, if you have 8 servers (virtual or not), you still need 8 public IPs from your ISP.
> Gino
> On 22 Dec 2011, at 12:38, Pascal Robert wrote:
>
>>
>> Le 2011-12-22 à 07:34, Gino Pacitti a écrit :
>>
>>> Ah... Could you let me know how the thing sets up when you are finished
>>>
>>> I currently have a few WOInstances on different domains served via virtual hosting on osx server but I want to move to Linux Virtualized...
>>>
>>> If you have 8 instances of Linux with 8 different sites each requiring an IP address then do you need a network card to the server with 8 connection ports?
>>
>> Each VM need at least one IP, and each VM will have a virtual network card. You don't need a hardware card with 8 ports on it, but I strongly suggest that either you get two network cards (if the server have onboard ports, just add one card) so that you can failover in case one of the ports blow up.
>>
>>> Gino
>>> On 22 Dec 2011, at 12:30, Dev WO wrote:
>>>
>>>> Hello Gino,
>>>>
>>>> I'm actually setting up a Linux virtualized server for WO (Debian).
>>>> I'm not done yet, but as far as your concerned, a virtualized server is just a server, it can have one or multiple IP addresses, but if you have 2 VM, you will have at least one IP (different) for each.
>>>> So it's basically like having a "hardware" server.
>>>>
>>>> At least that's what I think, I may change my mind when I'm done;)
>>>>
>>>> Just re-reading your question, each instance must have its own IP(s) like a "real" server.
>>>>
>>>>
>>>> Xavier
>>>>
>>>> On 22 déc. 2011, at 13:25, Gino Pacitti wrote:
>>>>
>>>>> Hi all
>>>>>
>>>>> To those who have experience with virtualized Linux server...
>>>>>
>>>>> If I set up a linux machine with virtualization and set up WO Environments and Apache for each instance -
>>>>>
>>>>> Does the individual instances of OS use the same IP address shared across OSes?
>>>>>
>>>>> So if one WOApp is on domain1.com and on OS Instance 1
>>>>>
>>>>> And
>>>>>
>>>>> WOApp2 is on domain2.com and on OS Instance 2
>>>>>
>>>>>
>>>>> How do you deal with Virtual Server configuration?
>>>>>
>>>>> Gino
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list (email@hidden)
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>
>>>>> This email sent to email@hidden
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden