UBC consistency check - Revision history

Kir: highlight vzcfgvalidate

2014-11-23T22:35:34Z

highlight vzcfgvalidate

Kir: more ways to check current configuration -- with links!

2013-10-01T20:35:55Z

more ways to check current configuration -- with links!

Grin: code

2013-01-29T10:15:34Z

code

Fayette at 11:52, 25 May 2008

2008-05-25T11:52:58Z

Botinki Kira: Robot: Automated text replacement (-Virtual Environment +container)

2008-03-11T10:40:49Z

Robot: Automated text replacement (-Virtual Environment +container)

Kir: fix ubc proc file name

2008-01-09T00:38:37Z

fix ubc proc file name

Kir: use template:man

2006-11-05T19:04:44Z

use template:man

Hvdkamer at 14:54, 30 August 2006

2006-08-30T14:54:02Z

Kir: Added UBC toc

2006-08-22T07:25:51Z

Added UBC toc

Kir: added to UBC category

2006-08-22T06:48:46Z

added to UBC category

@@ Line 4: / Line 4: @@
 Configuration of resource control parameters for a container
-is invalid if these constraints are not satisfied. The best way to ensure the
+is invalid if these constraints are not satisfied. '''The best way to ensure the
-validity of the configuration is to use the {{man|vzcfgvalidate|8}} utility.
+validity of the configuration is to use the {{man|vzcfgvalidate|8}} utility.'''
 All the interdependencies discussed below and their importance are summarized in [[UBC interdependencies table]].

@@ Line 10: / Line 10: @@
 The configured limits can be checked through
-* <code>/proc/user_beancounters</code> interface;
+* /[[proc/user_beancounters]] interface;
-* container configuration files in <code>/etc/vz/conf/</code> directory.
+* [[BC proc entries|/proc/bc/]] interface;

← Older revision		Revision as of 10:15, 29 January 2013
Line 84:		Line 84:

	should be maintained for each parameter.		should be maintained for each parameter.
		+
		+	== Code ==
		+	See [[User:Grin/openvz checker.pl]] for a contributed code to check the consistency.

	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]

@@ Line 5: / Line 5: @@
 Configuration of resource control parameters for a container
 is invalid if these constraints are not satisfied. The best way to ensure the
-validity of the configuration is to use {{man|vzcfgvalidate|8}} utility.
+validity of the configuration is to use the {{man|vzcfgvalidate|8}} utility.
 All the interdependencies discussed below and their importance are summarized in [[UBC interdependencies table]].
@@ Line 19: / Line 19: @@
 (<code>avnumproc</code> here stands for the expected average number of processes).
-This constraint is important for reliable work of applications in the
+This constraint is important for applications to work reliably in the
 container.
-If it is not satisfied, applications will start to fail at the middle of
+If it is not satisfied, applications will start to fail in the middle of
-operations instead of failing at the moment of spawning more processes,
+operations instead of failing while spawning more processes
-and the application abilities to handle resource shortage will be very
+and the application's ability to handle resource shortage will be very
 limited.
@@ Line 49: / Line 49: @@
 Selecting the left side equal to the right side in the inequalities
 above ensures minimal performance of network communications.
-Increasing the left side will increase performance to certain extent.
+Increasing the left side will increase performance to a certain extent.
-== UDP socket buffers should be big enough if the system is not tight on memory ==
+== UDP socket buffers should be large enough if the system is not tight on memory ==
 <math>dgramrcvbuf_{bar} \ge 129KB</math>
@@ Line 57: / Line 57: @@
 These constraints are desired, but not essential.
-Big enough buffers for UDP sockets improve reliability of datagram delivery.
+Large enough buffers for UDP sockets improve reliability of datagram delivery.
 However, note that if the UDP traffic is so bursty that it needs larger
 buffers, the datagrams will likely be lost not because of resource control
 limits, but because of other memory and performance limitations.
-== Number of file limit should be adequate for the expected number of processes ==
+== Number of files limit should be adequate for the expected number of processes ==
 <math>numfile \ge avnumproc \cdot 32</math>
-Note that each process after <code>execve(2)</code> system call
+Note that each process after a <code>execve(2)</code> system call
 requires a file for each loaded shared library.
-Too low <code>numfile</code> limit will increase the chances of failures
+A too low <code>numfile</code> limit will increase the chances of failures
-during <code>execve(2)</code> call with diagnostics not clear
+during <code>execve(2)</code> calls with error messages that are not clear
-for the users.
+to the users.
 == The limit on the total size of <code>dentry</code> and <code>inode</code> structures locked in memory should be adequate for allowed number of files ==
@@ Line 75: / Line 75: @@
 <math>dcachesize_{bar} \ge numfile \cdot 384\ \rm(bytes)</math>
-Too low <code>dcachesize</code> limit will increase the chances of
+A too low <code>dcachesize</code> limit will increase the chances of
-file operation refusals not expected by applications.
+file operation refusals resulting in unexpected application failures.
 == Barrier should be less or equal than limit ==

@@ Line 3: / Line 3: @@
 System resource control parameters have certain interdependencies. Constraints on the parameter settings are listed below. Indexes <code>bar</code> and <code>lim</code> in the formulae below mean the barrier and the limit of the parameters, respectively.
-Configuration of resource control parameters for a Virtual Environment
+Configuration of resource control parameters for a container
 is invalid if these constraints are not satisfied. The best way to ensure the
 validity of the configuration is to use {{man|vzcfgvalidate|8}} utility.
@@ Line 11: / Line 11: @@
 The configured limits can be checked through
 * <code>/proc/user_beancounters</code> interface;
-* Virtual Environment configuration files in <code>/etc/vz/conf/</code> directory.
+* container configuration files in <code>/etc/vz/conf/</code> directory.
@@ Line 20: / Line 20: @@
 This constraint is important for reliable work of applications in the
-Virtual Environment.
+container.
 If it is not satisfied, applications will start to fail at the middle of
 operations instead of failing at the moment of spawning more processes,

@@ Line 1: / Line 1: @@
 {{UBC toc}}
-System resource control parameters have certain interdependencies. Constraints on the parameter settings are listed below. Indexes <code>bar and <code>lim</code> in the formulae below mean the barrier and the limit of the parameters, respectively.
+System resource control parameters have certain interdependencies. Constraints on the parameter settings are listed below. Indexes <code>bar</code> and <code>lim</code> in the formulae below mean the barrier and the limit of the parameters, respectively.
 Configuration of resource control parameters for a Virtual Environment

@@ Line 1: / Line 1: @@
 System resource control parameters have certain interdependencies. Constraints on the parameter settings are listed below. Indexes <code>bar and <code>lim</code> in the formulae below mean the barrier and the limit of the parameters, respectively.
@@ Line 83: / Line 85: @@
 should be maintained for each parameter.
 [[Category:Troubleshooting]]

@@ Line 83: / Line 83: @@
 should be maintained for each parameter.
-[[Category:Kernel]]
+[[Category:UBC]]
 [[Category:Troubleshooting]]