Demo scripts Virtuozzo - Revision history

Sergey Bronnikov: add criu demoes

2015-10-13T08:28:59Z

add criu demoes

Sergey Bronnikov: criu inside jslinux

2015-08-06T19:32:44Z

criu inside jslinux

Sergey Bronnikov: add useful links

2015-08-02T21:19:56Z

add useful links

Sergey Bronnikov: Update demo "Full container lifecycle"

2015-08-02T19:10:36Z

Update demo "Full container lifecycle"

Sergey Bronnikov: add P.Haul demos

2015-07-30T13:34:09Z

add P.Haul demos

Sergey Bronnikov: docker inside CT

2015-07-23T20:32:19Z

docker inside CT

Sergey Bronnikov: initial list of demo scripts

2015-07-23T13:17:05Z

initial list of demo scripts

New page

{{Virtuozzo}}

The following demo scripts (scenarios) can be used to show advantages of Virtuozzo.

== Full container lifecycle ==

Create a container, set an IP, start, add a user, enter, exec, show
<code>ps -axf</code> output inside the container, stop, and destroy.
It should take about 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:

# CT=123
# IP=10.1.1.123
# sed -i "/$IP /d" ~/.ssh/
# time vzctl create $CT --ostemplate fedora-core-5-i386-default
# vzctl set $CT --ipadd $IP --hostname newCT --save
# vzctl start $CT
# vzctl exec $CT ps axf
# vzctl set $CT --userpasswd guest:secret --save
# ssh guest@$IP
[newCT]# ps axf
[newCT]# logout
# vzctl stop $CT
# vzctl destroy $CT

== Massive container creation ==

Create/start 50 or 100 containers in a shell loop. Shows fast deployment
and high density.

Here are the example commands needed:

<pre>
# time for ((CT=200; CT<250; CT++)); do \
> time vzctl create $CT --ostemplate fedora-core-9-i386; \
> vzctl start $CT; \
> done
</pre>

== Massive container load ==

Use containers from the previous item — load those by <code>ab</code> or
<code>http_load</code>. This demo shows that multiple containers are working
just fine, with low response time etc.

<pre>
# for ((CT=200; CT<250; CT++)); do \
> vzctl set $CT --ipadd 10.1.1.$CT --save; \
> done
</pre>

On another machine:

<pre>
# rpm -ihv http_load
#
</pre>
FIXME: http_load commands

== 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 container and
<code>vncclient</code> to connect to it, then run
<code>xscreensaver-demo</code>, choose a suitable screensaver (eye-candy but
not too CPU aggressive) and while the picture is moving start a live
migration. You'll see that <code>xscreensaver</code> stalls for a few
seconds but then continues to run — on another machine! That looks amazing,
to say at least.

FIXME: commands, setup, VNC template.

=== CRIU (Checkpoint and Restore In Userspace ===

* [https://github.com/tych0/presentations/blob/master/ods2014.md Migration of Doom inside container inside LXC container]
* [http://criu.org/Docker Checkpoint and Restore of Docker container]
* [https://github.com/jpetazzo/critmux CRIU + tmux]
* [http://criu.org/Simple_loop Simple loop]
* [http://criu.org/Asciinema CRIU screencasts]

== Resource management ==
Below scenarios aims to show how OpenVZ resource management works.

=== [[UBC]] protection ===

==== fork() bomb ====
<pre>
# while [ true ]; do \
> while [ true ]; do \
> echo " " > /dev/null;
> done &
> done
</pre>

We can see that the number of processes inside container will not be growing.
We will see only the increase of <code>numproc</code> and/or
<code>kmemsize</code> fail counters in <code>/proc/user_beancounters</code>.

==== dentry cache eat up ====
FIXME

=== CPU scheduler ===

{{Warning|CPU weights only works in stable kernels.}}

Create 3 containers:
<pre>
# vzctl create 101
# vzctl create 102
# vzctl create 103
</pre>

Set container weights:
<pre>
# vzctl set 101 --cpuunits 1000 --save
# vzctl set 102 --cpuunits 2000 --save
# vzctl set 103 --cpuunits 3000 --save
</pre>

We set next CPU sharing <code>CT101 : CT102 : CT103 = 1 : 2 : 3</code>

Start containers:
<pre>
# vzctl start 101
# vzctl start 102
# vzctl start 103
</pre>

Run busy loops in all containers:
<pre>
# vzctl enter 101
[ve101]# while [ true ]; do true; done
# vzctl enter 102
[ve102]# while [ true ]; do true; done
# vzctl enter 103
[ve103]# while [ true ]; do true; done
</pre>

Check in top that sharing works:
<pre>
# top
COMMAND %CPU
bash 48.0
bash 34.0
bash 17.5
</pre>

So, we see that CPU time is given to container in proportion ~ 1 : 2 : 3.

Now start some more busy loops. CPU distribution should remain the same.

=== Disk quota ===
<pre>
# vzctl set CTID --diskspace 1048576:1153434 --save
# vzctl start CTID
# 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>

[[Category:Events‏‎]]

← Older revision		Revision as of 08:28, 13 October 2015
Line 95:		Line 95:

	* [http://criu.org/Asciinema CRIU screencasts]		* [http://criu.org/Asciinema CRIU screencasts]
		+	* [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
		+	* [https://github.com/ianmiell/shutit-criu Live migration of Docker container inside Vagrant box]

	=== P.Haul ===		=== P.Haul ===

@@ Line 189: / Line 189: @@
 * [https://www.youtube.com/c/OpenVZorg OpenVZ demo on Youtube]
 * [[Screencasts|Virtuozzo screencasts]]
 [[Category:Events‏‎]]

@@ Line 27: / Line 27: @@
   # prlctl destroy $NAME
-== Massive container creation ==
+== Multiple containers creation ==
-Create/start 50 or 100 containers in a shell loop. Shows fast deployment
+Create/start 10 containers in a shell loop.
 Here are the example commands needed:
 <pre>
-# time for ((CT=200; CT<250; CT++)); do \
+# time for ((CT=100; CT<110; CT++)); do \
->  time prlctl create $CT --ostemplate centos-6-x86_64 --vm-type=ct; \
+  time prlctl create $CT --ostemplate centos-6-x86_64 --vmtype=ct; \
->  prlctl start $CT; \
+  prlctl start $CT; \
-> done
+  done
 </pre>
@@ Line 49: / Line 48: @@
 <pre>
 # for ((CT=200; CT<250; CT++)); do \
->  vzctl set $CT --ipadd 10.1.1.$CT --save; \
+  prlctl set $CT --ipadd 10.1.1.$CT/24; \
-> done
+  done
 </pre>
@@ Line 62: / Line 61: @@
 == Live migration ==
 If you have two boxes, do <code>vzmigrate --online</code> from one box
@@ Line 74: / Line 75: @@
 FIXME: commands, setup, VNC template.
-=== CRIU (Checkpoint and Restore In Userspace ===
+=== CRIU (Checkpoint and Restore In Userspace) ===
 * [https://github.com/tych0/presentations/blob/master/ods2014.md Migration of Doom inside container inside LXC container]
 * [http://criu.org/Docker Checkpoint and Restore of Docker container]
 * [https://github.com/jpetazzo/critmux CRIU + tmux]
-* [http://criu.org/Simple_loop Simple loop]
 * [http://criu.org/Asciinema CRIU screencasts]
 * [https://github.com/xemul/p.haul/blob/master/test/mtouch/HOWTO P.Haul HOWTO]
 * [https://github.com/xemul/p.haul/wiki/Live-migrating-OVZ-mainstream-container Live migrating OVZ mainstream container]
-== Docker inside CT ==
+[[Docker_inside_CT]]
 == Resource management ==
@@ Line 95: / Line 113: @@
 <pre>
 # while [ true ]; do \
->     while [ true ]; do \
+     while [ true ]; do \
->         echo " " > /dev/null;
+         echo " " > /dev/null;
->     done &
+     done &
-> done
+ done
 </pre>
@@ Line 109: / Line 127: @@
 === CPU scheduler ===
 Create 3 containers:
 <pre>
-# vzctl create 101
+# prlctl create 101
-# vzctl create 102
+# prlctl create 102
-# vzctl create 103
+# prlctl create 103
 </pre>
 Set container weights:
 <pre>
-# vzctl set 101 --cpuunits 1000 --save
+# prlctl set 101 --cpuunits 1000
-# vzctl set 102 --cpuunits 2000 --save
+# prlctl set 102 --cpuunits 2000
-# vzctl set 103 --cpuunits 3000 --save
+# prlctl set 103 --cpuunits 3000
 </pre>
@@ Line 130: / Line 146: @@
 Start containers:
 <pre>
-# vzctl start 101
+# prlctl start 101
-# vzctl start 102
+# prlctl start 102
-# vzctl start 103
+# prlctl start 103
 </pre>
 Run busy loops in all containers:
 <pre>
-# vzctl enter 101
+# prlctl enter 101
 [ve101]# while [ true ]; do true; done
-# vzctl enter 102
+# prlctl enter 102
 [ve102]# while [ true ]; do true; done
-# vzctl enter 103
+# prlctl enter 103
 [ve103]# while [ true ]; do true; done
 </pre>
@@ Line 160: / Line 176: @@
 === Disk quota ===
 <pre>
-# vzctl set CTID --diskspace 1048576:1153434 --save
+# prlctl set CTID --diskspace 1048576:1153434 --save
-# vzctl start CTID
+# prlctl start CTID
-# vzctl enter CTID
+# prlctl enter CTID
 [ve]# dd if=/dev/zero of=/tmp/tmp.file bs=1048576 count=1000
 dd: writing `/tmp/tmp.file': Disk quota exceeded
 </pre>
 [[Category:Events‏‎]]

@@ Line 13: / Line 13: @@
 Here are the example commands needed:
-  # CT=123
+  # NAME=vz
-  # IP=10.1.1.123
+  # IP=10.1.1.123/24
   # sed -i "/$IP /d" ~/.ssh/
-  # time vzctl create $CT --ostemplate fedora-core-5-i386-default
+  # time prlctl create $NAME --ostemplate centos-6-x86_64 --vmtype=ct
-  # vzctl set $CT --ipadd $IP --hostname newCT --save
+  # prlctl set $NAME --ipadd $IP --hostname $NAME
-  # vzctl start $CT
+  # prlctl start $NAME
-  # vzctl exec $CT ps axf
+  # prlctl exec $NAME ps axf
-  # vzctl set $CT --userpasswd guest:secret --save
+  # prlctl set $NAME --userpasswd guest:secret
   # ssh guest@$IP
-  [newCT]# ps axf
+  [vz]# ps axf
-  [newCT]# logout
+  [vz]# logout
-  # vzctl stop $CT
+  # prlctl stop $NAME
-  # vzctl destroy $CT
+  # prlctl destroy $NAME
 == Massive container creation ==
@@ Line 36: / Line 36: @@
 <pre>
 # time for ((CT=200; CT<250; CT++)); do \
->  time vzctl create $CT --ostemplate fedora-core-9-i386; \
+>  time prlctl create $CT --ostemplate centos-6-x86_64 --vm-type=ct; \
->  vzctl start $CT; \
+>  prlctl start $CT; \
 > done
 </pre>