Editing
Short+presentation
From Linix VServer
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
<div id="header"> <div class="logo"> [[Linux-VServer|[[File:http://linux-vserver.org/logo.png|[Home]]]]] </div> <span id="short-presentation"></span> = [[?action=find&find=short+presentation|short presentation]] = <div id="toolbar-top"> [[Linux-VServer]] | [[RecentChanges]] | [http://linux-vserver.org/?action=prefs Preferences] | [http://tavi.sourceforge.net/FormattingRules FormattingRules] </div> ----- </div> <div id="body"> First for those who still haven't heard of the vserver project: It allows you to run linux inside linux: Any distributions inside any distributions. Each virtual server has its own packages, its own services, its own users and is confined to using some IP numbers only and some area(s) of the file system. You can think of them as virtual machines. For many people, virtual server may look like a great toy: Very high geek coolness factor, but not much. It looks cool, but probably not for everyone. '''Wroonnnngggggg!!!!''' Few specs and some explanations 1-Virtual servers are running with the same kernel as the host. Performance are exactly the same as a non virtual server (unlike other VM solutions). 2-Virtual servers have no overhead. There is no special daemons running. A vserver running crond,sshd,httpd and sendmail uses the same resources as a normal linux server. 3-Virtual servers generally share the disk space with the host, so there is no need to pre-allocate disk space for each vserver only to find out later that your disk is full, yet each vserver is only using of tiny portion of their allocated space. 4-A second vserver generally cost 40-100 megs of disk space only. It shares most of the binaries and libraries with the first one. Most of this space is a copy of the RPM database. 5-Vservers are updated independantly even if they share binaries with other vservers. 6-32 bits distributions vservers runs normally on a 64bits linux host, but faster, sometime a lot. 7-You can mix various distributions on the same server all runing at once. http://www.solucorp.qc.ca is a rh7.3 vserver running on a rh7.3 server. We also run FC3 vservers as well as Debian vservers on the same box (A Celeron 500mhz btw). 8-Admin tools work inside a vserver as usual. 9-A cracked vserver can't reach the host server. The host server may be used to investigate safely the cracked server (and fix it), something almost impossible with a typical linux installation. <span id="why-do-you-need-vservers"></span> = Why do you need vservers ? = Believe me this will change a lot and you will never look back. Here are some ideas '''A) Many tasks on the same box''' As the hardware evolves, it is tempting to put more and more tasks on a server. Linux can handle it. Linux is reliable and so on. At some point, you end up with so much stuff and so much people fiddling in the same box that you start fearing whenever you wish to update something. Vservers are fixing this. The same box runs multiple vservers and each one does the job it is supposed to do. If you need to upgrade to php5 for a given project you do so and only this project is affected. Also, you can give the root password of a vserver to one administrator and he will be able to perform updates, restart services and so on without having to know about every other project hosted on a server. '''b) Moving vserver around''' Once you have found that a project is using more resource than expected, you can move it to another box without having to fiddle here and there. A vserver is just a directory inside the host server. You tar it and copy it to another box and restart it there. An administrator can move vservers around without knowing what they do. '''c) Experimenting and upgrading.''' You have this typical problem. You intend to upgrade a site either with new package (new PHP5) or new features (new version of the Web applications). After having tested all this on the development machine, you are ready to update the production server. Having some experience you do it properly * First a good backup of the server * Then you perform all the upgrades and install the new applications * Fire: the new server is online and kicking. * 2 hours later, you realise that something does not work as expected. * To make it worst, it works fine on the development machine. * Now it is 2 am and this has to work by 8am. Hum. (A famous french song: Je m'arrete ou je continue) Should I stop and restore the tape or I hang on and hope to find the problem... We have all experienced this. Another solution to this problem would be to install the new production server on new hardware, but this is not as easy as you have to clone the first server (most people are not confortable doing this) or you do not have the hardware. Using vserver, all this is very easy * You stop the production vserver * You clone it (Cloning a vserver takes 1 minutes unless it has a lot of data). * You perform the upgrades in the new vserver and give it life. Later you find it does not work as expected and you can't fixed it (this night). * You turn off the new vserver and assign it a new IP number. * You start both the old and new. Now the old is still online and you can fiddle with the new (on a different IP address) to fix the problem. '''d) development''' You are working on a new project. At this point you have no idea of the resource it will need (load). In general, we do a meeting and decide about the new hardware. But we have no idea. So instead, we put the new project on a vserver on the first available linux box, including the workstation of the developper. And we develop. Once the thing is ready, we clone the vserver on some production server and give it a go. Later once we know how popular the new service is, we can move it again to a more powerful server, as needed, without any fiddling (moving accounts, installing packages, and so on) On my notebook, I have 33 vservers allowing me to tests various project and various distributions from rh6.2 to FC3 and Debian. ----- We are often talking about our preferred distribution. Should we use FC, Debian or something else ? Should we give a spin to the latest and greatest ? With vservers, the choice of a distribution is less important. When you select a distribution, you expect it will do the following * Good hardware support/detection * Good package technology/updates * Good package selection * Reliable packages The choice is important because every service running on a box will be using the same distribution. Most distributions out there are good and reliable. But they have flaw. For example, a distribution say XXX is great but is not delivering the latest and greatest PHP. Now because you have decided to use XXX for some projects, it does not prevent you from using XXY for other projects. So instead of moving to XXY for everything, you move to it as you see fit, project per project. Takes few hours to investigate vservers, you will never look back. </div> <div id="footer"> <div class="copyleft"> <br /> Permission is granted to copy, distribute and/or modify this document under the terms of the<br /> [http://www.fsf.org/licenses/fdl.txt GNU Free Documentation License], Version 1.2 or any later version published by the Free Software Foundation. </div> ----- <div id="toolbar-bottom"> [[short+presentation?action=edit|Edit this document]] | [[short+presentation?action=history|View document history]]<br /> </div> Document last modified Fri, 04 Mar 2005 19:45:37<br /> <div class="form"> <br /> Search: </div> </div>
Summary:
Please note that all contributions to Linix VServer may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Linix VServer:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Page actions
Page
Discussion
Read
Edit
History
Page actions
Page
Discussion
More
Tools
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
About
Overview
Paper
News
Developers
Donations
Search
Getting Started
Downloads
FAQs
Documentation
Support
Participate
How to participate
Report a Bug
Communicate
Teams/Projects
Hall of Fame
Resources
Archives
Recent Wiki Changes
Pastebin
Related Projects
VServer Hosting
Happy VServer Users
Tools
What links here
Related changes
Special pages
Page information