Usage Scenarios - Revision history

Glenn: +{{Languages|Usage Scenarios}}

2011-10-21T21:56:53Z

+{{Languages|Usage Scenarios}}

Glenn: spelling

2011-10-21T19:00:59Z

spelling

Glenn: +cats

2011-10-21T18:56:54Z

+cats

82.113.123.4: /* Enhancing Security */

2007-10-14T23:01:38Z

‎Enhancing Security

68.167.189.55: /* Fail-over Scenarios */

2007-02-28T06:08:57Z

‎Fail-over Scenarios

213.84.156.173: /* Other considerations */

2007-01-29T20:55:56Z

‎Other considerations

Daniel15: /* Consolidation and Separation */ Minor updates

2006-12-16T00:49:16Z

‎Consolidation and Separation: Minor updates

Pabs: fix spelling errors

2006-12-15T15:40:27Z

fix spelling errors

Through: /* Other considerations */

2006-11-27T12:17:32Z

‎Other considerations

Through: /* Other considerations */

2006-11-27T12:16:45Z

‎Other considerations

← Older revision		Revision as of 21:56, 21 October 2011
Line 1:		Line 1:
		+	{{Languages\|Usage Scenarios}}
		+
	For many people, virtual server may look like a great toy: Very high geekness factor. It looks cool, but probably not for everyone. '''Wrong!'''		For many people, virtual server may look like a great toy: Very high geekness factor. It looks cool, but probably not for everyone. '''Wrong!'''

@@ Line 109: / Line 109: @@
 * [[Overview]]
-[[Category:Documentaion]]
+[[Category:Documentation]]
 [[Category:Community]]
 [[Category:Categories]]

← Older revision		Revision as of 18:56, 21 October 2011
Line 108:		Line 108:

	* [[Overview]]		* [[Overview]]
		+
		+	[[Category:Documentaion]]
		+	[[Category:Community]]
		+	[[Category:Categories]]

@@ Line 20: / Line 20: @@
 * Unreachable from the network.
-* Able to log messages from the virtual server in a secure way. The virtual server would be unable to change/erase the logs. Even a cracked virtual server would not be able the edit the log.
+* Able to log messages from the virtual server in a secure way. The virtual server would be unable to change/erase the logs. Even a cracked virtual server would not be able to edit the log.
 * Able to run intrusion detection facilities, potentially spying the state of the virtual server without being accessible or noticed. For example, tripwire could run there and it would be impossible to circumvent its operation or trick it.

@@ Line 46: / Line 46: @@
 == Fail-over Scenarios ==
-Pushing the limit a little further, replication technology could be used to keep an up-to-the-minute copy of the filesystem of a running virtual server. This would permit a very fast fail-over if the running server goes offline for whatever reason.
+Pushing the limit a little further, replication technology could be used to keep an up-to-the-minute copy of the filesystem of a running virtual server. This would permit a very fast [[fail-over]] if the running server goes offline for whatever reason.
 All the known methods to accomplish this, starting with network replication via rsync, or drbd, via network devices, or shared disk arrays, to distributed filesystems, can be utilized to reduce the down-time and improve overall efficiency.
 == Experimenting and Upgrading ==

@@ Line 93: / Line 93: @@
 == Other considerations ==
-* '''Virtual Private Servers are running on the same kernel as the host:''' Unlike other VM solutions, Linux-VServer does not require additional memory or processing power, in fact it may even reduce used memory due to the fact that multiple virtual servres may share the same files.
+* '''Virtual Private Servers are running on the same kernel as the host:''' Unlike other VM solutions, Linux-VServer does not require additional memory or processing power, in fact it may even reduce used memory due to the fact that multiple virtual servers may share the same files.
 * '''There are no special daemons running:''' A VPS running crond, sshd, httpd and sendmail uses the same resources as a normal Linux server running these services.

@@ Line 5: / Line 5: @@
 == Consolidation and Separation ==
-As the hardware evolves, it is tempting to put more and more tasks on a server. Though Linux could reliably handle it, at some point, you will end up with too much stuff and people fiddling in the same box that you worry about updating things.
+As the hardware evolves, it is tempting to put more and more tasks on a server. Though Linux could reliably handle it, at some point, you will end up with too much stuff and people fiddling in the same box that you worry about updating things. Additionally, separating different or similar services which otherwise would interfere with each other, either because they are poorly designed or because they are simply incapable of peaceful coexistence for whatever reason, may often be complex or even impossible.
-Additionally separating different or similar services which otherwise would interfere with each other, either because they are poorly designed or because they are simply incapable of peaceful coexistence for whatever reason, may often be complex or even impossible.
+The Linux-VServer project addresses this issue. The same box is able to run multiple virtual servers and each one does the job it is supposed to do. If you need to upgrade to PHP 5 for a given project, you can do so, and only that one project is affected.
-The Linux-VServer project addresses this issue. The same box is able to run multiple virtual servers 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 that project is affected.
+Also, you can give the root password of a virtual server to an administrator for that virtual server and he/she will be able to perform updates, restart services and so on without having to know about every other project hosted on the same server. This allows a clever provider to sell Virtual Private Servers, which uses less resources than other virtualization techniques, which in turn allows to put more units on a single machine.
-−
-Also, you can give the root password of a virtual server to the administrator of one virtual server and he will be able to perform updates, restart services and so on without having to know about every other project hosted on the same server.
-−
 This allows a clever provider to sell Virtual Private Servers, which uses less resources than other virtualization techniques, which in turn allows to put more units on a single machine.
 The list of providers doing so is relatively long, and so this is rightfully considered the main area of application. See [[VServer Hosting]] for a (probably incomplete) list of companies providing Virtual Private Servers based on the Linux-VServer technology.

@@ Line 29: / Line 29: @@
 Another option is to put the firewall in a virtual server, and pull in the DMZ, containing each service in a separate VPS. On proper configuration, this setup can reduce the number of required machines drastically, without impacting performance.
-== Resource Independance ==
+== Resource Independence ==
 Since virtual servers are only guests on the hardware they are using, they are not aware of the specifics: they do not contain disk configurations, kernels or network configurations.
@@ Line 93: / Line 93: @@
 * 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. Still each one has its pecularities and probably flaws. For example, one distribution is doing a great job on security but is not delivering the latest and greatest PHP. Now because you have decided to use this distribution for some projects, using virtual servers does not prevent you from using another distribution for other projects or even a second virtual server for existing projects.
+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. Still each one has its peculiarities and probably flaws. For example, one distribution is doing a great job on security but is not delivering the latest and greatest PHP. Now because you have decided to use this distribution for some projects, using virtual servers does not prevent you from using another distribution for other projects or even a second virtual server for existing projects.
 == Other considerations ==

@@ Line 108: / Line 108: @@
 * '''Admin tools work inside a vserver as usual''': A vserver feels like a real server from within and can be used in the same ways.
 == See Also ==
 * [[Overview]]