The GPL licence is one of the reasons that i've choosen Vserver.
I use Linux-Vserver since 2006, on Debian hosts (i build my own kernels)
whithout any problems.
My goal was to use it with dot1q and routing.
And it's possible to do without full virtualization of network ! (it's
the same with BSD Jails ...).
Most of our criticals services works on it: ldap daemons for example,
and Hight Availability / Load Balancing / SSL frontends.
Two (very) old servers (active/passive with DRBD) with only 2 Go of RAM,
one poor Xeon 32 2.8 Ghz, and software RAID for theses services:
- 3 HA/LB servers for Webmails (HAProxy, one of them handle SSL with Nginx)
- 1 HA/LB server for the "e-learning platform" (HAProxy + Nginx for SSL)
- 2 HA/LB for ldap services (HAProxy)
- 1 Tomcat for the "Cas" SSO server
- 1 Tomcat for the "Shibboleth" SSO server
- 1 Apache/Tomcat server for the "Virtual Desktop" frontend
All of that runs easily (518 days of uptime) for our 40000 users (load
average on "active" node ~ 2).
So, thanks to the Linux-Vserver team ;)
Friendly,
LS
mourad.alia@orange-ftgroup.com a écrit :
> ________________________________________
> De : ALIA Mourad NRS
> Date d'envoi : jeudi 9 décembre 2010 19:14
> À : vserver@list.linux-vserver.org
> Objet : VServer vs OpenVZ.
> I made a mistake in my text :
>
> " VServer is more tooled, simpler, virtualise the network, supports hot VM migration".
> to be replaced by :
> " OpenVZ is more tooled, simpler, virtualise the network, supports hot VM migration".
>
> Sorry for that,
>
> Cheers,
>
> -- Mourad
>
> Dear VServers,
>
> As introduced in my previsous post, wa are about using VServer to emaulate P2P like VoIP peers. This is used for sacalability and performance testing of our VoIP application.
>
> Here are our needs :
>
> A) We want to have a maximum of VMs per server. Our server are 24 hyperthreded machine with 6 physical network interfaces :
> IP Network Server NSN2U (Ballenger-NH)
> Single 600W AC PSU
> Memory 24 GB
> CPU Dual Xeon E5645
> SATA HDD 500GB
> Ethernet I/O Module (four Gigabit rear ports)
>
> B) Each VM hosts a JVM which run one or many instances of our applications.
>
> C) The applications (VoIP peers) communicate basically through multicast.
>
> D) Each n VMs (m applications) will use one given Eth physical interface to distribute correctly the network traffic.
>
> Currently, there is a hot discussion in my departement on OpenVZ vs VServer : " VServer is more tooled, simpler, virtualise the network, supports hot VM migration".
>
> What do you think about this versus ?
>
> Any particular advise towards my use case ?
>
> Thank you for your response and support,
>
> Kind regards,
>
> -- Mourad ALIA
> Software Architect
> OBS
>
> *********************************
> This message and any attachments (the "message") are confidential and intended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.
> France Telecom Group shall not be liable for the message if altered, changed or falsified.
> If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
> ********************************
>
>
>
>
-- Laurent Spagnol Administrateur GNU/Linux Université de Reims Centre de Ressources Informatiques Campus du Moulin de la Housse BP 1039 - 51687 Reims cedex 2 Tel: 03.26.91.88.32 Fax: 03.26.91.31.87Received on Fri Dec 10 09:13:14 2010