Editing
Installation Considerations
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="content"> <span id="top"></span> <span id="installation-considerations"></span> = Installation Considerations = <div id="bodyContent"> <span id="siteSub"></span> === From Linux-VServer === <div id="contentSub"> </div> <div id="jump-to-nav"> Jump to: [[#column-one|navigation]], [[#searchInput|search]] </div> This guide will give you an idea about pre-requesites and installation considerations of the host system. It is targeted towards production systems, so some of the information provided here may or may not be important to your setup. Decide for your own demand. {| id="toc" class="wikitable toc" summary="Contents" |- | <div id="toctitle"> <span id="contents"></span> == Contents == </div> * [[#Hardware_Compatibility|<span class="tocnumber">1</span> <span class="toctext">Hardware Compatibility</span>]] * [[#Hardware_Availability|<span class="tocnumber">2</span> <span class="toctext">Hardware Availability</span>]] * [[#Hardware_Requirements|<span class="tocnumber">3</span> <span class="toctext">Hardware Requirements</span>]] * [[#Choose_Your_Distribution|<span class="tocnumber">4</span> <span class="toctext">Choose Your Distribution</span>]] * [[#Choose_Your_Kernel_Version|<span class="tocnumber">5</span> <span class="toctext">Choose Your Kernel Version</span>]] ** [[#Versioning_explained|<span class="tocnumber">5.1</span> <span class="toctext">Versioning explained</span>]] * [[#Disk_Partitioning|<span class="tocnumber">6</span> <span class="toctext">Disk Partitioning</span>]] * [[#Final_Notes|<span class="tocnumber">7</span> <span class="toctext">Final Notes</span>]] |} <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=1|edit]]] </div> <span id="Hardware_Compatibility"></span> <span id="hardware-compatibility"></span> == Hardware Compatibility == The Linux-VServer kernel runs on many platforms, including those listed below: * alpha * arm * ia64 * m68k * mips * ppc * ppc64 * s390 * sparc * sparc64 * x86 * x86_64 See [[index.php?title=Tested_Configurations&action=edit|Tested Configurations]] for details. <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=2|edit]]] </div> <span id="Hardware_Availability"></span> <span id="hardware-availability"></span> == Hardware Availability == The host system availability is more critical than the availability of a typical server. Since it runs multiple Virtual Private Servers providing a number of critical services each, the outage of the host system may be very costly. Additionally outage can be as disastrous as the simultaneous outage of a number of servers running critical services. Discussing all aspects of high-availability is out of the scope of this document, however the following considerations should be followed to have a clean and secure host system: * Use RAID storage for guest filesystems. * Do not run software on the host system. Instead create guest systems where you can host necessary services. The only needed service on the host system is probably sshd. * Do not create users on the host system. You can create as many users as you need in any guest system. <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=3|edit]]] </div> <span id="Hardware_Requirements"></span> <span id="hardware-requirements"></span> == Hardware Requirements == The exact hardware configuration depends on how many Virtual Private Servers you are going to run on the computer and what load these VPSs are going to produce. Thus, in order to choose the right configuration, you should follow the recommendations below: ; CPUs : The more Virtual Private Servers you plan to run simultaneously, the more CPUs you need. ; Memory : The more memory you have, the more Virtual Private Servers you can run. The exact figure depends on the number and nature of applications you are planning to run in your Virtual Private Servers. However, on the average, at least 1 GB of RAM is recommended for every 20-30 Virtual Private Servers ; Disk space : Each Virtual Private Server occupies 10β500 MB of hard disk space for system files (depends on the use of [[index.php?title=Unification&action=edit|Unification]]) in addition to the user data inside the Virtual Private Server (for example, web site content). You should consider it when planning disk partitioning and the number of Virtual Private Servers to run. <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=4|edit]]] </div> <span id="Choose_Your_Distribution"></span> <span id="choose-your-distribution"></span> == Choose Your Distribution == There are many different Linux distributions, or versions. A distribution is the compiled Linux source code, usually combined with extra features and software. Some distributions are available for download at no charge while others are available at affordable prices on CD-ROM from Linux retailers worldwide. Each distribution has its own purpose, and a number of factors should go into deciding which distribution is best for each user. Some distributions are better suited to home users, others are excellent for commercial settings. Some are better suited for Intel or Macintosh PCs, other are excellent for use on high-performance computers. Any current Linux distribution most likely contains the software needed to do the job, including kernel and drivers, libraries, utilities and applications programs. Still, one of the most common questions people ask is "which distribution should I get?" This question is often answered by an assortment of people, each proclaiming their favorite distribution is better than all the rest. Probably most people favor the first distribution they successfully installed. Or, if they had problems with the first, they favor the next distribution they install which addresses the problems of the first, and so on. It is not in the scope of this document to discuss features of all the distributions out there, but nearly all should work with Linux-VServer, so it is up to you to decide which distribution fits your requirements. For an overview of available distributions checkout [http://www.distrowatch.com DistroWatch]. <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=5|edit]]] </div> <span id="Choose_Your_Kernel_Version"></span> <span id="choose-your-kernel-version"></span> == Choose Your Kernel Version == <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=6|edit]]] </div> <span id="Versioning_explained"></span> <span id="versioning-explained"></span> === Versioning explained === The Linux-VServer project maintains several branches of the kernel patch. Since version 1.00 the versioning is similar to the kernel versioning scheme. Even numbered releases (a.X.z with even X) are stable, reasonably well tested and expected not to change feature-wise. Odd numbered (a.Y.z with odd Y) releases are development releases. The last digit/number (z) is a subversion identifier. Experimental versions and Release Candidates might add a fourth identifier to that scheme. Basically the stable and development releases should be similar in functionality, but the development releases will include features and enhancements not present in the stable branch. Once those features mature (and get well tested), they will be incorporated by the stable branch.Check out the [[Feature_Matrix|Feature Matrix]] for a comparison. For example the first stable release (1.00) uses two systemcalls as the previous releases did. However, the vserver system calls have been changed in the first development release (1.1.0). Linus assigned the vserver project a single system call, so a [[index.php?title=System_Call_Switch&action=edit|System Call Switch]] has been implemented. Running a development release usually requires using recent (latest) tools from the util-vserver development branch. 1.X.z and 1.Y.z releases are for the 2.4 kernels, while 1.9.x (obsoleted by now) and 2.X.y releases are for the 2.6 series. All downloads are available in the [[Downloads|Downloads]] section. Also take a look at the [[ChangeLogs|ChangeLogs]]. <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=7|edit]]] </div> <span id="Disk_Partitioning"></span> <span id="disk-partitioning"></span> == Disk Partitioning == Since each guests is a seperate root filesystem somewhere in the host system filesystem hierarchy, it is advisable to create a partitioning scheme that fits your needs. Discussing all possible disk configuration is surely out of the scope of this document, however you should take the following guidelines into account while setting up disk space for your guest systems: * Generally, one big partition for ''all'' guest systems should suffice * If you don't want to use [[index.php?title=Disk_Limits_and_Quota&action=edit|Disk Limits]] you can use one partition per guest system to limit its available disk space. However this will (in most cases) prevent an easy enlargement of disk space later on. * If you want to use [[index.php?title=Disk_Limits_and_Quota&action=edit|Quota]] ''inside'' your guest system you have to use seperate partitions per guest system. This will probably change in the future * You should take care of hard disk failure, e.g. use RAID systems, make regular backups, etc. * To obtain more flexible space management consider using some Volume Management solution like lvm, lvm2 or evms. <div class="editsection" style="float:right;margin-left:5px;"> [<nowiki/>[[index.php?title=Installation_Considerations&action=edit§ion=8|edit]]] </div> <span id="Final_Notes"></span> <span id="final-notes"></span> == Final Notes == If you think the information provided in this document is too vague, feel free to [[Communicate|contact]] the Linux-VServer community and ask for help on your specific setup. <div class="printfooter"> Retrieved from "http://wiki.linux-vserver.org/Installation_Considerations" </div> <div class="visualClear"> </div> </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