Demo scripts - Revision history

Sergey Bronnikov: added category

2015-06-07T06:32:51Z

added category

Kir: VE->CT, formatting, some corrections/additions

2009-02-06T17:22:17Z

VE->CT, formatting, some corrections/additions

Kir: formatting, articles /* Full VE lifecycle */

2006-11-13T11:42:03Z

formatting, articles ‎Full VE lifecycle

Major: /* Massive VE load */

2006-10-30T16:59:33Z

‎Massive VE load

Major: /* Massive VE creation */

2006-10-30T16:13:34Z

‎Massive VE creation

Major: /* fork() bomb */

2006-10-30T16:08:06Z

‎fork() bomb

Major: /* CPU scheduler */

2006-10-30T14:30:52Z

‎CPU scheduler

Major: /* CPU scheduler */

2006-10-27T12:02:30Z

‎CPU scheduler

Major: /* Disk quota */

2006-10-27T10:47:13Z

‎Disk quota

Major: /* edit fork() bomb */

2006-10-27T10:04:23Z

‎edit fork() bomb

← Older revision		Revision as of 06:32, 7 June 2015
Line 151:		Line 151:
	dd: writing `/tmp/tmp.file': Disk quota exceeded		dd: writing `/tmp/tmp.file': Disk quota exceeded
	</pre>		</pre>
		+
		+	[[Category:Events‏‎]]

@@ Line 1: / Line 1: @@
 The following demo scripts (scenarios) can be used to show advantages of OpenVZ.
-== Full VE lifecycle ==
+== Full container lifecycle ==
-Create a VE, set an IP, start, add a user, enter, exec, show <code>ps -axf</code> output inside the VE, stop, and destroy. It should take two minutes ("compare that to a time you need to deploy a new (non-virtual) server!"). During the demonstration, describe what's happening and why.
+Create a container, set an IP, start, add a user, enter, exec, show
 Here are the example commands needed:
-  # VE=123
+  # CT=123
   # IP=10.1.1.123
   # sed -i "/$IP /d" ~/.ssh/
-  # time vzctl create $VE --ostemplate fedora-core-5-i386-default
+  # time vzctl create $CT --ostemplate fedora-core-5-i386-default
-  # vzctl set $VE --ipadd $IP --hostname newVE --save
+  # vzctl set $CT --ipadd $IP --hostname newCT --save
-  # vzctl start $VE
+  # vzctl start $CT
-  # vzctl exec $VE ps axf
+  # vzctl exec $CT ps axf
-  # vzctl set $VE --userpasswd guest:secret --save
+  # vzctl set $CT --userpasswd guest:secret --save
   # ssh guest@$IP
-  [newVE]# ps axf
+  [newCT]# ps axf
-  [newVE]# logout
+  [newCT]# logout
-  # vzctl stop $VE
+  # vzctl stop $CT
-  # vzctl destroy $VE
+  # vzctl destroy $CT
-== Massive VE creation ==
+== Massive container creation ==
-Create/start 50 or 100 VEs in a shell loop. Shows fast deployment and high density.
+Create/start 50 or 100 containers in a shell loop. Shows fast deployment
 Here are the example commands needed:
 <pre>
-# time for ((VE=200; VE<250; VE++)); do \
+# time for ((CT=200; CT<250; CT++)); do \
->  time vzctl create $VE --ostemplate fedora-core-5-i386-default; \
+>  time vzctl create $CT --ostemplate fedora-core-9-i386; \
->  vzctl start $VE; \
+>  vzctl start $CT; \
 > done
 </pre>
-== Massive VE load ==
+== Massive container load ==
-Use VEs from previous item — load those by <code>ab</code> or <code>http_load</code>. This demo shows that multiple VEs are working just fine, with low response time etc.
+Use containers from the previous item — load those by <code>ab</code> or
 <pre>
-# for ((VE=200; VE<250; VE++)); do \
+# for ((CT=200; CT<250; CT++)); do \
->  vzctl set $VE --ipadd 10.1.1.$VE --save; \
+>  vzctl set $CT --ipadd 10.1.1.$CT --save; \
 > done
 </pre>
 On another machine:
 <pre>
 # rpm -ihv http_load
@@ Line 52: / Line 61: @@
 == Live migration ==
-If you have two boxes, do "<code>vzmigrate --online</code>" from one box to another. You can use, say, <code>xvnc</code> in a VE and <code>vncclient</code> to connect to it, then run <code>xscreensaver-demo</code> and while the picture is moving do a live migration. You'll show <code>xscreensaver</code> stalls for a few seconds but then keeps running — on another machine! That looks amazing, to say at least.
+If you have two boxes, do <code>vzmigrate --online</code> from one box
-FIXME: commands, setup, vnc template.
+FIXME: commands, setup, VNC template.
 == Resource management ==
@@ Line 69: / Line 85: @@
 > done
 </pre>
-We can see that number of processes inside VE will not be grow up. We will see only increase of <code>numproc</code> or <code>kmemsize</code> fail counters in <code>/proc/user_beancounters</code>.
 ==== dentry cache eat up ====
@@ Line 75: / Line 94: @@
 === CPU scheduler ===
-Create 3 VEs:
 <pre>
 # vzctl create 101
@@ Line 82: / Line 104: @@
 </pre>
-Set VEs weights:
+Set container weights:
 <pre>
 # vzctl set 101 --cpuunits 1000 --save
@@ Line 89: / Line 111: @@
 </pre>
-We set next cpu sharing <code>VE101 : VE102 : VE103 = 1 : 2 : 3</code>
+We set next CPU sharing <code>CT101 : CT102 : CT103 = 1 : 2 : 3</code>
-Run VEs:
+Start containers:
 <pre>
 # vzctl start 101
@@ Line 98: / Line 120: @@
 </pre>
-Run busy loops in VEs:
+Run busy loops in all containers:
 <pre>
 # vzctl enter 101
@@ Line 117: / Line 139: @@
 </pre>
-So, we see that CPU time is given to VEs in proportion  ~ 1 : 2 : 3.
+So, we see that CPU time is given to container in proportion ~ 1 : 2 : 3.
 === Disk quota ===
 <pre>
-# vzctl set VEID --diskspace 1048576:1153434 --save
+# vzctl set CTID --diskspace 1048576:1153434 --save
-# vzctl start VEID
+# vzctl start CTID
-# vzctl enter VEID
+# vzctl enter CTID
 [ve]# dd if=/dev/zero of=/tmp/tmp.file bs=1048576 count=1000
 dd: writing `/tmp/tmp.file': Disk quota exceeded
 </pre>

@@ Line 3: / Line 3: @@
 == Full VE lifecycle ==
-Create VE, set IP, start, add user, enter, exec, show ps -axf output inside VE, stop, and destroy. It should take two minutes ("compare that to a time you need to deploy a new (non-virtual) server!"). During the demonstration, describe what's happening and why.
+Create a VE, set an IP, start, add a user, enter, exec, show <code>ps -axf</code> output inside the VE, stop, and destroy. It should take two minutes ("compare that to a time you need to deploy a new (non-virtual) server!"). During the demonstration, describe what's happening and why.
 Here are the example commands needed:

@@ Line 38: / Line 38: @@
 Use VEs from previous item — load those by <code>ab</code> or <code>http_load</code>. This demo shows that multiple VEs are working just fine, with low response time etc.
-FIXME: commands, ab/http_load setup.
+<pre>
 == Live migration ==

@@ Line 27: / Line 27: @@
 Here are the example commands needed:
- # VE=200
+<pre>
- # time while [ $VE -lt 250 ]; do \
+# time for ((VE=200; VE<250; VE++)); do \
- >  time vzctl create $VE --ostemplate fedora-core-5-i386-default; \
+>  time vzctl create $VE --ostemplate fedora-core-5-i386-default; \
- >  vzctl start $VE; \
+>  vzctl start $VE; \
- >  let VE++; \
+> done
- > done
+</pre>
 == Massive VE load ==

← Older revision		Revision as of 10:47, 27 October 2006
Line 67:		Line 67:

	=== Disk quota ===		=== Disk quota ===
−	~~FIXME~~	+	<pre>
		+	# vzctl set VEID --diskspace 1048576:1153434 --save
		+	# vzctl start VEID
		+	# vzctl enter VEID
		+	[ve]# dd if=/dev/zero of=/tmp/tmp.file bs=1048576 count=1000
		+	dd: writing `/tmp/tmp.file': Disk quota exceeded
		+	</pre>

@@ Line 52: / Line 52: @@
 ==== fork() bomb ====
-FIXME
+<pre>
 ==== dentry cache eat up ====