OpenVZ Virtuozzo Containers Wiki - User contributions [en]

User talk:Perchrh

2008-03-06T12:34:38Z

Perchrh:

== Why vzctl-lib? ==

In your edit [http://wiki.openvz.org/w/index.php?title=OS_template_cache_preparation&curid=1436&diff=4230&oldid=4162&rcid=4301], you added vzctl-lib to yum command needed to install vzpkg. I think that vzpkg depends on vzctl, which in turn depends on vzctl-lib, so it should be picked up automatically. Was it the case for you that vzpkg didn't work unless being installed with explicit mention of vzctl-lib, or you just added that for some other reason? I'm going to revert your edit but really need to know why you did it.

Thank you for working with our wiki! --[[User:Kir|Kir]] 15:06, 5 March 2008 (EST)

: Yes, you are right. The reason I added it is that on my centos 5 x86-64 machine I was not able to run vzpkg, it failed because it tried calling a script which is part of vzctl-lib. As you say there should be a dependency in place. My experience is that it is missing. Therefore I recommend to add vzctl-lib to the yum-command. It will not cause any problems if the dependency is in place, right? {{Unsigned|Perchrh|13:55, 6 March 2008}}

:: I have checked that vzpkg requires vzctl, and vzctl requires vzctl-lib. So this dependency should be picked up automatically by yum. In case it's not working that way we should file a bug for yum. Could you please re-check the issue? --[[User:Kir|Kir]] 05:06, 6 March 2008 (EST)

::: Alright,
:::<code>
:::[root@osl2r134 ~]# rpm -q --whatrequires vzctl-lib
:::vzctl-3.0.22-1
:::</code>

:::The dependency is in place, so I would call it a bug in yum. I'll see if I have time (work is crazy) to reproduce the problem later.
:::--
:::PER

User talk:Perchrh

2008-03-06T12:34:13Z

Perchrh:

== Why vzctl-lib? ==

In your edit [http://wiki.openvz.org/w/index.php?title=OS_template_cache_preparation&curid=1436&diff=4230&oldid=4162&rcid=4301], you added vzctl-lib to yum command needed to install vzpkg. I think that vzpkg depends on vzctl, which in turn depends on vzctl-lib, so it should be picked up automatically. Was it the case for you that vzpkg didn't work unless being installed with explicit mention of vzctl-lib, or you just added that for some other reason? I'm going to revert your edit but really need to know why you did it.

Thank you for working with our wiki! --[[User:Kir|Kir]] 15:06, 5 March 2008 (EST)

: Yes, you are right. The reason I added it is that on my centos 5 x86-64 machine I was not able to run vzpkg, it failed because it tried calling a script which is part of vzctl-lib. As you say there should be a dependency in place. My experience is that it is missing. Therefore I recommend to add vzctl-lib to the yum-command. It will not cause any problems if the dependency is in place, right? {{Unsigned|Perchrh|13:55, 6 March 2008}}

:: I have checked that vzpkg requires vzctl, and vzctl requires vzctl-lib. So this dependency should be picked up automatically by yum. In case it's not working that way we should file a bug for yum. Could you please re-check the issue? --[[User:Kir|Kir]] 05:06, 6 March 2008 (EST)

::: Alright,
<code>
[root@osl2r134 ~]# rpm -q --whatrequires vzctl-lib
vzctl-3.0.22-1
</code>

The dependency is in place, so I would call it a bug in yum. I'll see if I have time (work is crazy) to reproduce the problem later.
--
PER

User talk:Perchrh

2008-03-06T12:33:43Z

Perchrh:

== Why vzctl-lib? ==

In your edit [http://wiki.openvz.org/w/index.php?title=OS_template_cache_preparation&curid=1436&diff=4230&oldid=4162&rcid=4301], you added vzctl-lib to yum command needed to install vzpkg. I think that vzpkg depends on vzctl, which in turn depends on vzctl-lib, so it should be picked up automatically. Was it the case for you that vzpkg didn't work unless being installed with explicit mention of vzctl-lib, or you just added that for some other reason? I'm going to revert your edit but really need to know why you did it.

Thank you for working with our wiki! --[[User:Kir|Kir]] 15:06, 5 March 2008 (EST)

: Yes, you are right. The reason I added it is that on my centos 5 x86-64 machine I was not able to run vzpkg, it failed because it tried calling a script which is part of vzctl-lib. As you say there should be a dependency in place. My experience is that it is missing. Therefore I recommend to add vzctl-lib to the yum-command. It will not cause any problems if the dependency is in place, right? {{Unsigned|Perchrh|13:55, 6 March 2008}}

:: I have checked that vzpkg requires vzctl, and vzctl requires vzctl-lib. So this dependency should be picked up automatically by yum. In case it's not working that way we should file a bug for yum. Could you please re-check the issue? --[[User:Kir|Kir]] 05:06, 6 March 2008 (EST)

::: Alright,
<code>
[root@osl2r134 ~]# rpm -q --whatrequires vzctl-lib
vzctl-3.0.22-1
</code>
The dependency is in place, so I would call it a bug in yum. I'll see if I have time (work is crazy) to reproduce the problem later.
--PER

User talk:Perchrh

2008-03-06T09:55:02Z

Perchrh:

User talk:Perchrh

2008-03-06T09:39:26Z

Perchrh:

NFS

2008-03-06T09:30:06Z

Perchrh:

This page describes how to mount NFS partition inside VE.

== NFS server ==
Currently OpenVZ kernel doesn't include kernel NFS server support. However you are still able to use user space [[NFS server inside VE]].

== NFS client ==
=== Preparations ===
==== Prerequisites ====
You will need the following software:

# [http://openvz.org/download/utils#vzctl vzctl] version 3.0.13 or higher (do <code>vzctl --version</code>)
# [http://openvz.org/download/kernel/ kernel] version 2.6.18-028test006 or higher (2.6.18-028stab* will do), or any recent RHEL5-based or 2.6.20-based kernel.

Note: In all the kernels earlier than 028stab038, kernel NFS support can be given to a VE by setting:

sunrpc.ve_allow_rpc = 1
fs.nfs.ve_allow_nfs = 1
kernel.ve_allow_kthreads = 1

This can be done by adding the above lines into /etc/sysctl.conf on the hardware node, and then running <code>sysctl -p</code>.

===== Debian Notes =====

Debian Etch still uses vzctl version 3.0.11 and so NFS client support is not yet available. Lenny presently has version 3.0.18.

==== Prepare the HN ====

For NFS mounts to work in the VEs with the RHEL5-based kernels you must enable kernel threads in the VE by setting "kernel.ve_allow_kthreads=1" in /etc/sysctl.conf

<pre>
# modprobe nfs
</pre>

==== Prepare the VE ====
To allow a VE use NFS filesystem, you will need to start it with "nfs" feature enabled. If the VE is running while you set the --features "nfs:on", you will need to reboot it.
<pre>
# vzctl set 101 --features "nfs:on" --save
# vzctl start 101
</pre>

After this you may see nfs in <code>/proc/filesystems</code>
<pre>
# vzctl exec 101 cat /proc/filesystems
ext3
ext2
nodev rpc_pipefs
nodev proc
nodev nfs
nodev sysfs
nodev tmpfs
nodev devpts
</pre>

=== Mounting NFS ===
Assuming that you already have NFS server set up at <code>192.168.0.1:/nfs_pub</code> mounting will be simple
<pre>
# vzctl enter 100
# mkdir /nfs
# mount -t nfs 192.168.0.1:/nfs_pub /nfs
# cat /proc/mounts
simfs / simfs rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw 0 0
nfs /nfs nfs rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.0.1 0 0
</pre>

For more details on how to setup NFS mount see [http://nfs.sourceforge.net/nfs-howto/ar01s04.htm NFS-client HOWTO]

=== Known issues ===
There are quite a few parameters in NFS, so sometimes it doesn't work due to misconfiguration. We've created a separate
page describing those situations: [[ NFS doesn't work ]]

[[Category: HOWTO]]

OS template cache preparation

2008-03-05T14:32:37Z

Perchrh:

This article describes the procedure of an OS template cache creation. It assumes you already have OpenVZ installed and running. The steps needed to achieve it are documented in the [[Quick installation]] document.

== Terminology ==

Please make sure you understand these terms:

* [[OS template]]
* [[OS template metadata]]
* [[OS template cache]]

== Creating an OS template cache ==
You can create an [[OS template cache]] using template utilities and [[OS template metadata]] right on your [[hardware node]]. The process is automated and will take from about 10 minutes to a few hours, depending on the network speed, and the result will be most up-to-date template cache.

=== Installing template utilities ===

You have to install a few packages in order to be able to create/update OS template cache(s).

==== Using yum ====
<pre>
# yum install vzpkg vzyum vzrpm43-python vzrpm44-python vzctl-lib
</pre>

==== Using rpm ====
Packages are available from [http://openvz.org/download/template/utils/ Download » Templates » Utilities]. You need both <tt>vzpkg</tt> and <tt>vzyum</tt> packages, as well as one or both <tt>vzrpm43</tt>/<tt>vzrpm44</tt> (including their <tt>-python</tt> counterparts), depending on the OS templates being used.

Install these utilities using rpm:

<pre>
# rpm -ihv vzpkg*.rpm vzyum*.rpm vzrpm44*.rpm
</pre>

In Red Hat Enterprise Linux, to install <tt>vzyum</tt> you will need <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=python-elementtree&system=redhat python-elementtree]</tt>, <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=python-sqlite&system=redhat python-sqlite]</tt>, and <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=python-urlgrabber&system=redhat python-urlgrabber]</tt>. These packages might have dependencies of their own. For example, <tt>python-sqlite</tt> needs <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=sqlite&system=redhat sqlite]</tt>.

=== Installing OS template metadata ===

To create an [[OS template cache]], you need to get the [[OS template metadata|metadata]] for the chosen OS template(s).

==== Using yum ====
To see which templates are available, run
<pre>
# yum search vztmpl
</pre>

To install some of the templates, run
<pre>
# yum install vztmpl-XXX [...]
</pre>

==== Using rpm ====
Get the chosen <tt>vztmpl-*</tt> packages from [http://openvz.org/download/template/metadata/ Downloads » Templates » Metadata] (or directly from [http://download.openvz.org/template/metadata/ download.openvz.org/template/metadata] or one of the [[Download mirrors|mirrors]] and install them:

<pre>
# rpm -ihv vztmpl-*.rpm
</pre>

=== Installing repository cache (optional) ===

Optionally, you may want to get a snapshot of the local copy of the package repository for the chosen OS template(s). This is not required but might speed up the initial OS template cache creation considerably. The tarballs are available from [http://openvz.org/download/template/repocache/ Downloads » Templates » Repo Cache]; download and untar them to the <tt>/vz/template</tt> directory on your OpenVZ [[Hardware Node]]. If you choose to skip this step, all the needed files will be downloaded from the Internet automatically when needed.

Note - The cache may be out of date meaning you end up downloading them all again anyway.

=== Running <tt>vzpkgcache</tt> ===

Run the <tt>vzpkgcache</tt> utility; see the vzpkgcache(8) man page for details. It will create or update the caches of all the templates for which the corresponding metadata exist.

# vzpkgcache centos-4-i386-minimal

== Alternative: use precreated template cache ==

As an alternative to creating a cache using template metadata, you can use precreated template cache taken from [http://openvz.org/download/template/cache Downloads » Templates » Precreated], or directly from [http://download.openvz.org/template/precreated/ download.openvz.org/template/precreated], or from one of the [[Download mirrors|mirrors]].

Precreated templates can be easily updated using the following algorithm:
# create temporary [[container]] based on template
# update [[container]] using OS-specific tools (yum, apt or similar)
# pack [[container]] as a new template
Examples of this procedure are described in details at [[Updating Ubuntu template]], [[Updating Debian template]], [[Fedora template update]]

In order to use precreated template cache files, download files for chosen OS distributions and place them as-is (no unpacking needed) to the <tt>/vz/template/cache</tt> directory.

'''NOTE:''' If you use precreated CentOS-4 templates and wish to install software using vzyum, you will probably run into error like this:

[root@localhost tmp]# vzyum MYVPSID install mypackage
[root@localhost tmp]# ERROR: No such OS template: install

This might apply to Fedora also. To fix this problem, install the appropriate [[OS template metadata]] on the OpenVZ host, for example

yum install vztmpl-centos-4

== Next step ==

Follow on to the [[VE creation]] article.

[[Category: Installation]]
[[Category: Templates]]