Difference between pages "OpenVZ/pt-br" and "Translations:Metro/122/en"

< OpenVZ(Difference between pages)
(Created page with "== Apresentação == OpenVZ (veja [http://wiki.openvz.org wiki.openvz.org]) é uma solução de virtualização de servidor a nível do sistema operacional (OS-level server v...")
 
(Importing a new version from external source)
 
Line 1: Line 1:
== Apresentação ==
+
On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that {{c|buildrepo}} has been configured to manage. The first number on each line is a '''failcount''', which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount:
 
+
OpenVZ (veja [http://wiki.openvz.org wiki.openvz.org]) é uma solução de virtualização de servidor a nível do sistema operacional (OS-level server virtualization solution),  
+
construído no Linux. OpenVZ permite a criação de containers Linux virtuais isolados e seguros (chamados de "VE"s) em um único servidor físico. Cada container possui sua própria atualização local, power state, interfaces de rede, limites de recurso e porção limitada de filesystem hospede. OpenVZ é com frequência descrito como "chroot on steroids."
+
 
+
Funtoo possui suporte ao OpenVZ das seguintes maneiras:
+
 
+
* Building of OpenVZ templates using [[Metro]], our distribution build tool.
+
* Improvement of <tt>vzctl</tt>, by developing an improved/patched version hosted on [http://www.github.com/funtoo/vzctl GitHub].
+
* Integration of [[Funtoo Linux Networking]] support into vzctl (these patches have been accepted upstream by the OpenVZ project.)
+
* Improvement of vzctl startup scripts to do things like properly initialize veth and vzeventd.
+
* Integrating additional patches into openvz-rhel6-stable and openvz-rhel5-stable ebuilds in order to ensure production-quality OpenVZ functionality.
+
* Maintaining compatibility with production RHEL5-based OpenVZ kernels, as well as instructions on how to get Funtoo Linux set up for these kernels in our [[RHEL5 Kernel HOWTO]]. (Note: openvz-rhel6-kernel RHEL6-based kernel is now the recommended kernel for deploying OpenVZ.)
+
 
+
In addition, Daniel is currently employed at [http://www.zenoss.com Zenoss] and is the author and maintainer of the [http://community.zenoss.org/blogs/zenossblog/2012/01/24/openvz-and-zenoss Zenoss OpenVZ ZenPack] ([https://github.com/zenoss/ZenPacks.zenoss.OpenVZ GitHub link])
+
== Recommended Versions ==
+
 
+
For setting up OpenVZ on Funtoo Linux so that you can create Linux-based containers, an <tt>x86-64bit</tt> version of Funtoo Linux is strongly recommended. The <tt>openvz-rhel6-stable</tt> ebuild is the recommended kernel to use. If you emerge this kernel with the <tt>binary</tt> USE flag enabled, it will build a binary kernel and initrd using the default Red Hat configuration which should boot on nearly all hardware. After emerging, you will need to edit <tt>/etc/boot.conf</tt>, run [[boot-update]], and reboot into the new OpenVZ kernel.
+
 
+
{{fancywarning|1=
+
Please use ext4 exclusively when deploying an OpenVZ host. The Parallels development team tests extensively with ext4, and modern versions of <tt>openvz-rhel6-stable</tt> are '''not''' compatible with XFS, and you may experience kernel bugs.
+
}}
+
 
+
Alternatively, you could emerge <tt>openvz-rhel5-stable</tt> with the <tt>binary</tt> USE flag enabled to use the older RHEL5-based OpenVZ kernel. This requires additional steps which are covered in the [[RHEL5 Kernel HOWTO]].
+
 
+
You will also need to emerge <tt>vzctl</tt>, which are the OpenVZ userspace tools.
+

Latest revision as of 17:31, July 12, 2015

On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that buildrepo has been configured to manage. The first number on each line is a failcount, which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount: