Changes

Jump to: navigation, search

Quick installation (legacy)

4,704 bytes removed, 02:58, 27 November 2018
rm translate tags
{{Warning|This document briefly article describes the steps needed to install legacy version of OpenVZ on your (RPM based) machine. For '''Debian''' based systems current version, see [[Installation on DebianQuick installation]].}}
<!--T:1-->This document is also available in briefly describes the following languages: [http://forum.openvz.org/index.php?t=tree&amp;goto=35&amp;#msg_35 French], [http://forum.openvz.org/index.php?t=tree&amp;goto=1805&amp;#msg_1805 German],[http://wiki.openvz.jp Japanese]steps needed to install '''legacy''' OpenVZ on your '''RHEL 6''' (CentOS 6,[[Quick_installation_(SpanishScientific Linux 6)|Spanish]]machine.
OpenVZ consists of a kernel, user<!--T:2--level tools>For '''Debian''' based systems, and container templates. This guide tells how to install the kernel and the toolsplease see [[Installation on Debian]].
== Requirements ==<!--T:3-->This guide assumes you are running recent release {{Out|A commercial version of Fedora Core (like FC5) or RHEL/CentOS 4. CurrentlyOpenVZ is available, OpenVZ kernel tries to support the same hardware that Red Hat kernels supportwhich simplifies installation with a single disk as well as supports networked installation using PXE boot. For full hardware compatibility listTo learn more about Virtuozzo and request a free trial, please see [httphttps://www.swsoftvirtuozzo.com/en/products/virtuozzoopenvz/hcl/ Virtuozzo HCL].}}
==Requirements = 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 perT:5-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<!--T:6-->This guide assumes you are running '''RHEL (CentOS, Scientific Linux) 6''' on your system. Currently, because the root user of this is a container will be able recommended platform 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 systemrun OpenVZ on.
OpenVZ per=== /vz file system === <!--T:7-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? ===<!--T:8-->It is recommended to use a separate partition for containers (by default '''/vz''') and format it to '''ext4'''.
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.pre-setup === <!--T:9-->
=== yum pre<!--T:10--setup ===>If you want Download [https://download.openvz.org/openvz.repo openvz.repo] file and put it to use yum, you should set up OpenVZ your <code>/etc/yum .repos.d/</code> repository first.:
Download [http<!--T://download.openvz.org/openvz.repo openvz.repo] file and put it to your <code11-->/etc/yum.repos.d/</codepre> repository. This can be achieved by the following commands, as root:<prenowiki># cd wget -P /etc/yum.repos.d# wget http/ https://download.openvz.org/openvz.repo# rpm --import http://download.openvz.org/RPM-GPG-Key-OpenVZ</prenowiki> 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.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 !--T:12-ihv ovzkernel[-flavor]*.rpm></pre>Import OpenVZ GPG key used for signing RPM packages:
Here <code!--T:13-->[-flavor]</codepre> is optional, and can be <codenowiki>rpm --import http://download.openvz.org/RPM-GPG-Key-smpOpenVZ</codenowiki> or <code>-enterprise</codepre>. Refer to [[kernel flavors]] for more info.
{{Note|<tt>To make sure that you are downloading tamper free versions of the signed packages you should verify the fingerprint of the key you imported into the rpm -U</tt> (where <tt>-U</tt> stands for ''upgrade'') should '''not''' be used, otherwise all currently installed kernels will be uninstalledkey database as described on the [[Package signatures]] page.}}
== Configuring the bootloader Kernel installation ==<!--T:14-->
In case GRUB <!--T:15-->Limited OpenVZ functionality is used as the boot loadersupported when you run a recent 3.x kernel (check [[vzctl for upstream kernel]], it will be configured automatically: lines similar to these will be added to the <tt>/boot/grub/grubso OpenVZ kernel installation is optional but still recommended.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 /initrdT:16-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:# yum install vzkernel
== System configuration == <pre>title OpenVZ (2.6.8!-022stab029.1) root (hd0,0) kernel /vmlinuz-2.6.8T:17-022stab029.1 ro root=/dev/sda5 initrd /initrd-2.6.8-022stab029.1.img</pre>
== Configuring ==<!--T:18-->{{Note|With vzctl 4.4 or newer there is no need to do manual configuration. Skip to [[#Tools_installation]].}}
<!--T:19-->
Please make sure the following steps are performed before rebooting into OpenVZ kernel.
=== sysctl ===<!--T:20-->
<!--T:21-->
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.
<!--T:22-->
<pre>
# On Hardware Node we generally need
net.ipv4.conf.default.proxy_arp = 0
<!--T:23-->
# Enables source route verification
net.ipv4.conf.all.rp_filter = 1
<!--T:24-->
# Enables the magic-sysrq key
kernel.sysrq = 1
<!--T:25-->
# We do not want all our interfaces to send redirects
net.ipv4.conf.default.send_redirects = 1
</pre>
=== SELinux === SELinux should be disabled. To that effect, put the following line to <code>/etc/sysconfig/selinux</code>:<pre>SELINUX=disabled</pre> === Conntracks === {{Note|In OpenVZ kernels later than 2.6.8, connection tracking is enabled by default so skip this section.}} In the old (2.6.8!--based) OpenVZ kernels 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 on some distributions) 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> fileT:<pre>options ip_conntrack ip_conntrack_enable_ve0=1</pre> == 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_Centos26-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!--T:27--># rpm -Uhv vzctl*SELinux should be disabled.rpm vzquota*.rpmPut <code>SELINUX=disabled</code> to <code>/etc/sysconfig/selinux</precode>:
If rpm complains about unresolved dependencies, you'll have to satisfy them first, then repeat the installation. <!--T:28-->echo "SELINUX=disabled" > /etc/sysconfig/selinux
When all the tools are installed, start the OpenVZ subsystem.== Tools installation == <!--T:29-->
== Starting OpenVZ ==<!--T:30-->{{Out|Before installing tools, please read about [[vzstats]] and opt-out if you don't want to help the project.}}
As root, execute the following command<!--T:31-->OpenVZ needs some user-level tools installed:
<pre!--T:32--># /sbin/service vz start</pre>yum install vzctl vzquota ploop
This will load all the needed == Reboot into OpenVZ kernel modules. This script should also start all the containers marked to be auto== <!-started on machine boot (there aren't any yet).-T:33-->
During <!--T:34-->Now reboot the next reboot, this script machine and choose "OpenVZ" on the boot loader menu (it should be executed automaticallydefault choice).
== Installing Download OS template caches templates ==<!--T:35-->
<!--T:36-->An OS template cache is a Linux distribution installed into a container
and then packed into a gzipped tarball. Using such a cache, a new container
can be created in a matter of minutes. Download precreated template caches 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]]. Put those tarballs '''as-is (no unpacking needed)''' to the <tt>/vz/template/cache/</tt> directory(for Debain, this is <tt>/var/lib/vz/template/cache/</tt>)minute.
<!--T:37-->
Download precreated template caches 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]]. Put those tarballs '''as-is (no unpacking needed)''' to the <tt>/vz/template/cache/</tt> directory.
== Next steps ==<!--T:38-->
<!--T:39-->OpenVZ is now set up on your machine. To load OpenVZ kernel by default, edit the default line Follow on to [[basic operations 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 detailsenvironment]] document.
Follow on to [[basic operations in OpenVZ environment]] document.
[[Category: Installation]]
[[Category: HOWTO]]
Retrieved from "https://wiki.openvz.org/Special:MobileDiff/9717...23051"

Navigation menu