OpenVZ Virtuozzo Containers Wiki - User contributions [en]

IRC

2022-02-24T15:09:49Z

Dowdle:

<translate>

If you want to talk to the OpenVZ users and sometimes developers live, we can usually be found on the #openvz channel on irc.freenode.net.

== Some simple rules == 


* Please note that this is a volunteer service, so be polite - you won't get much help if being rude.


* Please do a research before asking questions. Search this wiki, the [[mailing lists]] and [[forum:|forum]] for questions that were asked in the past.


* Also remember that the level of activity varies, so if you don't get help at once, stay online for a while. People will answer if they can, or ask for more details if they need it. Repeating the same question again and again won't help.


* Don't send private messages to people unless they have asked you to — it's considered rude.


* Chances are that people had the same challenges as you at one time — so following the above points will ensure a good experience, both for you and for us.

== Connecting == 


[irc://irc.freenode.net/openvz Click here] to connect with an IRC client (requires IRC client installed).

Many users of the freenode IRC network have since moved to the libra.chat network, so see #openvz there also.


To connect with an IRC client, you need one installed. Here are our IRC client recommendations:


* Via web browser: [https://webchat.freenode.net/?channels=#openvz Freenode webchat] or [https://kiwiirc.com/client/irc.freenode.net/#openvz Kiwi IRC client] or [https://web.libera.chat/#openvz Libra.chat webchat]
* For Linux: [http://www.xchat.org/ XChat]
* For Mac OS X: [http://www.colloquy.info/ Colloquy]
* For Windows: [http://www.mirc.com/ mIRC]

== IRC logs == 


It is possible to find all conversation in the past. IRC logs are saved using [https://botbot.me/freenode/openvz/ botbot.me].
You will never miss an interesting discussion :)
</translate>

[[Category: Communication]]

Success stories

2015-10-26T16:57:57Z

Dowdle: /* MontanaLinux */

== Atlassian ==



[[Image:Atlassian-logo.png|right|250px]]

Atlassian is an Australian enterprise software company that develops products geared towards software developers and project managers. It is best known for its issue tracking application, JIRA, and its team collaboration product, Confluence. Atlassian serves over 35,000 customers globally, including 85 of the Fortune 100.

* Atlassian Summit 2012, San Francisco - "[http://www.slideshare.net/GoAtlassian/inside-the-atlassian-ondemand-private-cloud Inside the Atlassian OnDemand Private Cloud]"
* Puppet Camp Tokyo 2014 - "[http://www.slideshare.net/PuppetLabs/1-m-pluginspuppetcamptokyo2014 Fireballs, ice bats and 1,000,000 plugins: a story of continuous delivery]"

''George Barnett, Atlassian''

== FastVPS ==

[[Image:Fastvps logotype.png|right|255px]]

Our company has been using OpenVZ to provide services for customers for nearly 9 years. We are very pleased with it, as it enables us to provide maximum computing capabilities to our customers with almost no overhead. Compared with other solutions, OpenVZ has a number of competitive advantages, including the ploop file system and live migration of containers. We are truly grateful to the OpenVZ team for continuous support and wish the project further success! -- ''Pavel Odintsov, CTO, FastVPS Eesti OU''

* Moscow Virtualization Meetup, Moscow - "[http://www.youtube.com/watch?v=yu6Wih_znSM Использование контейнеризации в среде массового хостинга]"

== MontanaLinux ==

[http://www.montanalinux.org/ MontanaLinux.org] is a hub for Montana area Linux User Groups and has been using OpenVZ since 2005. MontanaLinux.org is primarily maintained by Scott Dowdle and a handful of other Montana area LUG members.

Scott's day job is Systems Administrator for the [http://www.cs.montana.edu/ Computer Science Department] at Montana State University Bozeman in Bozeman, Montana. The CS Dept. has been using OpenVZ for a handful of infrastructure servers for close to 10 years. Especially appreciated is the SAN-less live migration feature.

OpenVZ is also used in the CSCI 351 Systems Administration class where every student is given an OpenVZ container to manage and do their assignments in. Giving each student a system they can be "root" of provides them with valuable hands-on experience. OpenVZ works very well in educational environments.

== Parallels ==



[[Image:Parallels-logo.png|right|250px]]

We, at Parallels IT services, maintain the entire company infrastructure and actively use Linux containers for all provided services. We have chosen Virtuozzo containers for the high container density per server and for ease of administration. -- ''Pavel Gashev, System Administrator, Parallels Inc.''

[http://parallels.com/about/ Parallels], a global leader in cross-platform solutions, makes it simple for customers to use and access the applications and files they need on any device or operating system. We help both businesses and individuals take advantage of the best technology out there, whether it’s Mac, Windows, iOS, Android, or the cloud.

== Pixar Animation Studios ==

[[Image:Pixar logo.svg|right|250px]]

[http://www.pixar.com/about Pixar Animation Studios] located in Emeryville, California. Pixar Animation Studios has created
acclaimed animated feature and short films for over 25 years. Pixar is also home to the RenderMan line of software products.

== Travis CI ==


[[Image:TravisCI-logo.png|right|180px]]

"We’re booting 120,000 containers per day on OpenVZ, it’s okay I guess." -- [https://twitter.com/roidrage/status/517776484342452226 Mathias Meyer, CEO] of Travis CI

== Yandex ==


[[Image:Yandex eng logo.png|right|140px]]

[https://company.yandex.com/ Yandex] is one of the largest internet companies in Europe, operating Russia’s most popular search engine and its most visited website.

* "[http://www.slideshare.net/profyclub/ss-5815331 Танки в Лунапарке: нагрузочное тестирование в Яндексе]"

== WarGaming.Net ==

[[Image:Wargaming.net logo.png|right|180px]]

Wargaming Public Co Ltd is an international game developer and publisher. Primarily focused on TBS and RTS games, Wargaming switched to developing free-to-play online action games in 2009, and has since become one of the leaders in the market. The company's critical and commercial success came after the launch of its first online project, the military-themed team-based game World of Tanks.

== See also ==

* [[Partners]]
* [[Use cases]]
* [[Testimonials]]
* [[Hosting providers]]

Success stories

2015-10-26T16:07:10Z

Dowdle: Added sentence about hands-on experience for students

== Atlassian ==



[[Image:Atlassian-logo.png|right|250px]]

Atlassian is an Australian enterprise software company that develops products geared towards software developers and project managers. It is best known for its issue tracking application, JIRA, and its team collaboration product, Confluence. Atlassian serves over 35,000 customers globally, including 85 of the Fortune 100.

* Atlassian Summit 2012, San Francisco - "[http://www.slideshare.net/GoAtlassian/inside-the-atlassian-ondemand-private-cloud Inside the Atlassian OnDemand Private Cloud]"
* Puppet Camp Tokyo 2014 - "[http://www.slideshare.net/PuppetLabs/1-m-pluginspuppetcamptokyo2014 Fireballs, ice bats and 1,000,000 plugins: a story of continuous delivery]"

''George Barnett, Atlassian''

== FastVPS ==

[[Image:Fastvps logotype.png|right|255px]]

Our company has been using OpenVZ to provide services for customers for nearly 9 years. We are very pleased with it, as it enables us to provide maximum computing capabilities to our customers with almost no overhead. Compared with other solutions, OpenVZ has a number of competitive advantages, including the ploop file system and live migration of containers. We are truly grateful to the OpenVZ team for continuous support and wish the project further success! -- ''Pavel Odintsov, CTO, FastVPS Eesti OU''

* Moscow Virtualization Meetup, Moscow - "[http://www.youtube.com/watch?v=yu6Wih_znSM Использование контейнеризации в среде массового хостинга]"

== MontanaLinux ==

[http://www.montanalinux.org/ MontanaLinux.org] is a hub for Montana area Linux User Groups and has been using OpenVZ since 2005. MontanaLinux.org is primarily maintained by Scott Dowdle and a handful of other Montana area LUG members.

Scott's day job is Systems Administrator for the [http://www.cs.montana.edu/ Computer Science Department] at Montana State University Bozeman in Bozeman, Montana. The CS Dept. has been using OpenVZ for a handful of infrastructure servers for close to 10 years. OpenVZ is also used in the CSCI 351 Systems Administration class where every student is given an OpenVZ container to manage and do their assignments in. Giving each student a system they can be "root" of provides them with valuable hands-on experience. OpenVZ works very well in educational environments.

== Parallels ==



[[Image:Parallels-logo.png|right|250px]]

We, at Parallels IT services, maintain the entire company infrastructure and actively use Linux containers for all provided services. We have chosen Virtuozzo containers for the high container density per server and for ease of administration. -- ''Pavel Gashev, System Administrator, Parallels Inc.''

[http://parallels.com/about/ Parallels], a global leader in cross-platform solutions, makes it simple for customers to use and access the applications and files they need on any device or operating system. We help both businesses and individuals take advantage of the best technology out there, whether it’s Mac, Windows, iOS, Android, or the cloud.

== Pixar Animation Studios ==

[[Image:Pixar logo.svg|right|250px]]

[http://www.pixar.com/about Pixar Animation Studios] located in Emeryville, California. Pixar Animation Studios has created
acclaimed animated feature and short films for over 25 years. Pixar is also home to the RenderMan line of software products.

== Travis CI ==


[[Image:TravisCI-logo.png|right|180px]]

"We’re booting 120,000 containers per day on OpenVZ, it’s okay I guess." -- [https://twitter.com/roidrage/status/517776484342452226 Mathias Meyer, CEO] of Travis CI

== Yandex ==


[[Image:Yandex eng logo.png|right|140px]]

[https://company.yandex.com/ Yandex] is one of the largest internet companies in Europe, operating Russia’s most popular search engine and its most visited website.

* "[http://www.slideshare.net/profyclub/ss-5815331 Танки в Лунапарке: нагрузочное тестирование в Яндексе]"

== WarGaming.Net ==

[[Image:Wargaming.net logo.png|right|180px]]

Wargaming Public Co Ltd is an international game developer and publisher. Primarily focused on TBS and RTS games, Wargaming switched to developing free-to-play online action games in 2009, and has since become one of the leaders in the market. The company's critical and commercial success came after the launch of its first online project, the military-themed team-based game World of Tanks.

== See also ==

* [[Partners]]
* [[Use cases]]
* [[Testimonials]]
* [[Hosting providers]]

Success stories

2015-10-26T16:03:18Z

Dowdle: Added MontanaLinux

== Atlassian ==



[[Image:Atlassian-logo.png|right|250px]]

Atlassian is an Australian enterprise software company that develops products geared towards software developers and project managers. It is best known for its issue tracking application, JIRA, and its team collaboration product, Confluence. Atlassian serves over 35,000 customers globally, including 85 of the Fortune 100.

* Atlassian Summit 2012, San Francisco - "[http://www.slideshare.net/GoAtlassian/inside-the-atlassian-ondemand-private-cloud Inside the Atlassian OnDemand Private Cloud]"
* Puppet Camp Tokyo 2014 - "[http://www.slideshare.net/PuppetLabs/1-m-pluginspuppetcamptokyo2014 Fireballs, ice bats and 1,000,000 plugins: a story of continuous delivery]"

''George Barnett, Atlassian''

== FastVPS ==

[[Image:Fastvps logotype.png|right|255px]]

Our company has been using OpenVZ to provide services for customers for nearly 9 years. We are very pleased with it, as it enables us to provide maximum computing capabilities to our customers with almost no overhead. Compared with other solutions, OpenVZ has a number of competitive advantages, including the ploop file system and live migration of containers. We are truly grateful to the OpenVZ team for continuous support and wish the project further success! -- ''Pavel Odintsov, CTO, FastVPS Eesti OU''

* Moscow Virtualization Meetup, Moscow - "[http://www.youtube.com/watch?v=yu6Wih_znSM Использование контейнеризации в среде массового хостинга]"

== MontanaLinux ==

[http://www.montanalinux.org/ MontanaLinux.org] is a hub for Montana area Linux User Groups and has been using OpenVZ since 2005. MontanaLinux.org is primarily maintained by Scott Dowdle and a handful of other Montana area LUG members.

Scott's day job is Systems Administrator for the [http://www.cs.montana.edu/ Computer Science Department] at Montana State University Bozeman in Bozeman, Montana. The CS Dept. has been using OpenVZ for a handful of infrastructure servers for close to 10 years. OpenVZ is also used in the CSCI 351 Systems Administration class where every student is given an OpenVZ container to manage and do their assignments in. OpenVZ works very well in educational environments.

== Parallels ==



[[Image:Parallels-logo.png|right|250px]]

We, at Parallels IT services, maintain the entire company infrastructure and actively use Linux containers for all provided services. We have chosen Virtuozzo containers for the high container density per server and for ease of administration. -- ''Pavel Gashev, System Administrator, Parallels Inc.''

[http://parallels.com/about/ Parallels], a global leader in cross-platform solutions, makes it simple for customers to use and access the applications and files they need on any device or operating system. We help both businesses and individuals take advantage of the best technology out there, whether it’s Mac, Windows, iOS, Android, or the cloud.

== Pixar Animation Studios ==

[[Image:Pixar logo.svg|right|250px]]

[http://www.pixar.com/about Pixar Animation Studios] located in Emeryville, California. Pixar Animation Studios has created
acclaimed animated feature and short films for over 25 years. Pixar is also home to the RenderMan line of software products.

== Travis CI ==


[[Image:TravisCI-logo.png|right|180px]]

"We’re booting 120,000 containers per day on OpenVZ, it’s okay I guess." -- [https://twitter.com/roidrage/status/517776484342452226 Mathias Meyer, CEO] of Travis CI

== Yandex ==


[[Image:Yandex eng logo.png|right|140px]]

[https://company.yandex.com/ Yandex] is one of the largest internet companies in Europe, operating Russia’s most popular search engine and its most visited website.

* "[http://www.slideshare.net/profyclub/ss-5815331 Танки в Лунапарке: нагрузочное тестирование в Яндексе]"

== WarGaming.Net ==

[[Image:Wargaming.net logo.png|right|180px]]

Wargaming Public Co Ltd is an international game developer and publisher. Primarily focused on TBS and RTS games, Wargaming switched to developing free-to-play online action games in 2009, and has since become one of the leaders in the market. The company's critical and commercial success came after the launch of its first online project, the military-themed team-based game World of Tanks.

== See also ==

* [[Partners]]
* [[Use cases]]
* [[Testimonials]]
* [[Hosting providers]]

QA Team hardware

2015-03-12T15:58:10Z

Dowdle: Changed from User: to just name

== Why? ==

When developers receive testing results, look at bug reports, or discuss technical issues, they may ask you to submit the detailed information about configuration of your computer. This report includes things such as the type of CPU, the kind of memory, and other important hardware specifications. Adding your 'quick link' from here reduces the time which would be wasted if they need ask you to post up additional information, then you getting it and posting it up. It is much faster if you include your link in the bug report/discussion at the beginning. If they do not need it, they need not click on the link.

== How to add new configuration? ==

* Install this application:

rpm -Uvh http://mirror.symnds.com/distributions/gf/el/6/gf/x86_64/gf-release-6-6.gf.el6.noarch.rpm
yum install -y hwinfo.x86_64

* Run the command:

hwinfo > openvz_report.txt

* Add the output to http://pastebin.org service or create a [https://gist.github.com gist] and add a link to it at the '''top''' of the below table. This [https://raw.githubusercontent.com/chilicuil/learn/master/python/pastebin Python script] may be helpful.

{| class="wikitable sortable"
!Vendor
!Model
!Type
!Full specification
!Person
|-
|Supermicro
|na
|Server
|[https://gist.github.com/ligurio/7654ce5e3714f604c32e Specification]
|[[User:Sergey Bronnikov]]
|-
|Intel
|na
|Desktop
|na
|[[User:Sergey Bronnikov]]
|-
|Depo
|na
|Desktop
|na
|[[User:Sergey Bronnikov]]
|-
|Dell
|PowerEdge R510
|Rackmount Server
|[http://www.montanalinux.org/files/specs-openvz3-cs-montana-edu.txt dmidecode output]
|Scott Dowdle
|}

[[Category: QA]]

QA Team hardware

2015-03-12T15:57:16Z

Dowdle:

QA Team hardware

2015-03-12T15:56:05Z

Dowdle: Added my system

QA Team members

2015-03-12T15:34:00Z

Dowdle: Corrected my URL

Please add configuration of your hardware to [[QA_Team_hardware|QA Team hardware]] once you have added yourself to the table below.

{| class="wikitable sortable"
!TZ
!Real name
!IRC name
!Involvement
!Native languages
!Website
|-
|UTC+4
|Sergey Bronnikov
|sergeyb
|vzkernel regression, new features testing
|Russian, English
![http://bronevichok.ru bronevichok.ru]
|-
|na
|Pavel Odintsov
|na
|new features testing
|Russian, English
![http://fastvps.ru fastvps.ru]
|-
|MDT
|Scott Dowdle
|dowdle
|vzkernel testing
|English
![http://www.montanalinux.org/ www.montanalinux.org]
|-

|}

[[Category: QA]]

QA Team members

2015-03-12T15:33:23Z

Dowdle: Added myself to the list

Ploop/Backup

2014-10-01T18:00:23Z

Dowdle: /* File-based backup */

[[File:Ploop-backup.png|300px|right|thumb|How backup via snapshot is done]]
This article explains how to do consistent backups for [[ploop]] containers, using ploop snapshot feature.

== Backup types ==
There are two ways of doing backups, both have their pros and cons.

* When doing an '''image backup''', one copies ploop image files directly. There can be only one big file, or maybe a few relatively big files. Copying a few big files (rather than a lot of small files) is faster because there's not too much metadata (file info) to be copied). Also, filesystem properties are fully preserving (since images containing the filesystem are copied).

* When doing a '''file backup''', one copies individual container' files. This is more suitable if you want selective backups (such as only some directories/files).

The following table summarizes pros and cons of both approaches.

{| class="wikitable"
! Characteristic
! Image
! File
|-
|| Incremental backups
| {{Yes}} || {{Yes-No}}{{H:title|Requires tools such as rsnapshot|*}}
|-
|| Selective backups
| {{No}} || {{Yes}}
|-
|| Faster full backup and restore
| {{Yes}} || {{No}}
|-
| Preserve filesystem properties
| {{Yes}} || {{No}}
|-
|| Compatible with pre-ploop backups
| {{No}} || {{Yes}}
|-
|| Restore individual files
| {{Yes}} || {{Yes}}
|}

== Image-based backup ==

Assuming you have a running container identified by <code>$CTID</code>. The following needs to be done:

<source lang="bash">
# Known snapshot ID
ID=$(uuidgen)
VE_PRIVATE=$(vzlist -H -o private $CTID)

# Take a snapshot without suspending a CT and saving its config
vzctl snapshot $CTID --id $ID --skip-suspend --skip-config

# Perform a backup using your favorite backup tool
# (cp is just an example)
cp $VE_PRIVATE/root.hdd/* /backup/destination

# Delete (merge) the snapshot
vzctl snapshot-delete $CTID --id $ID
</source>

The following script implements the commands above and allows - when stored as <code>vzbackup</code> - to backup your container by executing the script in the following way:

<code>./vzbackup 101 /backup/destination/</code>

The script removes older backups and keeps only the latest four backups. You can change the number of backups kept by changing the four in <code>head -n-4</code> to the number of backups you would like to keep.

<source lang="bash">
#!/bin/bash
if [ -z $1 -o -z $2 ]
then
echo "Usage: vzbackup CTID BACKUP-PATH"
exit 1
fi

CTID=$1
FOLDER=$2
BACKUPPATH=$FOLDER/$CTID-$( date +%F_%H_%M )

#create BACKUP-PATH
mkdir -p $BACKUPPATH

# Known snapshot ID
ID=$(uuidgen)
VE_PRIVATE=$(vzlist -H -o private $CTID)

# Take a snapshot without suspending a CT and saving its config
vzctl snapshot $CTID --id $ID --skip-suspend --skip-config

# Perform a backup using your favorite backup tool
# (cp is just an example)
cp $VE_PRIVATE/root.hdd/* $BACKUPPATH/

# Delete (merge) the snapshot
vzctl snapshot-delete $CTID --id $ID

# remove old backups
rm -rf $( find $FOLDER -type d -name "$CTID*" -exec ls -d1rt "{}" + | head -n-4 )

echo "BACKUP FINISHED."
</source>

== File-based backup ==

Assuming you have a running container identified by <code>$CTID</code>. The following needs to be done:

<source lang="bash">
# Known snapshot ID
ID=$(uuidgen)

# Directory used to mount a snapshot
MNTDIR=./mnt
mkdir $MNTDIR

# Take a snapshot without suspending a CT and saving its config
vzctl snapshot $CTID --id $ID --skip-suspend --skip-config

# Mount the snapshot taken
vzctl snapshot-mount $CTID --id $ID --target $MNTDIR

# Perform a backup using your favorite backup tool
# (tar is just an example)
tar cf backup.tar $MNTDIR

# tar with compression examples, see man page of tar for more options
# tar cfJ backup.tar.xz $MNTDIR
# tar cfz backup.tar.gz $MNTDIR

# Unmount the snapshot
vzctl snapshot-umount $CTID --id $ID

# Delete (merge) the snapshot
vzctl snapshot-delete $CTID --id $ID
</source>

== See also ==

* [[Ploop]]
* [[Man/vzctl.8#Snapshotting|vzctl(8), section Snapshotting]].

[[Category: Storage]]
[[Category: HOWTO]]

NX inside VE

2014-01-02T22:19:13Z

Dowdle:

You can run full graphical remote desktop inside container using [http://en.wikipedia.org/wiki/NX_technology NX technology]. This is handy for when you work from home and you wish to run a web browser on your work's internal network to access local resources. You can use NX client to connect to remote NX server.

[http://www.x2go.org/ x2go] is a related project that uses a fork of the NX3 GPL'ed libraries and works fairly well and doesn't have the limitations that the free (gratis) version of NX from NoMachine has. x2goserver and x2goclient packages are available as stock packages in several distros including Fedora 19 and 20, as well as being available for RHEL6/clones via the EPEL repository. If you can't find x2go packages in your distro's stock repository, check the x2go website for packages. x2go is actually easier to setup. Just install the desired GUI desktop inside of your container, install x2goserver, enable the x2gocleansessions service, make sure sshd is enabled... and connect as a user account over ssh via the x2goclient from the desired remote machine making sure to select the appropriate settings in the client.

= Fedora =

[[File:NX server on Fedora 12.png|thumb|300px|Connecting remotely with NX Client to Fedora inside OpenVZ container.]]

* Use fedora template to create new container and install desktop of your choice:

GNOME:

<pre>yum groupinstall "GNOME Desktop Environment"</pre>

KDE:

<pre>yum groupinstall "KDE (K Desktop Environment)"</pre>

XFce:

<pre>yum groupinstall "XFCE"</pre>

* You may need to install additional package audiofile:
<pre>yum install audiofile</pre>

* Download installation RPM packages for server from site [http://www.nomachine.com/select-package.php?os=linux&id=1 www.nomachine.com]. Choose right architecture i386 or x86_64.

Example:
<pre>wget http://64.34.161.181/download/3.4.0/Linux/nxclient-3.4.0-5.i386.rpm
wget http://64.34.161.181/download/3.4.0/Linux/nxnode-3.4.0-6.i386.rpm
wget http://64.34.161.181/download/3.4.0/Linux/FE/nxserver-3.4.0-8.i386.rpm</pre>

* Do simple manual installation of RPM packages.

Example:
<pre>
rpm -ivh nxclient-3.4.0-5.i386.rpm
rpm -ivh nxnode-3.4.0-6.i386.rpm
rpm -ivh nxserver-3.4.0-8.i386.rpm</pre>

* Done. You can now connect from NX client to your server.

= Ubuntu =

== Installation ==

Create a new container using the gutsy template. Edit /etc/apt/sources.list and enable the "multiverse" repository.
Install X and XDM
<pre>apt-get install xorg xdm</pre>
Then add this 3rd party repo to sources.list. (Warning: the datakeylive.com repository below is obsolete! No ubuntu repository offers freenx at the moment)

<tt>deb <s>http://www.datakeylive.com/ubuntu</s> gutsy main 
deb-src <s>http://www.datakeylive.com/ubuntu</s> gutsy main 
</tt>
Install the repo keys and update: 
<tt>
wget <s>http://www.datakeylive.com/ubuntu/dists/gutsy/wjeremy.key</s> -O - | apt-key add - 
wget <s>http://www.datakeylive.com/ubuntu/dists/gutsy/alivesoftware.key</s> -O - | apt-key add - 
sudo apt-get update
</tt>
Install FreeNX (*)
<pre>
apt-get install expect openssh-server tcl8.4 libxcomp2 libxcompext2 libxcompshad nxlibs nxagent nxproxy nxclient freenx openssl
</pre>
For Ubuntu 8.04 :
<pre>
apt-get install expect openssh-server tcl8.4 libxcomp3 libxcompext3 libxcompshad nxlibs nxagent nxproxy nxclient freenx-server openssl
</pre>
Finally install XFCE
<pre>
apt-get install xfce4
</pre>

== Configuration ==

=== Configuring X ===
In /etc/X11/xdm/xdm-config, comment out the line where it says '''DisplayManager.requestPort: 0'''

In /etc/X11/xdm/Xservers, comment out the line ''':0 local /usr/bin/X :0 vt7''' (this starts a local X server, which will fail)

In /etc/X11/xdm/Xaccess, uncomment the line with '''* #any host can get a login window''' (Please keep in mind the security implications by the above line. Read the comments found in the file and set it appropriately)

=== Configure NX Server ===

Edit /etc/X11/xorg.conf. Ensure that the files section looks similar to this:

<pre>
Section "Files"

# path to defoma fonts
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
EndSection
</pre>

Now create a local user account:
<pre>useradd -m <username></pre>

Now add this user to nxserver:
<pre>nxserver --adduser <username></pre>

=== Configure NX client ===

Setup the Host/Port.
In the desktop section select Unix and Custom. In Settings, select "Run the default X client script on server" and select "New virtual Desktop".

Now try to connect. You should get the XFCE desktop.

Thanks to dantalizing for the feedback.

== Troubleshooting ==

(*)
If you get any errors like:
<pre>
dpkg: error processing /var/cache/apt/archives/libxcomp3_3.1.0-6-2_i386.deb (--unpack):
trying to overwrite `/usr/lib/libXcomp.so.3.1.0', which is also in package libxcomp2
</pre>
while installing the libxcomp package, just force-install the libxcomp package:
<pre>
# cd /var/cache/apt/archives
# dpkg --force-all -i libxcomp3_3.1.0-6-2_i386.deb
# apt-get -f install
</pre>

You '''can't print from VE''' to client PC easily because printing in NX is realized via samba-mount of shared client's printer and CIFS isn't virtualized yet.

[[Category: HOWTO]]
[[Category: X]]

Automatically setting quotaugidlimit

2013-02-12T22:40:28Z

Dowdle: Initial placeholder for page

Place holder for user MaddinXx to share their shell script.

Creating a CentOS 6 Template

2012-10-23T20:05:52Z

Dowdle: Created page with "DRAFT - still in the works This guide requires that you already have a CentOS 6 (Having 5 might also work) - If you do not have CentOS 6 installed, do it in KVM or VirtualBox..."

DRAFT - still in the works

This guide requires that you already have a CentOS 6 (Having 5 might also work) - If you do not have CentOS 6 installed, do it in KVM or VirtualBox or whatever you want.

At a CentOS 6 host do:

yum install yum-utils
yumdownloader centos-release.x86_64

mkdir -p /newroot/var/lib/
touch /newroot/var/lib/random-seed #without it, the initscript installation script will fail

rpm --rebuilddb --root=/newroot
rpm -i --root=/newroot --nodeps centos-release-6-3.el6.centos.9.x86_64.rpm
yum --installroot=/newroot install -y openssh-clients openssh-server yum yum-utils man wget sudo tar passwd
# if you want a extremely minimal installation only install yum

yum --installroot=/newroot clean all # not sure if that is really needed

ln -s /proc/mounts /newroot/etc/mtab

/newroot/etc/fstab should look like this:
none /dev/pts devpts rw,gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0

rm -f /newroot/dev/null
mknod -m 600 /newroot/dev/console c 5 1

#if you want (not sure about this. If they are there, mingettys will run. On the other hand, if you upgrade your CentOS VPS in OpenVZ they would probably be recreated)

rm /newroot/etc/init/start-ttys.conf /newroot/etc/init/tty.conf
tar zcf /vz/template/cache/centos-6-x86_64.tar.gz .

VSwap

2011-12-28T16:32:47Z

Dowdle: Updated to reflect recent blog post by Kir that kmemsize, dcachesize, and locked pages can be set to unlimited for kernel 042stable042 and later

New [[Download/kernel/rhel6|RHEL6-based OpenVZ]] kernel has a new memory management model, which supersedes [[UBC|User beancounters]]. It is called '''VSwap'''.

Now you can set two primary parameters: <code>physpages</code> and <code>swappages</code>, while all the other beancounters become secondary.

* '''physpages'''
: This parameter limits the physical memory (RAM) available to processes inside a container.
: The <code>barrier</code> is ignored, and the <code>limit</code> sets the limit.
: Currently the user memory and the page cache are accounted into <code>physpages</code>.

* '''swappages'''
: This parameter limits the amount of swap space which can be used for processes inside a container.
: The <code>barrier</code> is ignored, and the <code>limit</code> sets the limit.

The sum of <code>physpages.limit</code> and <code>swappages.limit</code> limits the maximum amount
of allocated memory which can be used by a container. When physpages limit
is reached, memory pages belonging to the container are pushed out to
so called virtual swap (''vswap''). The difference between normal swap
and vswap is that with vswap no actual disk I/O usually occurs. Instead,
a container is artificially slowed down, to emulate the effect of the real
swapping. Actual swap out occurs only if there is a global memory shortage
on the system.

=== Secondary parameters ===
'''Even though these settings are classed as secondary, they are still important settings!'''

In addition to <code>physpages</code> and <code>swappages</code> being set, it is ''currently'' recommended to:

* Set <code>kmemsize</code> to no more than 1/2 of <code>physpages</code>
* Set <code>dcachesize</code> to no more than 1/2 of <code>kmemsize</code>
* Set <code>lockedpages</code> to no more than 1/2 of <code>physpages</code>

VSwap CT config samples (like [http://git.openvz.org/?p=vzctl;a=blob;f=etc/conf/ve-vswap-256m.conf-sample ve-vswap-256m.conf-sample] that come with vzctl are currently implementing these recommendations.

{{Note|VSwap feature is still being worked on, so these recommendation might change in the future.}}

{{Note|As of 042stab042 and later kernels, you are not required to set kmemsize, dcachesize and lockedpages resources, so you can set those to unlimited. For more information, see Kir's blog post on the subject [http://openvz.livejournal.com/39765.html].}}

[[Category: UBC]]

Setting up an iptables firewall

2009-11-03T17:57:16Z

Dowdle: Added section on Shorewall

This document consists of two parts. The first is setting up a firewall (using iptables) on the HN, which will restrict traffic to the containers. The effect would emulate, as far as the containers and their customers are concerned, an external hardware firewall controlled by the sysadmin. The second is setting up a firewall that protects the [[HN]] itself but still allows traffic to the containers, thus allowing individual containers to define their own iptables.

While the firewalls shown here can be accomplished using iptables manually (or using Fedora core's iptables service), the methods presented here are especially modular and easy to modify. This is important when you have 20+ containers and a lot of other things to be doing...

The scripts and pathnames given here are for Fedora Core 6, though they can probably be applied to most similar SysV-like systems with little modification.

== A little background ==

On our systems, we use the HN to provide privileged services which are not appropriate for access by the containers. For example, the HN acts as a backup server, runs Nagios for health monitoring, has a webserver for managing the 3ware RAID controller, etc. The containers are leased to customers, who can't entirely be trusted, especially if they get hacked. As such, our scenario is one in which the HN must be protected from all access (even from the containers) except for a few trusted hosts (e.g. my home-office).

The exception to this is the nameserver, which we want open to the world. We use it as a caching nameserver for our containers and also to host DNS for a few customer domain.

== An alternative from the author of Shorewall ==

For those who might find the solution provided in this wiki article unsatisfactory (for whatever reason), the creator of Shorewall (Tom Eastep) has written a nice article explaining how to use Shorewall on an OpenVZ host node to manage the host node, containers, and more... with quite a complex setup as an example. The article IS NOT an introduction to Shorewall for beginners, so some pre-existing knowledge and understanding of Shorewall may be required.

Shorewall and OpenVZ by Tom Eastep - http://www.shorewall.net/OpenVZ.html

See also this OpenVZ Forum posting - http://forum.openvz.org/index.php?t=msg&goto=16406&

== Setting up a HN-based firewall ==

This setup emulates (to the containers anyway) an external hardware firewall. It protects the HN from any access and then defines what services and ports are allowed/banned for individual containers. This leaves the firewall controlled by the site administrator, not be individual containers and the hackers who've gotten into them. ;)

First off, let's disable Fedora's existing <code>iptables</code> service:
<pre>
service iptables stop
chkconfig iptables off
</pre>

Now create the new <code>firewall</code> service. This code should be <code>/etc/init.d/firewall</code> and then should be chmod'd 755.
<pre>
#!/bin/sh
# firewall Start iptables firewall
# chkconfig: 2345 08 92
# description: Starts, stops and saves iptables firewall
# This script sets up the firewall for the INPUT chain (which is for
# the HN itself) and then processes the config files under
# /etc/firewall.d to set up additional rules in the FORWARD chain
# to allow access to containers' services.

. /etc/init.d/functions

# the IP block allocated to this server
SEGMENT="192.168.0.0/24"
# the IP used by the hosting server itself
THISHOST="192.168.0.1"
# services that should be allowed to the HN;
# services for containers are configured in /etc/firewall.d/*
OKPORTS="53"
# hosts allowed full access through the firewall,
# to all containers and to this server
DMZS="12.34.56.78 90.123.45.67"

purge() {
echo -n "Firewall: Purging and allowing all traffic"
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P INPUT ACCEPT
iptables -F
success ; echo
}

setup() {
echo -n "Firewall: Setting default policies to DROP"
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -I INPUT -j ACCEPT -m state --state ESTABLISHED,RELATED
iptables -I FORWARD -j ACCEPT -m state --state ESTABLISHED,RELATED
iptables -I INPUT -j ACCEPT -i lo
iptables -I FORWARD -j ACCEPT --source $SEGMENT
success ; echo

echo "Firewall: Allowing access to HN"
for port in $OKPORTS ; do
echo -n " port $port"
iptables -I INPUT -j ACCEPT -s $SEGMENT -d $THISHOST --protocol tcp --destination-port $port
iptables -I INPUT -j ACCEPT -s $SEGMENT -d $THISHOST --protocol udp --destination-port $port
success ; echo
done
for ip in $DMZS ; do
echo -n " DMZ $ip"
iptables -I INPUT -i eth0 -j ACCEPT -s $ip
iptables -I FORWARD -i eth0 -j ACCEPT -s $ip
success ; echo
done

CTSETUPS=`echo /etc/firewall.d/*`
if [ "$CTSETUPS" != "/etc/firewall.d/*" ] ; then
echo "Firewall: Setting up container firewalls"
for i in $CTSETUPS ; do
. $i
echo -n " $CTNAME CT$CTID"
if [ -n "$BANNED" ]; then
for source in $BANNED ; do iptables -I FORWARD -j DROP --destination $CTIP --source $source ; done
fi
if [ -n "$OPENPORTS" ]; then
for port in $OPENPORTS ; do iptables -I FORWARD -j ACCEPT --protocol tcp --destination $CTIP --destination-port $port ; done
for port in $OPENPORTS ; do iptables -I FORWARD -j ACCEPT --protocol udp --destination $CTIP --destination-port $port ; done
fi
if [ -n "$DMZS" ]; then
for source in $DMZS ; do iptables -I FORWARD -j ACCEPT --protocol tcp --destination $CTIP --source $source ; done
for source in $DMZS ; do iptables -I FORWARD -j ACCEPT --protocol udp --destination $CTIP --source $source ; done
fi
[ $? -eq 0 ] && success || failure
echo
done
fi
}

case "$1" in
start)
echo "Starting firewall..."
purge
setup
;;
stop)
echo "Stopping firewall..."
purge
;;
restart)
$0 stop
$0 start
;;
status)
iptables -n -L
;;
*)
echo "Usage: $0 <start|stop|restart|status>"
;;
esac
</pre>

The above script can be called like this:
<pre>
service firewall start
service firewall stop
service firewall restart
service firewall status
</pre>

It will set up the firewall for the HN according to the parameters you specified for OKPORTS, DMZs, etc. and then it will call each file under /etc/firewall.d and process its configuration.

So create a file under /etc/firewall.d The exact filename isn't important, as long as it's meaningful to you, e.g. <code>ExampleCompany</code> or <code>ve12</code> and give it content like this:

<pre>
# This file is processed by /etc/init.d/firewall
CTID="1" # the container's ID#
CTNAME="Customer1" # A human-friendly label for the container
CTIP="192.168.1.34" # the IP address for this container
OPENPORTS="80 443" # ports that should be universally opened
# to the entire Internet
DMZS="1.2.3.0/24 5.6.7.8/32" # IPs and blocks that should have full access
# to the container's services
BANNED="" # IPs and blocks that should be entirely
# blocked from the container's services
</pre>

And there you go. Go ahead and start the firewall and check its status:
<pre>
service firewall restart
service firewall status
</pre>

As you can see, you can now add and edit the configurations for individual containers very easily. This method proves a lot easier to manage than Fedora's iptables-config mechamism!

=== Debian Notes ===

The setup above works fine for Debian as well, however /etc/init.d/functions is missing. Here is a very simple version that you can use:

# /etc/init.d/functions

success() {
echo -n "...success"
}
failure() {
echo -n "...failure"
}

== Setting up a firewall that allows per-container configuration ==

This setup configures iptables on the HN to disallow access to all hosts, including the containers. However, it allows all traffic into the containers so they may define their own iptables rules and therefore manage their own firewall.

<pre>
iptables -P FORWARD ACCEPT
iptables -F FORWARD
</pre>

This will remove all rules for the FORWARD chain so all packets can pass back and forth between containers and the outside world.

If you want to use a firewall inside a container, please load these modules BEFORE starting the container:

<pre>
modprobe xt_tcpudp
modprobe ip_conntrack
</pre>

If you do not, you will get an error like this: "iptables: No chain/target/match by that name"

If you want to use stateful firewall rules (and you should!) you will also need to make sure that 'ipt_state' is in the 'IPTABLES' option in your vz.conf file:

<pre>
IPTABLES="ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state"
</pre>

Also make sure the 'xt_state' module is loaded on the host:

<pre>
modprobe xt_state
</pre>

== See also ==

* [[Traffic accounting with iptables]]

[[Category: Networking]]

Traffic accounting through proc

2009-02-03T23:03:23Z

Dowdle: The installing to crontab wasn't quite right.

Traffic Accounting through /proc/net/dev

== Introduction ==
Traffic accounting in OpenVZ can be done through data collection against
<code>/proc/net/dev</code> in the individual containers on a [[HN]].

== Prerequisites ==
* OpenVZ
* RRDTool
* GNU AWK

== Script ==
First create a directory to store your RRD files:

# mkdir /var/lib/rrd/

Then install this script:

<source lang="bash">
#!/bin/sh
# Script Name: vz_direct_traffic_log
# Author: "Brian Harrington, Alticon Inc" <bharrington@alticon.net>
# Website: htty://www.alticon.net

# Time to do the data collection.
for veid in `/usr/sbin/vzlist -o veid -H | sed 's/ //g'`; do

RRDFILE="/var/lib/rrd/$veid.rrd"

if ! test -e $RRDFILE; then
echo $RRDFILE does not exist, creating.
# Place your preferred RRD Creation command here
fi

# Parse out the inbound/outbound traffic and assign them to the corresponding variables
eval `/usr/sbin/vzctl exec $veid "grep venet0 /proc/net/dev" | \
awk -F: '{print $2}' | awk '{printf"CTIN=%-15d\nCTOUT=%-15d\n", $1, $9}'`

# Send the data to the corresponding RRD time with (N)now as the update time
/usr/bin/rrdtool update $RRDFILE N:$CTIN:$CTOUT
done
</source>

== Setup ==
Add this to cron to run every 5 minutes:

# echo "*/5 * * * * root /path/to/script/vz_direct_traffic_log " >> \
/etc/crontab && /etc/init.d/crontab restart

To check the output of this later run:

# rrdtool fetch /var/lib/rrd/<veid>.rrd AVERAGE -s -3600

== See also ==

* [[Traffic accounting with iptables]]

[[Category: Monitoring]]
[[Category: Networking]]

Using vzpkg and vzyum on x86 64

2008-12-19T18:13:38Z

Dowdle: Added warning about missing vzquota.x86_64

This document describes a way to install OpenVZ in a x86_64 computer, so that it can create cache templates, use vzyum and vzrpm.
This is intended to work in a host with Centos-4, Centos-5, Fedora Core 5, Fedora Core 6, RHEL 4 or any other RPM based based system with python 2.2, 2.3 or 2.4 version.

Last Revision: 08:10, 3 March 2008 (EST)

== THE PROBLEM ==

There is a known problem with vzpkg-2.7.0 and vzyum-2.4.0 in x86_64 computers:
Vzyum, vzpkgcache and vzrpm are broken in 64 bit systems, so we are unable to create new cache templates in a x86_64 computer or update each [[container]] using vzyum or vzrpm.
This text describes a work around and a few hacks to get it work flawless.

{{Note| The basic idea is to change the code in such a way that vzyum and vzrpm use the real yum and rpm to do the job, and also create new x86_64 paths required by the system.}}

== REQUIREMENTS ==

* - A x86_64 computer
* - A host with x86_64 Centos, Fedora Core or RHEL, or other Redhat based systems with python 2.2, 2.3 or 2.4 version (vzrpm is unable to run with python 2.5 version)
* - Yum package installed.

== TESTED HOSTS ==

* - Centos 4
* - Centos 5
* - Fedora Core 5
* - Fedora Core 6

== HOSTS PROBABLY WORKING (not tested) ==

* - RHEL 4
* - RHEL 5

== HOSTS NOT WORKING ==

* - Older distros with yum version less then 2.4, python version less then 2.2, rpm version less then 4.3
* - Fedora 7
* - Fedora 8
* - Or any other system with python 2.5 or above.

== SIDE EFFECTS ==

Until now there is only one side effect detected in this solution:
* The yum cache is not common to all [[container]]s. Instead, each [[container]] has it's own yum cache in the directory <code>/var/cache/yum-cache</code>.
This is a consequence from using the modified vzyum.

== INSTALL Openvz ==

There are two ways to install it:

* A - AUTOMATIC INSTALL (FASTEST)
* B - MANUAL INSTALL - STEP BY STEP

=== A - AUTOMATIC INSTALL (FASTEST) ===

General considerations

* This is a fastest way to install openvz utilities, and template utilities, ready to use in a x86_64 system.
* You can only use the automatic install IF YOU HAVE YUM AND RPM PACKAGES INSTALLED IN YOUR SYSTEM.
* This process uses a bash script which automates all the hard work made by hand in the manual install. It was successfully tested in several systems.
* If something goes wrong, or if you want to understand the way it works to install a diferent distribution, it's better to do the manual install, and try to adapt it to your needs.

Procedure

* Read carefully the [[Quick installation]] page and install the openvz kernel, configure the bootloader, change sysctl.conf, and finally reboot your system the way it is described there.
* Download the file [http://linux.carreira.com.pt/ovzutils/setx86_64-0.3.tar.gz setx86_64-0.3] and then untar and run the script:

<pre>
tar xzvf setx86_64-0.3.tar.gz
sh setx86_64
</pre>

{{Warning|Please note that the setx86_64 script currently may not install the vzquota.x86_64 package and only include the vzquota.i386... which has been noted to cause disk quota issues when creating containers. To avoid this issue it is recommended you manually install the vzquota.x86_64 package until the script is updated:
yum install vzquota.x86_64}}

Press Enter and some tests are made to know if you can go on with the installation.
If you choose to go on with it, the script will download and patch everything for you.
All the vztemplates metadata available in openvz.org site are also installed and fixed for x86_64 system.

When it finishes with the message "END INSTALL", you can go on reading this document jumping to the undermentioned [[#STEP_11|STEP 11]].

=== B - MANUAL INSTALL -STEP BY STEP ===

If for any reason you prefer manual installation, you may start your install process the same way as described in [[Quick installation]].
In x86_64, the packages vzpkg, vzyum and vztmpl-* are broken. So, let's install them this way, to avoid problems:

<code>
yum install vzrpm*
</code>

We can't "yum install vzyum" because it breaks with an error: 
Error: Missing Dependency: cElementTree.so is needed by package vzyum

So we must download it first and then install it.

<code>
wget -c http://download.openvz.org/template/utils/vzyum/2.4.0-11/vzyum-2.4.0-11.noarch.rpm
rpm --nodeps -Uvh vzyum*.rpm
yum install vzpkg*
</code>

==== TWEAKING THE CODE ====

Now let's tweak the code doing it step by step.
You can do a copy-paste from the next command lines to your system.
The example is using Centos-4 distribution, but Fedora or other distribution with yum, rpm and python (version 2.2, 2.3 or 2.4) installed, may be tried. You only have to change the reference name and version in STEPS 1 to 4.

===== STEP 1 =====

Install "vztmpl-centos-4":

<code>
yum install vztmpl-centos-4
</code>

Note: In setx86-0.3 script, all the vztemplates available in openvz.org site are downloaded and used to build x86_64 templates, ready to be used.

===== STEP 2 =====

The template installed is a i386 template. So, we need to create a x86_64 template from the i386.
We only have to replace i386 references with x86_64 in all files.

<code>
cd /vz/template/centos/4/
cp -a i386 x86_64
cd /vz/template/centos/4/x86_64/config
sed -i.tmp 's/i386/x86_64/g' yum.conf
rm -f yum.conf.tmp
</code>

Now we have a x86_64 centos template installed. 
You can do the same procedure to other distro templates.

===== STEP 3 =====

Edit the file <code>/vz/template/centos/4/x86_64/config/yum.conf</code> with your editor.
Change the line:

:<code>cachedir=/vz/template/centos/4/x86_64/yum-cache</code>

:to

:<code>cachedir=/var/cache/yum-cache</code>

{{Note| With this changes, vzyum is not going to be able to use a common cache directory to all [[container]]s as it was used to do. Each [[container]] will have it's own cache directory.
To avoid to have a directory named /vz/template/centos/4/x86_64/yum-cache in each [[container]], it is preferable to use the correct cache directory /var/cache/yum-cache.}}

===== STEP 4 =====

Verify the host rpm version:

:<code>rpm --version</code>

In Centos-4 rpm is version 4.3.

Edit this file /vz/template/centos/4/x86_64/config/rpm, and
you will see the number 43.

When the host distro is the same of the template guest, everything would be correct, and we don't need doing anything. 
But if we have a different guest template, we might have to correct the values.

We have to change the number inside /vz/template/distro/version/x86_64/config/rpm
according to the rpm version of the host system. 
If rpm version is 4.4 the number would be 44. 
If rpm version is 4.3 the number would be 43.

===== STEP 5 =====

If you list the directory vz-addons like this:

ls -l /vz/template/centos/4/x86_64/vz-addons

probably you will see the file MAKEDEV-3.3.13-1.3.swsoft.i386.rpm.
This "ls" allows us to confirm which MAKEDEV version we need to use in this step.

Edit the files minimal.list and default.list in /vz/template/centos/4/x86_64/config directory, and change the line:

<pre>
MAKEDEV

to

MAKEDEV-3.3.13 (or the version you saw in the "ls")
</pre>
This avoids the undesirable update of special MAKEDEV-swsoft to the real MAKEDEV from the distro yum repository during a vzyum action.

===== STEP 6 =====

Verify if you have rpm-python installed in your system, because it has 64 bit module needed:

<pre>
rpm -q rpm-python
rpm-python-4.3.3-18_nonptl
</pre>

Install it if you didn't do it already:
yum install rpm-python

In Centos-4 version python is 2.3. So, we must replace rpmmodule.so from vzrpm43-python to the 64 bit module that rpm-python-x86_64 provides.

<pre>

cd /usr/share/vzpkgtools/vzrpm43/lib/python2.3/site-packages/
cp /usr/lib64/python2.3/site-packages/rpmmodule.so .
cp: overwrite `./rpmmodule.so'? y
cd /usr/share/vzpkgtools/vzrpm43/lib/python2.3/site-packages/rpmdb
cp /usr/lib64/python2.3/site-packages/rpmdb/_rpmdb.so .
cp: overwrite `./_rpmdb.so'? y
</pre>

In other Operating Systems or other versions, you must verify which python version is installed in the host system.
Depending on that, the 32 bit files to be replaced are different (read the setx86_64-0.3 script, line 320 to line 345, to understand how it is done).

<blockquote style="background: white; border: 1px solid rgb(153, 153, 153); padding: 1em;">
Note: 
Someone reported the note below, but the tests I made, didn't confirm it was really needed. Everything worked flawless without it. 
Nevertheless, if you find some problems, try the workaround described below: 

For CentOS-5, you will need to do something a bit different. "rpmmodule.so" is provided in your sitewide python distribution, so instead of copying it across, you need to:
:rm /usr/share/vzpkgtools/vzrpm43/lib/python2.4/site-packages/rpmmodule.so

</blockquote>

Now we must edit and change these 3 files described in the next steps:

/usr/share/vzpkg/cache-os

/usr/share/vzpkg/functions

/usr/bin/vzyum

===== STEP 7 =====

Edit the file /usr/share/vzpkg/cache-os 
Change the next lines:

 -Line 136:
<pre>
change: --vps=$VEID check-update
to: check-update
</pre>

 -Line 185:
<pre>
change: YUM_CMD="--installroot=$VE_ROOT --vps=$VEID $YUM_CONF_FILE -y $YUM_CMD"
to: YUM_CMD="--installroot=$VE_ROOT $YUM_CONF_FILE -y $YUM_CMD"
</pre>

===== STEP 8 =====

Edit the file /usr/share/vzpkg/functions 
Change the next lines:

 -Line 21:
<pre>
change: YUM=/usr/share/vzyum/bin/yum
to: YUM=`which yum`
</pre>

 -Line 22:
<pre>
change: ARCHES="x86 i386 x86_64 ia64"
to: ARCHES="i386 x86_64 ia64 x86"
</pre>

 -Line 111:
<pre>
change: export RPM=`get_rpm $tdir`
to: export RPM=`which rpm`
</pre>

 -Line 450:
<pre>
change: rpm=`get_rpm $tdir`
to: rpm=`which rpm`
</pre>

===== STEP 9 =====

Edit the file /usr/bin/vzyum 
Change the next line:

 -Line 51:
<pre>
change: YUM_ARGS="$YUM_ARGS --installroot $VE_ROOT --vps=$VEID"
to: YUM_ARGS="$YUM_ARGS --installroot $VE_ROOT"
</pre>

The next piece of code fixed the vzyum bug described in [http://bugzilla.openvz.org/show_bug.cgi?id=488#c0 bugzilla #488]. 
It was impossible to install a package group with spaces in his name. 
Now we can use e.g. vzyum groupinstall \"GNOME Desktop Environment\",
or other group name listed in vzyum grouplist. 
(Don't forget the backslash before each doublequote)

 -Line 56:
<pre>
comment the line 56:
#exec $YUM $YUM_ARGS $USER_ARGS
</pre>

 -Last Line (57): 

<pre>
add this code:

TMPVZY=/tmp/tmpvzy.$$
echo $YUM $YUM_ARGS $USER_ARGS > $TMPVZY
sh $TMPVZY
exec rm -f $TMPVZY
</pre>

===== STEP 10 =====

Edit file /usr/bin/vzrpm
Change next line:

 -Line 40:
<pre>
change: RPM_ARGS="--root $VE_ROOT --veid $VEID"
to: RPM_ARGS="--root $VE_ROOT"
</pre>

 -Line 52:
<pre>
change: RPM=`get_rpm $TDIR`
to: RPM=`which rpm`
</pre>

===== STEP 11 =====

If you want your [[container]]s to have other country locales
edit <code>/vz/template/centos/4/x86_64/config/.rpmmacros</code> and change the line %_install_langs C
to the language you want, for example:

%_install_langs C:pt_PT:pt_PT.UTF-8:en_US:en_US.UTF-8

== TESTING THE NEW CODE ==

Now you can create your own template caches from your own templates.
Let's test it!

List all x86_64 templates available:

vzpkgls | grep x86_64

Choose one of them to create the first cache template (this can be time consuming):

vzpkgcache -f centos-4-x86_64-minimal

It finishes with complaints about cron.daily, but don't worry about it.
Now minimal cache is created. Confirm if they were created:

vzpkgls -c

If you see it in the cache list, then you can create your first [[container]]:

vzctl create 200 --ostemplate centos-4-x86_64-minimal

To change the locales, copy <code>/etc/sysconfig/i18n</code> to <code>/vz/private/200/etc/sysconfig</code>, if you wish to use another language and have done STEP 10 previously.

Now start [[container]] 200 previously created:

vzctl start 200

Then test also "vzyum" and see if it works. Try to install "nano editor":

vzyum 200 install nano

Try to use vzrpm, to list all rpm's installed in [[container]] 200:

vzrpm 200 -qa

If you didn't have any errors, the changes are fine.

If something went wrong, probably you made a mistake in those previous steps.
Carefully verify if you did it well, step by step.

[[Category: Templates]]
[[Category: HOWTO]]
[[Category: Troubleshooting]]

Quick installation (legacy)

2008-12-19T16:50:04Z

Dowdle: Just added a mention of the .x86_64 arch specific packages to avoid 64-bit users getting the 32-bit packages by mistake.

This document briefly describes the steps needed to install OpenVZ on your (RPM based) machine. For '''Debian''' based systems see [[Installation on Debian]].

This document is also available in the following languages: [http://forum.openvz.org/index.php?t=tree&goto=35&#msg_35 French], [http://forum.openvz.org/index.php?t=tree&goto=1805&#msg_1805 German],
[http://wiki.openvz.jp Japanese],
[[Quick_installation_(Spanish)|Spanish]].

OpenVZ consists of a kernel, user-level tools, and container templates. This guide tells how to install the kernel and the tools.

== Requirements ==
This guide assumes you are running recent release of Fedora Core (like FC5) or RHEL/CentOS 4. Currently, OpenVZ kernel tries to support the same hardware that Red Hat kernels support. For full hardware compatibility list, see [http://www.swsoft.com/en/products/virtuozzo/hcl/ Virtuozzo HCL].

=== Filesystems ===
It is recommended to use a separate partition for container's private directories (by default /vz/private/<veid>). The reason why you should do so is that if you wish to use OpenVZ per-container disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind, that per-container quota in this context includes not only pure per-container quota, but also usual Linux disk quota used in containers, not on [[HN]].

At least try to avoid using the root partition for containers, because the root user of a container will be able to overcome the 5% disk space barrier in some situations. This way the HN root partition can be completely filled and it will break the system.

OpenVZ per-container disk quota is supported only for ext2/ext3 filesystems. So use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

=== rpm or yum? ===

In case you have yum utility available on your system, you may want to use it effectively to install and update OpenVZ packages. In case you don't have yum, or don't want to use it, you can use plain old rpm. Instructions for both rpm and yum are provided below.

=== yum pre-setup ===
If you want to use yum, you should set up OpenVZ yum repository first.

Download [http://download.openvz.org/openvz.repo openvz.repo] file and put it to your <code>/etc/yum.repos.d/</code> repository. This can be achieved by the following commands, as root:
<pre>
# cd /etc/yum.repos.d
# wget http://download.openvz.org/openvz.repo
# rpm --import http://download.openvz.org/RPM-GPG-Key-OpenVZ
</pre>

In case you can not cd to /etc/yum.repos.d, it means either yum is not installed on your system, or yum version is too old. In that case, just stick to rpm installation method.

== Kernel installation ==

{{Note|In case you want to recompile the kernel yourself rather than use the one provided by OpenVZ, see [[kernel build]].}}

First, you need to choose what “flavor” of the kernel you want to install. Please refer to [[Kernel flavors]] for more information.

=== Using yum ===
Run the following command
<pre>
# yum install ovzkernel[-flavor]
</pre>

Here <code>[-flavor]</code> is optional, and can be <code>-smp</code> or <code>-enterprise</code>. Refer to [[kernel flavors]] for more info.

{{Note|if you need to install <code>x86_64</code> kernel and yum offers to install both <code>x86_64</code> and <code>i686</code> kernels, answer <code>No</code> and specify architecture manually, like this: <code>yum install ovzkernel[-flavor].x86_64</code>. This is fixed in newer yum versions.}}

=== Using rpm ===
Get the kernel binary RPM from the [[Download/kernel]] page. You only need one kernel RPM so please [[Kernel flavors|choose the appropriate one]] depending on your hardware.

Next, install the kernel RPM you chose:

<pre>
# rpm -ihv ovzkernel[-flavor]*.rpm
</pre>

Here <code>[-flavor]</code> is optional, and can be <code>-smp</code> or <code>-enterprise</code>. Refer to [[kernel flavors]] for more info.

{{Note|<tt>rpm -U</tt> (where <tt>-U</tt> stands for ''upgrade'') should '''not''' be used, otherwise all currently installed kernels will be uninstalled.}}

== Configuring the bootloader ==

In case GRUB is used as the boot loader, it will be configured automatically: lines similar to these will be added to the <tt>/boot/grub/grub.conf</tt> file:

<pre>
title Fedora Core (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5 quiet rhgb vga=0x31B
initrd /initrd-2.6.8-022stab029.1.img
</pre>
Change <tt>Fedora Core</tt> to <tt>OpenVZ</tt> (just for clarity reasons, so the OpenVZ kernels will not be mixed up with non-OpenVZ ones). Remove extra arguments from the kernel line, leaving only the <tt>root=...</tt> parameter. The modifed portion of <tt>/etc/grub.conf</tt> should look like this:

<pre>
title OpenVZ (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5
initrd /initrd-2.6.8-022stab029.1.img
</pre>

== Configuring ==

Please make sure the following steps are performed before rebooting into OpenVZ kernel.

=== sysctl ===

There are a number of kernel parameters that should be set for OpenVZ to work correctly. These parameters are stored in <tt>/etc/sysctl.conf</tt> file. Here are the relevant portions of the file; please edit accordingly.

<pre>
# On Hardware Node we generally need
# packet forwarding enabled and proxy arp disabled
net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp = 0

# Enables source route verification
net.ipv4.conf.all.rp_filter = 1

# Enables the magic-sysrq key
kernel.sysrq = 1

# We do not want all our interfaces to send redirects
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
</pre>

=== SELinux ===

SELinux should be disabled. To that effect, put the following line to <code>/etc/sysconfig/selinux</code>:
<pre>
SELINUX=disabled
</pre>

=== Conntracks ===

In the stable OpenVZ kernels (those that are 2.6.8-based) netfilter connection tracking for [[CT0]] is disabled by default. If you have a stateful firewall enabled on the host node (it is there by default) you should either disable it, or enable connection tracking for [[CT0]].

To enable conntracks for CT0, add the following line to <code>/etc/modprobe.conf</code> file:
<pre>
options ip_conntrack ip_conntrack_enable_ve0=1
</pre>

{{Note|In kernels later than 2.6.8, connection tracking is enabled by default.}}

== Rebooting into OpenVZ kernel ==

Now reboot the machine and choose "OpenVZ" on the boot loader menu. If the OpenVZ kernel has been booted successfully, proceed to installing the user-level tools for OpenVZ. If you are installing on x86_64 CentOS or Fedora system, you may want to continue the setup process using the [[Install_OpenVZ_on_a_x86_64_system_Centos-Fedora|x86_64 guide]].

== Installing the utilities ==

OpenVZ needs some user-level tools installed. Those are:

; vzctl
: A utility to control OpenVZ containers (create, destroy, start, stop, set parameters etc.)
; vzquota
: A utility to manage quotas for containers. Mostly used indirectly (by vzctl).

=== Using yum ===

<pre>
# yum install vzctl vzquota
</pre>

If on the x86_64 platform you would probably want to:

<pre>
# yum install vzctl.x86_64 vzquota.x86_64
</pre>

=== Using rpm ===

Download the binary RPMs of these utilities from [[Download/utils]]. Install them:

<pre>
# rpm -Uhv vzctl*.rpm vzquota*.rpm
</pre>

If rpm complains about unresolved dependencies, you'll have to satisfy them first, then repeat the installation.

When all the tools are installed, start the OpenVZ subsystem.

== Starting OpenVZ ==

As root, execute the following command:

<pre>
# /sbin/service vz start
</pre>

This will load all the needed OpenVZ kernel modules. This script should also start all the containers marked to be auto-started on machine boot (there aren't any yet).

During the next reboot, this script should be executed automatically.

== Next steps ==

OpenVZ is now set up on your machine. To load OpenVZ kernel by default, edit the default line in the /boot/grub/grub.conf file to point to the OpenVZ kernel. For example, if the OpenVZ kernel is the first kernel mentioned in the file, put it as default 0. See man grub.conf for more details.

The next step is to prepare the [[OS template]]: please continue to [[OS template cache preparation]] document.

[[Category: Installation]]
[[Category: HOWTO]]

Download/template/precreated

2008-12-16T20:49:11Z

Dowdle: Added warning with direct links to the download directories for official and contributed pre-created OS Templates.

{{Precreated templates info}}

{{Warning|The Debian templates below still contain insecure [http://www.debian.org/security/2008/dsa-1571 OpenSSL packages]. Make sure to install security updates and [http://www.debian.org/security/key-rollover/ recreate keys]!}}
{{Warning|This problem most likely also applies to the Ubuntu images.}}
{{Warning|This page is not always current so be sure and check out the direct links to the [http://download.openvz.org/template/precreated/ official] and the [http://download.openvz.org/template/precreated/contrib/ contributed] pre-created OS Templates.}}

{{DownloadTableHead}}
{{DownloadTableRow|path=template/precreated|file=asianux-2.0-SP1-minimal-x86.tar.gz|size=125 Mb|sig=asianux-2.0-SP1-minimal-x86.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=centos-4-i386-default.tar.gz|size=107 Mb|sig=centos-4-i386-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=centos-4-i386-minimal.tar.gz|size=33 Mb|sig=centos-4-i386-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=centos-4-x86_64-default.tar.gz|size=139 Mb|sig=centos-4-x86_64-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=centos-4-x86_64-minimal.tar.gz|size=60 Mb|sig=centos-4-x86_64-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=debian-3.1-i386-minimal.tar.gz|size=42 Mb|sig=debian-3.1-i386-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=debian-3.1-ia64-minimal.tar.gz|size=50 Mb|sig=debian-3.1-ia64-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=debian-3.1-powerpc-minimal.tar.gz|size=43 Mb|sig=debian-3.1-powerpc-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=debian-3.1-sparc-minimal.tar.gz|size=43 Mb|sig=debian-3.1-sparc-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=debian-3.1-x86_64-minimal.tar.gz|size=41 Mb|sig=debian-3.1-x86_64-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=debian-4.0-i386-minimal.tar.gz|size=53 Mb|sig=}}
{{DownloadTableRow|path=template/precreated|file=debian-4.0-sparc-minimal.tar.gz|size=49 Mb|sig=debian-4.0-sparc-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=debian-etch-powerpc-minimal.tar.gz|size=54 Mb|sig=debian-etch-powerpc-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-7-ppc-minimal.tar.gz|size=144 Mb|sig=fedora-7-ppc-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-3-i386-default.tar.gz|size=105 Mb|sig=fedora-core-3-i386-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-3-i386-minimal.tar.gz|size=33 Mb|sig=fedora-core-3-i386-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-4-i386-default.tar.gz|size=114 Mb|sig=fedora-core-4-i386-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-4-i386-minimal.tar.gz|size=45 Mb|sig=fedora-core-4-i386-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-5-i386-default.tar.gz|size=125 Mb|sig=fedora-core-5-i386-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-5-i386-minimal.tar.gz|size=44 Mb|sig=fedora-core-5-i386-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-5-ppc-minimal.tar.gz|size=101 Mb|sig=fedora-core-5-ppc-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=fedora-core-6-i686-default.tar.gz|size=154 Mb|sig=fedora-core-6-i686-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=gentoo-20060317-amd64-stage3.tar.gz|size=119 Mb|sig=gentoo-20060317-amd64-stage3.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=gentoo-20060317-i686-stage3.tar.gz|size=106 Mb|sig=gentoo-20060317-i686-stage3.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=mandriva-2006-i386-minimal.tar.gz|size=28 Mb|sig=mandriva-2006-i386-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=opensuse-10-i386-default.tar.gz|size=90 Mb|sig=opensuse-10-i386-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=opensuse-10-x86_64-default.tar.gz|size=96 Mb|sig=opensuse-10-x86_64-default.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=ubuntu-7.10-amd64-minimal.tar.gz|size=51 Mb|sig=ubuntu-7.10-amd64-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=ubuntu-7.10-i386-minimal.tar.gz|size=51 Mb|sig=ubuntu-7.10-i386-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=ubuntu-8.04-amd64-minimal.tar.gz|size=45 Mb|sig=ubuntu-8.04-amd64-minimal.tar.gz.asc}}
{{DownloadTableRow|path=template/precreated|file=ubuntu-8.04-i386-minimal.tar.gz|size=46 Mb|sig=ubuntu-8.04-i386-minimal.tar.gz.asc}}
{{DownloadTableTail}}
{{Contributed templates info}}

{{DownloadTableHead}}
{{DownloadTableRow|path=template/precreated/contrib|file=altlinux-2.4.tar.gz|size=24 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=altlinux-3.0-etcnet07.tar.gz|size=20 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=altlinux-3.0.tar.gz|size=20 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=altlinux-4.0-i586.tar.gz|size=22 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=altlinux-20060914-x86_64.tar.gz|size=21 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=altlinux-20060914.tar.gz|size=20 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=altlinux-20060928-x86_64.tar.gz|size=21 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=arch-0.8-i686-minimal.tar.gz|size=88 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=arch-0.8-x86_64-minimal.tar.gz|size=93 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=centos-5-i386-default.tar.gz|size=124 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=centos-5-i386-minimal.tar.gz|size=46 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=centos-5-x86_64-default.tar.gz|size=143 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=centos-5-x86_64-minimal.tar.gz|size=46 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=cern-4-i386-default.tar.gz|size=123 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=cern-4-i386-minimal.tar.gz|size=46 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=cern-4-x86_64-default.tar.gz|size=134 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=cern-4-x86_64-minimal.tar.gz|size=51 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=debian-4.0-amd64-minimal.tar.gz|size=52 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=debian-4.0-proxmox-mailgateway-2.0.tar.gz|size=117 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=fedora-8-i386-minimal.tar.gz|size=81 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=fedora-9-i386-default.tar.gz|size=152 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=fedora-9-i386-minimal.tar.gz|size=60 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=fedora-9-x86_64-default.tar.gz|size=173 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=fedora-9-x86_64-minimal.tar.gz|size=65 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=fedora-core-7-i386-default.tar.gz|size=109 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=fedora-core-7-i386-minimal.tar.gz|size=61 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=gentoo-amd64-20071018.tar.gz|size=139 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=slackware-10.2-i386-minimal.tar.gz|size=26 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=slackware-11.0-i386-minimal.tar.gz|size=28 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=slackware-12.0-i386-minimal.tar.gz|size=29 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=suse-9.3-x86_64.tar.gz|size=155 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=ubuntu-6.06-i386-minimal.tar.gz|size=60 Mb|sig=}}
{{DownloadTableRow|path=template/precreated/contrib|file=ubuntu-7.10-i386-minimal.tar.gz|size=45 Mb|sig=ubuntu-7.10-i386-minimal.tar.gz.md5}}
{{DownloadTableTail}}

Install vzpkg2 and pkg-cacher

2008-11-26T15:30:54Z

Dowdle: Added info on how to build a single OS Template

=== Introduction ===

Robert Nelson has created a couple new utilities to make managing and updating templates and containers easier, vzpkg2 pkg-cacher. So far they will create and update a large range of containers, including both 32bit and 64bit of the following:

* Centos 4 and 5,
* Fedora 7, 8 and 9,
* Debian Sarge and Etch,
* Ubuntu Feisty, Gutsy and Hardy.

Pkg-cacher is a transparent caching proxy daemon optimized for Debian and RPM packages. In other terms, pkg-cacher is a service that runs on a machine that other machines and containers, or "clients", use to update themselves instead of each of them directly hitting the package repositories. Pkg-cacher only downloads a file once and then gives that to all its clients, instead of each of the clients downloading the file from the Internet at large. It is based on [http://www.nick-andrew.net/projects/apt-cacher/ apt-cacher], available with Debian. This version has been modified to understand RedHat RPM repositories. It also adds support for the HTTP Range header and deals correctly with files which have the same name but different content on different distributions or in some cases different versions of the same distribution.

Robert has setup repositories for Fedora, CentOS and Debian.

====Screencast====

Scott Dowdle has recorded a good screencast overview of vzpkg2 and pkg-cacher at:

http://www.montanalinux.org/vzpkg2-screencast.html

===Installation===

====Centos & Fedora installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

yum remove vzpkg vztmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Quick installation]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Download the repository file for your OS=====

For CentOS:
wget http://repo.opensource-sw.net/centos/ossw.repo -P /etc/yum.repos.d

For Fedora:
wget http://repo.opensource-sw.net/fedora/ossw.repo -P /etc/yum.repos.d

You may wish to edit the repository file, perhaps to add a priorities setting.

=====Install vzpkg2 and pkg-cacher=====

Once the repository is added in /etc/yum.repos.d, you can now install the new vzpkg2 and pkg-cacher from it:

yum install vzpkg2 vztmpl2-centos vztmpl2-fedora vztmpl2-debian vztmpl2-ubuntu
yum install pkg-cacher-sa

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it by running as root:

service pkg-cacher restart

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running.

To build an individual OS Template just run the 'vzpkgcache' command and pass it the name of the OS Template you want to build. For a list of OS Templates you can build, run the 'vzpkgls' command. Example:

vzpkgcache centos-5-i386-default

If you'd like to build all OS Templates available, just run the 'vzpkgcache' command without any parameters. Example:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

====Debian Installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

apt-get erase vzpkg vzctl-ostmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Installation on Debian]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Add the deb repositories to your /etc/apt/sources.list:=====

Add the following lines to your /etc/apt/sources.list:

Etch:
deb http://repo.opensource-sw.net/debian/ etch openvz
deb-src http://repo.opensource-sw.net/debian/ etch openvz

Sarge:
deb http://repo.opensource-sw.net/debian/ sarge openvz
deb-src http://repo.opensource-sw.net/debian/ sarge openvz

Then do:
apt-get update
apt-get install pkg-cacher-sa vzpkg2

=====Adding New Templates:=====

Install the desired OS Template Metadata packages:

apt-get install vztmpl2-centos vztmpl2-fedora vztmpl2-ubuntu vztmpl2-debian

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it.

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running

To get a list of what OS Templates you may now use, type the following:

vzpkgls

That will produce a list of available OS Templates. Use any name given in the list as a parameter to vzpkgcache to build that OS Template. Example:

vzpkgcache centos-5-i386-default

If you want to build all OS Templates you can simply run vzpkgcache without any paramters:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

===Source===

The source for the new vzpkg2 and templates is available on http://git.opensource-sw.net. In order to clone the updated source use the command:
git clone http://git.opensource-sw.net/git/vzpkg

The templates are available using:
git clone http://git.opensource-sw.net/git/vztmpl

Install vzpkg2 and pkg-cacher

2008-11-26T15:24:25Z

Dowdle: Updated to show how to build an individual OS Template rather than just all of them.

=== Introduction ===

Robert Nelson has created a couple new utilities to make managing and updating templates and containers easier, vzpkg2 pkg-cacher. So far they will create and update a large range of containers, including both 32bit and 64bit of the following:

* Centos 4 and 5,
* Fedora 7, 8 and 9,
* Debian Sarge and Etch,
* Ubuntu Feisty, Gutsy and Hardy.

Pkg-cacher is a transparent caching proxy daemon optimized for Debian and RPM packages. In other terms, pkg-cacher is a service that runs on a machine that other machines and containers, or "clients", use to update themselves instead of each of them directly hitting the package repositories. Pkg-cacher only downloads a file once and then gives that to all its clients, instead of each of the clients downloading the file from the Internet at large. It is based on [http://www.nick-andrew.net/projects/apt-cacher/ apt-cacher], available with Debian. This version has been modified to understand RedHat RPM repositories. It also adds support for the HTTP Range header and deals correctly with files which have the same name but different content on different distributions or in some cases different versions of the same distribution.

Robert has setup repositories for Fedora, CentOS and Debian.

====Screencast====

Scott Dowdle has recorded a good screencast overview of vzpkg2 and pkg-cacher at:

http://www.montanalinux.org/vzpkg2-screencast.html

===Installation===

====Centos & Fedora installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

yum remove vzpkg vztmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Quick installation]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Download the repository file for your OS=====

For CentOS:
wget http://repo.opensource-sw.net/centos/ossw.repo -P /etc/yum.repos.d

For Fedora:
wget http://repo.opensource-sw.net/fedora/ossw.repo -P /etc/yum.repos.d

You may wish to edit the repository file, perhaps to add a priorities setting.

=====Install vzpkg2 and pkg-cacher=====

Once the repository is added in /etc/yum.repos.d, you can now install the new vzpkg2 and pkg-cacher from it:

yum install vzpkg2 vztmpl2-centos vztmpl2-fedora vztmpl2-debian vztmpl2-ubuntu
yum install pkg-cacher-sa

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it by running as root:

service pkg-cacher restart

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running, then run as root:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

====Debian Installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

apt-get erase vzpkg vzctl-ostmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Installation on Debian]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Add the deb repositories to your /etc/apt/sources.list:=====

Add the following lines to your /etc/apt/sources.list:

Etch:
deb http://repo.opensource-sw.net/debian/ etch openvz
deb-src http://repo.opensource-sw.net/debian/ etch openvz

Sarge:
deb http://repo.opensource-sw.net/debian/ sarge openvz
deb-src http://repo.opensource-sw.net/debian/ sarge openvz

Then do:
apt-get update
apt-get install pkg-cacher-sa vzpkg2

=====Adding New Templates:=====

Install the desired OS Template Metadata packages:

apt-get install vztmpl2-centos vztmpl2-fedora vztmpl2-ubuntu vztmpl2-debian

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it.

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running

To get a list of what OS Templates you may now use, type the following:

vzpkgls

That will produce a list of available OS Templates. Use any name given in the list as a parameter to vzpkgcache to build that OS Template. Example:

vzpkgcache centos-5-i386-default

If you want to build all OS Templates you can simply run vzpkgcache without any paramters:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

===Source===

The source for the new vzpkg2 and templates is available on http://git.opensource-sw.net. In order to clone the updated source use the command:
git clone http://git.opensource-sw.net/git/vzpkg

The templates are available using:
git clone http://git.opensource-sw.net/git/vztmpl

Install vzpkg2 and pkg-cacher

2008-11-26T15:21:03Z

Dowdle: Removed the mis-information that said the metadata packages were only available in rpm format.

=== Introduction ===

Robert Nelson has created a couple new utilities to make managing and updating templates and containers easier, vzpkg2 pkg-cacher. So far they will create and update a large range of containers, including both 32bit and 64bit of the following:

* Centos 4 and 5,
* Fedora 7, 8 and 9,
* Debian Sarge and Etch,
* Ubuntu Feisty, Gutsy and Hardy.

Pkg-cacher is a transparent caching proxy daemon optimized for Debian and RPM packages. In other terms, pkg-cacher is a service that runs on a machine that other machines and containers, or "clients", use to update themselves instead of each of them directly hitting the package repositories. Pkg-cacher only downloads a file once and then gives that to all its clients, instead of each of the clients downloading the file from the Internet at large. It is based on [http://www.nick-andrew.net/projects/apt-cacher/ apt-cacher], available with Debian. This version has been modified to understand RedHat RPM repositories. It also adds support for the HTTP Range header and deals correctly with files which have the same name but different content on different distributions or in some cases different versions of the same distribution.

Robert has setup repositories for Fedora, CentOS and Debian.

====Screencast====

Scott Dowdle has recorded a good screencast overview of vzpkg2 and pkg-cacher at:

http://www.montanalinux.org/vzpkg2-screencast.html

===Installation===

====Centos & Fedora installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

yum remove vzpkg vztmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Quick installation]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Download the repository file for your OS=====

For CentOS:
wget http://repo.opensource-sw.net/centos/ossw.repo -P /etc/yum.repos.d

For Fedora:
wget http://repo.opensource-sw.net/fedora/ossw.repo -P /etc/yum.repos.d

You may wish to edit the repository file, perhaps to add a priorities setting.

=====Install vzpkg2 and pkg-cacher=====

Once the repository is added in /etc/yum.repos.d, you can now install the new vzpkg2 and pkg-cacher from it:

yum install vzpkg2 vztmpl2-centos vztmpl2-fedora vztmpl2-debian vztmpl2-ubuntu
yum install pkg-cacher-sa

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it by running as root:

service pkg-cacher restart

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running, then run as root:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

====Debian Installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

apt-get erase vzpkg vzctl-ostmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Installation on Debian]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Add the deb repositories to your /etc/apt/sources.list:=====

Add the following lines to your /etc/apt/sources.list:

Etch:
deb http://repo.opensource-sw.net/debian/ etch openvz
deb-src http://repo.opensource-sw.net/debian/ etch openvz

Sarge:
deb http://repo.opensource-sw.net/debian/ sarge openvz
deb-src http://repo.opensource-sw.net/debian/ sarge openvz

Then do:
apt-get update
apt-get install pkg-cacher-sa vzpkg2

=====Adding New Templates:=====

Install the desired OS Template Metadata packages:

apt-get install vztmpl2-centos vztmpl2-fedora vztmpl2-ubuntu vztmpl2-debian

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it.

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running, then run as root:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

===Source===

The source for the new vzpkg2 and templates is available on http://git.opensource-sw.net. In order to clone the updated source use the command:
git clone http://git.opensource-sw.net/git/vzpkg

The templates are available using:
git clone http://git.opensource-sw.net/git/vztmpl

Install vzpkg2 and pkg-cacher

2008-11-26T15:20:08Z

Dowdle: /* Adding New Templates: */

=== Introduction ===

Robert Nelson has created a couple new utilities to make managing and updating templates and containers easier, vzpkg2 pkg-cacher. So far they will create and update a large range of containers, including both 32bit and 64bit of the following:

* Centos 4 and 5,
* Fedora 7, 8 and 9,
* Debian Sarge and Etch,
* Ubuntu Feisty, Gutsy and Hardy.

Pkg-cacher is a transparent caching proxy daemon optimized for Debian and RPM packages. In other terms, pkg-cacher is a service that runs on a machine that other machines and containers, or "clients", use to update themselves instead of each of them directly hitting the package repositories. Pkg-cacher only downloads a file once and then gives that to all its clients, instead of each of the clients downloading the file from the Internet at large. It is based on [http://www.nick-andrew.net/projects/apt-cacher/ apt-cacher], available with Debian. This version has been modified to understand RedHat RPM repositories. It also adds support for the HTTP Range header and deals correctly with files which have the same name but different content on different distributions or in some cases different versions of the same distribution.

Robert has setup repositories for Fedora, CentOS and Debian.

====Screencast====

Scott Dowdle has recorded a good screencast overview of vzpkg2 and pkg-cacher at:

http://www.montanalinux.org/vzpkg2-screencast.html

===Installation===

====Centos & Fedora installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

yum remove vzpkg vztmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Quick installation]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Download the repository file for your OS=====

For CentOS:
wget http://repo.opensource-sw.net/centos/ossw.repo -P /etc/yum.repos.d

For Fedora:
wget http://repo.opensource-sw.net/fedora/ossw.repo -P /etc/yum.repos.d

You may wish to edit the repository file, perhaps to add a priorities setting.

=====Install vzpkg2 and pkg-cacher=====

Once the repository is added in /etc/yum.repos.d, you can now install the new vzpkg2 and pkg-cacher from it:

yum install vzpkg2 vztmpl2-centos vztmpl2-fedora vztmpl2-debian vztmpl2-ubuntu
yum install pkg-cacher-sa

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it by running as root:

service pkg-cacher restart

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running, then run as root:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

====Debian Installs:====

=====Remove Old Packages=====
If this is an '''existing''' install, uninstall your vzpkg and vztmpl-* packages:

apt-get erase vzpkg vzctl-ostmpl-*

and backup & remove your current template directory:

tar cjf /some/backup/location/old_templates.tbz /vz/template
rm -r /vz/template

If this is a '''new''' install, you should probably review the [http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf OpenVZ User's Guide] and the wiki's [[Installation on Debian]] page. The only way you would vary your installation setups is declining to install the default vzpkg package, and instead using vzpkg2 here.

=====Add the deb repositories to your /etc/apt/sources.list:=====

Add the following lines to your /etc/apt/sources.list:

Etch:
deb http://repo.opensource-sw.net/debian/ etch openvz
deb-src http://repo.opensource-sw.net/debian/ etch openvz

Sarge:
deb http://repo.opensource-sw.net/debian/ sarge openvz
deb-src http://repo.opensource-sw.net/debian/ sarge openvz

Then do:
apt-get update
apt-get install pkg-cacher-sa vzpkg2

=====Adding New Templates:=====

Install the desired OS Template Metadata packages:

apt-get install vztmpl2-centos vztmpl2-fedora vztmpl2-ubuntu vztmpl2-debian

Then move the templates to where Debian expects them:

mv /vz/template/* /var/lib/vz/template/

=====Configure vzpkg2=====

Open /etc/vz/vzpkg.conf in an editor. Replace 'hostname' with the hostname or IP of the machine you are installing this on for VZPKG_CACHE_HOST, make sure not to use 'localhost', because this name is what OpenVZ Containers will use to access the pkg-cacher daemon:

VZPKG_CACHE_HOST=hostname:3142

While you are here, review this file to ensure it makes sense for your setup. In particular, you will probably have to update the VZPKG_DNS line with IP addresses of DNS servers you use.

VZPKG_DNS=192.168.1.2,192.168.1.3

=====Configure pkg-cacher=====

Edit /etc/pkg-cacher/pkg-cacher.conf. You should read the included documentation in the file to ensure it is appropriate for your setup. Mostly the defaults will work just fine. By default pkg-cacher will let any system use its cache. You will probably want to limit it to your own systems on the line:

allowed_hosts=*

Once you have checked and updated pkg-cacher.conf, simply restart it.

=====Generate the new template cache=====

Now everything should be ready to go! Make sure both the 'vz' service and 'pkg-cacher' service are running, then run as root:

vzpkgcache

vzpkg2 should get to work generating your initial caches. Now you can run 'vzctl create' and use them.

===Source===

The source for the new vzpkg2 and templates is available on http://git.opensource-sw.net. In order to clone the updated source use the command:
git clone http://git.opensource-sw.net/git/vzpkg

The templates are available using:
git clone http://git.opensource-sw.net/git/vztmpl

Install vzpkg2 and pkg-cacher

2008-11-19T18:12:33Z

Dowdle: Initial place holder entry

This is a place holder for the page BurnMage is going to update with instructions culled from the OpenVZ Users mailing list... from emails by Robert Nelson on how to install vzpkg2 and pkg-cacher.

Differences between venet and veth

2008-06-17T20:56:13Z

Dowdle: There were a few typos... and I changed veth to venet with regards to speed and the host node admin config.

OpenVZ provides you to use either [[veth]] (Virtual eTHernet) or [[venet]] (Virtual NETwork) devices (or both) for in-[[CT]] networking. Here we describe the differences between those devices.

* ''veth'' allows broadcasts in CT, so you can use even a DHCP server inside a CT, or a samba server with domain broadcasts or other such stuff.
* ''veth'' has some security implications, so is not recommended in untrusted environments like HSP. This is due to broadcasts, traffic sniffing, possible IP collisions etc. i.e. CT's user can actually ruin your ethernet network with such direct access to ethernet layer.
* With ''venet'' device, only OpenVZ host node administrator can assign an IP to a CT. With ''veth'' device, network settings can be fully done on CT side by the CT administrator. CT should setup correct gateway, IP/netmask etc. and then a [[HN|node]] admin can only choose where your traffic goes.
* ''veth'' devices can be bridged together and/or with other devices. For example, in host system admin can bridge ''veth'' from 2 CTs with some VLAN eth0.X. In this case, these 2 CTs will be connected to this VLAN.
* ''venet'' device is a bit faster and more efficient.
* With ''veth'' devices, IPv6 auto generates an address from MAC.

The brief summary:
{| class="wikitable" style="text-align: center;"
|+ '''Differences between veth and venet'''
! Feature !! [[veth]] !! [[venet]]
|-
! MAC address
| {{yes}} || {{no}}
|-
! Broadcasts inside CT
| {{yes}} || {{no}}
|-
! Traffic sniffing
| {{yes}} || {{no}}
|-
! Network security
| style="background: #ffdddd" | Low <ref>Due to broadcasts, sniffing and possible IP collisions etc.</ref>
| style="background: #ddffdd" | High
|-
! Can be used in bridges
| {{yes}} || {{no}}
|-
! Performance
| style="background: #ffdddd" | Fast
| style="background: #ddffdd" | Fastest
|-
|}
<references/>

[[Category: Networking]]

Installation on Debian/old

2008-03-07T22:18:09Z

Dowdle: Added net.ipv4.ip_forward=1 as instructed by a Debian user who said it was needed.

OpenVZ consists of a kernel, user-level tools, and VE templates.

This guide tells how to install the kernel and the tools on [http://www.debian.org Debian] Stable.

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for VEs private directories (by default /var/lib/vz/private/<veid>). The reason why you should do so is that if you wish to use OpenVZ per-VE disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind, that per-VE quota in this context includes not only pure per-VE quota, but also usual Linux disk quota used in VE, not on [[HN]].

At least try to avoid using root partition for VEs, because the root user of VE will be able to overcome 5% disk space barrier in some situations. This way HN root partition can be completely filled and it will break the system.

OpenVZ per-VE disk quota is supported only for ext2/ext3 filesystems. So use one of these filesystems (ext3 is recommended) if you need per-VE disk quota.

=== Repository setup ===

At the moment two different repositories are online at http://download.openvz.org :

* by Ola Lundqvist <opal@debian.org>
: (OpenVZ Kernels only)
: apt-uri http://download.openvz.org/debian

* by Thorsten Schifferdecker <tsd@debian.systs.org>
: apt-uri http://download.openvz.org/debian-systs
: (Mirror of OpenVZ Repository from http://debian.systs.org/)

{{Note|The next steps used the Repository at http://download.openvz.org/debian-systs, the actually OpenVZ Tools for Debian are exist only in unstable, see http://packages.debian.org/vzctl}}

{{Note|per default on Ubuntu system, root task are done with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by the following commands, as root or as privileged "sudo" user

<pre>
# [sudo] echo "deb http://download.openvz.org/debian-systs etch openvz" >> /etc/apt/sources.list
# wget http://download.openvz.org/debian-systs/dso_archiv_signing_key.asc
# [sudo] apt-key add dso_archiv_signing_key.asc
# [sudo] apt-get update
</pre>

== Kernel installation ==

{{Note|In case you want to recompile the OpenVZ kernel yourself on Debian, see [[Compiling the OpenVZ Kernel (the debian way)]].}}

First, you need to choose what kernel you want to install.

{| class="wikitable"
|+'''OpenVZ Kernel list built with kernel config from http://download.openvz.org'''
! kernel !! Description !! Hardware !! Debian Architektur
|-
! ovzkernel-2.6.18
| uniprocessor
| up to 4GB of RAM
| i386 and amd64
|-
! ovzkernel-2.6.18-smp
| symmetric multiprocessor
| up to 4 GB of RAM
| i386 and amd64
|-
! ovzkernel-2.6.18-enterprise
| SMP + PAE support + 4/4GB split
| up to 64 GB of RAM
| i386 only
|}

{| class="wikitable"
|+'''OpenVZ Kernel list built with official Debian kernel config and OpenVZ Settings'''
! kernel !! Description !! Hardware !! Debian Architektur
|-
! fzakernel-2.6.18-686
| uni- and multiprocessor
| up to 4GB of RAM
| i386
|-
! fzakernel-2.6.18-686-bigmem
| symmetric multiprocessor
| up to 64 GB of RAM
| i386
|-
! fzakernel-2.6.18-amd64
| uni- and multiprocessor
|
| amd64
|-
|}

<pre>
# apt-get install <kernel>
</pre>

=== Configuring the bootloader ===

In case GRUB is used as the boot loader, it will be configured automatically, or execute update-grub; lines similar to these will be added to the <tt>/boot/grub/menu.lst</tt> file:

<pre>
[...]
title Debian GNU/Linux, kernel 2.6.18-ovz-028stab051.1-686
root (hd0,1)
kernel /vmlinuz-2.6.18-ovz-028stab051.1-686 root=/dev/sda5 ro vga=791
initrd /initrd.img-2.6.18-ovz-028stab051.1-686
savedefault
[...]
</pre>

{{Note|per default on debian/ubuntu, a 2.6.22 kernel will boot before a 2.6.18, please check manually the grub boot order. See man update-grub for more details}}

=== Rebooting into OpenVZ kernel ===

{{Warning|Before you restart your Server, keep in mind, that your system has all needed modules enabled; booting from your harddisk (e.g. hardware modules, raid system(s), lvm2 etc). May you need a INITRD (initramdisk) or compile needed kernel modules statically in.}}

Now reboot the machine and choose the OpenVZ Linux Kernel on the boot loader menu. If the OpenVZ kernel has been booted successfully, proceed to installing the user-level tools for OpenVZ.

== Installing the user-level tools ==

OpenVZ needs some user-level tools installed. Those are:

; vzctl
: A utility to control OpenVZ VPSs (create, destroy, start, stop, set parameters etc.)
; vzquota
: A utility to manage quotas for VPSs. Mostly used indirectly (by vzctl).

<pre>
# [sudo] apt-get install vzctl vzquota
</pre>

== Configuring ==

=== sysctl ===

There are a number of kernel parameters that should be set for OpenVZ to work correctly. These parameters are stored in <tt>/etc/sysctl.conf</tt> file. Here is the relevant part of the file; please edit it accordingly.

{{Note|vzctl version from debian-systs, automate changing sysctl options for openvz}}

<pre>
[...]

# On Hardware Node we generally need
# packet forwarding enabled and proxy arp disabled

net.ipv4.conf.default.forwarding=1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.ip_forward=1

# Enables source route verification
net.ipv4.conf.all.rp_filter = 1

# Enables the magic-sysrq key
kernel.sysrq = 1

# TCP Explict Congestion Notification
#net.ipv4.tcp_ecn = 0

# we do not want all our interfaces to send redirects
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0

[...]
</pre>

{{Note|You can make a symlink from /var/lib/vz to /vz as backward compability to Main OpenVZ
(Debian vz root directory is installed FHS-like to /var/lib/vz}}

# [sudo] ln -s /var/lib/vz /vz

=== VE OS Templates ===

To install a VE, you need VE OS Template(s), precreated can be found [http://download.openvz.org/contrib/template/precreated/ here] or create it : [http://wiki.openvz.org/Debian_template_creation Debian] , [http://wiki.openvz.org/Ubuntu_Gutsy_template_creation ubuntu] and all infos about [http://wiki.openvz.org/Category:Templates Templates]

{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}

# [sudo] apt-get install vzctl-ostmpl-debian

== Additial user tools ==

; vzprocps
: A set of utilities to provide system information (vzps and vztop)
:
; [http://wiki.openvz.org/Backup_of_a_running_VE_with_vzdump vzdump]
: A utility to backup and restore VE.

# [sudo] apt-get install vzprocps vzdump

== Use it! ==

After installing the OpenVZ kernel, user tools and a Minimal VE OS Template create a first VE and
do some [[Basic operations in OpenVZ environment]] and read the [[download:doc/OpenVZ-Users-Guide.pdf|doc/OpenVZ-Users-Guide.pdf]] and browse this wiki.

[[Category: HOWTO]]
[[Category: Installation]]

Migration from one HN to another

2007-09-09T02:51:45Z

Dowdle:

I just wanted to get the content out there. Could someone pretty this thing up?

The vzmigrate script is used to migrate a Virutal Environment from one Hardware Node to another.

You first have to setup SSH to permit the old HN to be able to login to the new HN without a password prompt. Run the following on the old HN.

<pre>[root@OpenVZ ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Created directory '/root/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
74:7a:3e:7f:27:2f:42:bb:52:4c:ad:55:31:6f:79:f2 root@OpenVZ.ics.local
[root@OpenVZ ~]# cd .ssh/
[root@OpenVZ .ssh]# ls -al
total 20
drwx------ 2 root root 4096 Aug 11 09:41 .
drwxr-x--- 5 root root 4096 Aug 11 09:40 ..
-rw------- 1 root root 887 Aug 11 09:41 id_rsa
-rw-r--r-- 1 root root 231 Aug 11 09:41 id_rsa.pub
[root@OpenVZ .ssh]# scp id_rsa.pub root@10.1.5.6:./id_rsa.pub
The authenticity of host '10.1.5.6 (10.1.5.6)' can't be established.
RSA key fingerprint is 3f:2a:26:15:e4:37:e2:06:b8:4d:20:ee:3a:dc:c1:69.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.1.5.6' (RSA) to the list of known hosts.
root@10.1.5.6's password:
id_rsa.pub 100% 231 0.2KB/s 00:00</pre>

Run the following on the new HN.

<pre>[root@Char ~]# cd .ssh/
[root@Char .ssh]# touch authorized_keys2
[root@Char .ssh]# chmod 600 authorized_keys2
[root@Char .ssh]# cat ../id_rsa.pub >> authorized_keys2
[root@Char .ssh]# rm ../id_rsa.pub
rm: remove regular file `../id_rsa.pub'? y</pre>

Run the following on the old HN.

<pre>[root@OpenVZ .ssh]# ssh -2 -v root@10.1.5.6
OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 10.1.5.6 [10.1.5.6] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type 1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.9p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '10.1.5.6' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: An invalid name was supplied
Cannot determine realm for numeric host address

debug1: An invalid name was supplied
Cannot determine realm for numeric host address

debug1: Next authentication method: publickey
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 149
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
Last login: Thu Aug 9 16:41:30 2007 from 10.1.5.20
[root@Char ~]# exit</pre>

Now that the vzmigrate script will function, a little bit on vzmigrate.

<pre>This program is used for VE migration to another node
Usage:
vzmigrate [-r yes|no] [--ssh=<options>] [--keep-dst] [--online] [-v]
destination_address <VEID>
Options:
-r, --remove-area yes|no
Whether to remove VE on source HN for successfully migrated VE.
--ssh=<ssh options>
Additional options that will be passed to ssh while establishing
connection to destination HN. Please be careful with options
passed, DO NOT pass destination hostname.
--keep-dst
Do not clean synced destination VE private area in case of some
error. It makes sense to use this option on big VE migration to
avoid syncing VE private area again in case some error
(on VE stop for example) occurs during first migration attempt.
--online
Perform online (zero-downtime) migration: during the migration the
VE hangs for a while and after the migration it continues working
as though nothing has happened.
-v
Verbose mode. Causes vzmigrate to print debugging messages about
its progress (including some time statistics).</pre>

Here is an example of migrating VE 101 from the current HN to one at 10.1.5.6:

<pre>[root@OpenVZ .ssh]# vzmigrate 10.1.5.6 101
OPT:10.1.5.6
Starting migration of VE 101 on 10.1.5.6
Preparing remote node
Initializing remote quota
Syncing private
Syncing 2nd level quota
Turning quota off
Cleanup</pre>

Here's a simple shell script that will migrate each VPS one after another. Just pass the destination host node as the single argument to the script. Feel free to add the -v flag to the vzmigrate flags if you'd like to see it execute with the verbose option:

<pre>#!/bin/bash
echo host=$1
vzlist | tail -n +2 | awk 'BEGIN { } /.*/ { print $1 }' | xargs -n1 echo vzmigrate --remove-area no --keep-dsk $1</pre>

[[Category:HOWTO]]

Basic operations in OpenVZ environment

2007-08-15T02:30:36Z

Dowdle:

This article assumes you have already [[Quick installation|installed OpenVZ]] and prepared the [[OS template cache]](s). If not, follow the links to perform the steps needed.

To create and start a [[VE]], run the following commands:
<pre>
[host-node]# vzctl create VEID --ostemplate osname
[host-node]# vzctl set VEID --ipadd a.b.c.d --save
[host-node]# vzctl set VEID --nameserver a.b.c.d --save
[host-node]# vzctl start VEID
</pre>

Here <tt>VEID</tt> is the numeric ID for the VE; <tt>osname</tt> is the name of the OS template for the VE, and <tt>a.b.c.d</tt> is the IP address to be assigned to the VE.

Example:
<pre>
[host-node]# vzctl create 101 --ostemplate fedora-core-5-minimal
[host-node]# vzctl set 101 --ipadd 10.1.2.3 --save
[host-node]# vzctl set 101 --nameserver 10.0.2.1 --save
[host-node]# vzctl start 101
</pre>

Your freshly-created VE should be up and running now; you can see its processes:

<pre>
[host-node]# vzctl exec VEID ps ax
</pre>

To enter VE give the following command:
<pre>
[host-node]# vzctl enter VEID
entered into VPS VEID
[ve]#
</pre>

To exit from VE, just type <code>exit</code> and press enter:
<pre>
[ve]# exit
exited from VPS VEID

[host-node]#
</pre>

To stop VE:

<pre>
[host-node]# vzctl stop VEID
Stopping VPS ...
VPS was stopped
VPS is unmounted
</pre>

And to destroy VE:
<pre>
[host-node]# vzctl destroy VEID
Destroying VPS private area: /vz/private/VEID
VPS private area was destroyed
</pre>

Now, when you know how to manage your [[VE]], learn about [[Resource management]].

[[Category: Installation]]
[[Category: HOWTO]]

LinuxWorld2007

2007-07-18T17:08:45Z

Dowdle: Opps, didn't get it right the first time.

OpenVZ will have a exhibit space at [http://linuxworldexpo.com/live/12/ LinuxWorld Conference and Expo], which will be held 6 to 9 August 2007 in San Francisco, California.

This page serves as a hub for ideas about what we gonna do at our booth and beyond, as well as a plan.

== Ideas ==

=== Community participation ===
* Made announces here ([[Template:Main page announce]]), at the mailing lists, forum, [http://community.livejournal.com/openvz/15447.html blog]

=== Hand-outs ===
* live CDs + install DVDs
* OpenVZ brochure

=== Timed events ===
* Quiz with OpenVZ T-shirts for winners (e.g. two times a day at a predefined time)

=== Demos ===
Either on request or at predefined times

* OpenVZ live demo, including migration (see [[demo scripts]]) -- on a few notebooks/workstations
* OpenVZ on Xen demo
* OpenVZ on VMware/Parallels demo

=== Hiring ===

We seek for and hire kernel developers to participate in OpenVZ.

== Crew ==

The following people are gonna be at the booth:
* [[User:Kir|Kir Kolyshkin]], OpenVZ project manager, t-shirt: '''L'''.
* Konstantin Khorenko, OpenVZ kernel team member, t-shirt: '''M'''.
* Scott Dowdle, BozemanLUG (Bozeman, Montana), t-shirt: '''XXL'''.
* Warren Sanders, BillingsLUG (Billings, Montana), t-shirt: '''XL'''.
* Marc Perkel

If you wanna join and be a part of OpenVZ crew at the event, it's not too late yet -- email kir-AT-openvz.org.

=== Schedule ===

This table lists who is on-duty for the OpenVZ booth at given times. Those are minimally required times; feel free to spend more time at the booth.

{| class="wikitable"
!| When/Who
!| Kir
!| Kostya
!| Scott
!| Warren
!| Marc
|-
|| Tuesday, 7th, 9am to 1pm
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
|| Tuesday, 7th, 1pm to 5pm
| {{yes}}
| {{yes}}
| {{yesno}}
| .
| .
|-
|-
|| Wednesday, 8th, 10am to 1:30pm
| .
| .
| {{yes}}
| {{yes}}
| {{yesno}}
|-
|| Wednesday, 8th, 1:30pm to 5pm
| .
| {{yes}}
| {{yes}}
| {{yesno}}
| .
|-
|-
|| Thursday, 9th, 10am to 1pm
| {{yesno}}
| .
| .
| {{yes}}
| {{yes}}
|-
|| Thursday, 9th, 1pm to 4 pm
| {{yes}}
| {{yesno}}
| .
| .
| {{yes}}
|}

== See also ==
* [[Demo scripts]]

LinuxWorld2007

2007-07-18T17:08:15Z

Dowdle: Added tee-shirts sizes for Scott and Warren and updated LUG references

OpenVZ will have a exhibit space at [http://linuxworldexpo.com/live/12/ LinuxWorld Conference and Expo], which will be held 6 to 9 August 2007 in San Francisco, California.

This page serves as a hub for ideas about what we gonna do at our booth and beyond, as well as a plan.

== Ideas ==

=== Community participation ===
* Made announces here ([[Template:Main page announce]]), at the mailing lists, forum, [http://community.livejournal.com/openvz/15447.html blog]

=== Hand-outs ===
* live CDs + install DVDs
* OpenVZ brochure

=== Timed events ===
* Quiz with OpenVZ T-shirts for winners (e.g. two times a day at a predefined time)

=== Demos ===
Either on request or at predefined times

* OpenVZ live demo, including migration (see [[demo scripts]]) -- on a few notebooks/workstations
* OpenVZ on Xen demo
* OpenVZ on VMware/Parallels demo

=== Hiring ===

We seek for and hire kernel developers to participate in OpenVZ.

== Crew ==

The following people are gonna be at the booth:
* [[User:Kir|Kir Kolyshkin]], OpenVZ project manager, t-shirt: '''L'''.
* Konstantin Khorenko, OpenVZ kernel team member, t-shirt: '''M'''.
* Scott Dowdle, BozemanLUG (Bozeman, Montana), t-shirt: '''XL'''.
* Warren Sanders, BillingsLUG (Billings, Montana), t-shirt: '''XXL'''.
* Marc Perkel

If you wanna join and be a part of OpenVZ crew at the event, it's not too late yet -- email kir-AT-openvz.org.

=== Schedule ===

This table lists who is on-duty for the OpenVZ booth at given times. Those are minimally required times; feel free to spend more time at the booth.

{| class="wikitable"
!| When/Who
!| Kir
!| Kostya
!| Scott
!| Warren
!| Marc
|-
|| Tuesday, 7th, 9am to 1pm
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
|| Tuesday, 7th, 1pm to 5pm
| {{yes}}
| {{yes}}
| {{yesno}}
| .
| .
|-
|-
|| Wednesday, 8th, 10am to 1:30pm
| .
| .
| {{yes}}
| {{yes}}
| {{yesno}}
|-
|| Wednesday, 8th, 1:30pm to 5pm
| .
| {{yes}}
| {{yes}}
| {{yesno}}
| .
|-
|-
|| Thursday, 9th, 10am to 1pm
| {{yesno}}
| .
| .
| {{yes}}
| {{yes}}
|-
|| Thursday, 9th, 1pm to 4 pm
| {{yes}}
| {{yesno}}
| .
| .
| {{yes}}
|}

== See also ==
* [[Demo scripts]]