Just wanted to mention that Kir created a new directory at the top level of the download site named beta. Inside of it you'll find a directory structure that you can eventually drill down into to find a number of new, beta OS Templates that Kir has built. Here's a list:
centos-4-x86_64.tar.gz, centos-4-x86.tar.gz, centos-5-x86_64.tar.gz, centos-5-x86.tar.gz, debian-3.1-x86.tar.gz, debian-4.0-x86_64.tar.gz, debian-4.0-x86.tar.gz, fedora-7-x86_64.tar.gz, fedora-7-x86.tar.gz, fedora-8-x86_64.tar.gz, fedora-8-x86.tar.gz, fedora-9-x86_64.tar.gz, fedora-9-x86.tar.gz, suse-10.3-x86_64.tar.gz, suse-10.3-x86.tar.gz, ubuntu-7.10-x86_64.tar.gz, ubuntu-7.10-x86.tar.gz, ubuntu-8.04-x86_64.tar.gz, ubuntu-8.04-x86.tar.gz
Sorry SUSE fans, no openSUSE 11 yet. :(
One big difference is that the Fedora and CentOS OS Templates now include yum which will make a number of people happy. No more fumbling around trying to download a bunch of rpm packages an using rpm to install yum.
The CentOS 5 OS Template
Oddly enough an OpenVZ "official" pre-created OS Template for CentOS 5 did not previously exist although there have been a number of builds posted in the "contrib" section. So far, I've tested out the CentOS 5 x86 and x86_64 OS Templates and they are a bit different from the contrib releases. For one thing, udevd is installed and running and the vzdev package puts files in /etc/udev/devices/ rather than /dev. This is good, because on previous CentOS Templates udev was not installed and if it happened to get installed as a dependency for something else, it would prevent future container starts from working... until udev was removed or the starting of udev was commented out from /etc/rc.d/rc.sysinit. Perhaps including udev will make migrating physical servers to OpenVZ containers a little more easy.
There are a number of updated vz packages installed that include:
vzdummy-kernel-el5, vzdummy-jre-fc6, vzdummy-glibc, vzdummy-apache, vzdev
The CentOS 5 OS Template is quite light-weight resource wise as a container made from initially only takes up about 14MB of RAM. The vzdummy-apache package helps there because it offers a modification to the stock Apache configuration (/etc/httpd/conf.d/swtune.conf) that changes the StartServers value to 1.
Community, please test these out and report any bugs you find!
centos-4-x86_64.tar.gz, centos-4-x86.tar.gz, centos-5-x86_64.tar.gz, centos-5-x86.tar.gz, debian-3.1-x86.tar.gz, debian-4.0-x86_64.tar.gz, debian-4.0-x86.tar.gz, fedora-7-x86_64.tar.gz, fedora-7-x86.tar.gz, fedora-8-x86_64.tar.gz, fedora-8-x86.tar.gz, fedora-9-x86_64.tar.gz, fedora-9-x86.tar.gz, suse-10.3-x86_64.tar.gz, suse-10.3-x86.tar.gz, ubuntu-7.10-x86_64.tar.gz, ubuntu-7.10-x86.tar.gz, ubuntu-8.04-x86_64.tar.gz, ubuntu-8.04-x86.tar.gz
Sorry SUSE fans, no openSUSE 11 yet. :(
One big difference is that the Fedora and CentOS OS Templates now include yum which will make a number of people happy. No more fumbling around trying to download a bunch of rpm packages an using rpm to install yum.
The CentOS 5 OS Template
Oddly enough an OpenVZ "official" pre-created OS Template for CentOS 5 did not previously exist although there have been a number of builds posted in the "contrib" section. So far, I've tested out the CentOS 5 x86 and x86_64 OS Templates and they are a bit different from the contrib releases. For one thing, udevd is installed and running and the vzdev package puts files in /etc/udev/devices/ rather than /dev. This is good, because on previous CentOS Templates udev was not installed and if it happened to get installed as a dependency for something else, it would prevent future container starts from working... until udev was removed or the starting of udev was commented out from /etc/rc.d/rc.sysinit. Perhaps including udev will make migrating physical servers to OpenVZ containers a little more easy.
There are a number of updated vz packages installed that include:
vzdummy-kernel-el5, vzdummy-jre-fc6, vzdummy-glibc, vzdummy-apache, vzdev
The CentOS 5 OS Template is quite light-weight resource wise as a container made from initially only takes up about 14MB of RAM. The vzdummy-apache package helps there because it offers a modification to the stock Apache configuration (/etc/httpd/conf.d/swtune.conf) that changes the StartServers value to 1.
Community, please test these out and report any bugs you find!


Comments
What is wrong?