| |||
k001 [openvz] | I am preparing an updated set of precreated templates; those should be ready tonight or tomorrow, available from the usual place. In addition to a bunch of updated templates, this time we add a few new ones: - Fedora 10 (aka Cambridge) - openSUSE 11.1 - Ubuntu 9.04 (aka The Jaunty Jackalope) OpenSUSE is interesting -- apparently they dropped yum (which was available in 10.3 and 11.0 but not in 11.1) and now they have something called zypper. Also note that openSUSE lacks the code name. Apparently the SUSE guys are already aware of the issue and have a plan to fix it -- the next release (openSUSE 11.2) will be codenamed Fichte, after the German XIIX century philosopher. Subsequent openSUSE releases will also be named after famous philosophers -- Rousseau, Voltaire, Lessing (although I'm not sure which Lessing do they have in mind, probably Theodor). Interesting... maybe they got the naming idea from OpenVZ kernels. ;) Also, during the next update (i.e. in about a month, not now) we are going to remove a few templates that are old and unsupported: - Debian 3.1 "Sarge" (EOL 30 Mar 2008) - Fedora 7 (EOL 13 Jul 2008) - openSUSE 10.3 (EOL 19 Sep 2008) - Fedora 8 (EOL 7 Jan 2009) - Ubuntu 7.10 (EOL 18 Apr 2009) Anybody who's using those distros inside containers should updated to something more (r|d)ecent and supported. You have been warned. PS For people who use our stable kernels (i.e. RHEL5 branch) -- please note that you have to update to the latest kernel (028stab062.3 at the moment) in order to use Fedora 10 in containers. This is due to a few new system calls recently added to the Linux kernel which Fedora 10 userland expect to have in the kernel. Those syscalls were just backported to our RHEL5 branch by the OpenVZ team. | ||
| |||
Good news, especially the Ubuntu Container will make many people happy.
(Reply) (Thread) (Link)
(Anonymous) on May 20th, 2009 - 01:29 pm
can we make the templates more minimal?
can we make the templates more minimal?
I find the ubuntu ones have all sorts of stuff I have to remove straight away if ever I need them. I keep a copy once I have done that so its not too big a deal, but frankly its annoying.
(Anonymous) on May 22nd, 2009 - 08:27 am
suse templates broken
suse templates broken
hi,
can not install the suse 11.1 templates.
seems the upload is broken.
could you please check those?
can not install the suse 11.1 templates.
seems the upload is broken.
could you please check those?
Fixed, thanks for the report. Indeed this was a strange glitch with tar/gzip.
Please try again.
Please try again.
(Anonymous) on May 22nd, 2009 - 01:55 pm
Re: suse templates broken
Re: suse templates broken
Thank you. Both work.
A howto for a actual suse 11.1 would be wonderful.
Could you please update the 10.3 template creation howto?
Thxs
A howto for a actual suse 11.1 would be wonderful.
Could you please update the 10.3 template creation howto?
Thxs
Wow. Thanks for the additional OS Templates. I'm going to rebase my contributed Fedora 10 OS Template off of the new official one. Here are the changes I make to the original:
1) Remove samba* packages. They take up a lot of space and very few people seem to use them
2) Updated /etc/httpd/conf/httpd.conf to have more traditional values for StartServers, etc. I think the OS Templates you provide are trying to use as little memory as possible by reducing Apache to a single server process, but most folks don't want that in practice
3) Added a few additional packages I like: mc, links, nano
4) In the x86_64 OS Template I remove all i386/i686 packages except for one that is not removable (libc). That saves space and I don't think the i386/i686 packages are used for anything unless someone needs to install a package that is i386 only that relies on them. This frees up a bit of space
5) Install the few updates that have come out in the day or two since you released the official OS Template
You can find my contributed OS Template in the usual place.
1) Remove samba* packages. They take up a lot of space and very few people seem to use them
2) Updated /etc/httpd/conf/httpd.conf to have more traditional values for StartServers, etc. I think the OS Templates you provide are trying to use as little memory as possible by reducing Apache to a single server process, but most folks don't want that in practice
3) Added a few additional packages I like: mc, links, nano
4) In the x86_64 OS Template I remove all i386/i686 packages except for one that is not removable (libc). That saves space and I don't think the i386/i686 packages are used for anything unless someone needs to install a package that is i386 only that relies on them. This frees up a bit of space
5) Install the few updates that have come out in the day or two since you released the official OS Template
You can find my contributed OS Template in the usual place.
hej,
can you tell my why there is always a httpd server installed in the templates?
would like some howtos for creating those templates "minimal".
can you tell my why there is always a httpd server installed in the templates?
would like some howtos for creating those templates "minimal".
Feel free to email me (dowdle@montanalinux.org) and I can give you more details because this isn't exactly the place for this type of information but...
In the Fedora 10 i386 OS Template the Apache related packages (httpd and httpd-tools) installed take up about 3MB of disk space. A container made from the OS Template uses about 50MB of RAM. To remember httpd and httpd-tools you can just "yum remove httpd httpd-tools" and in a few seconds they are gone.
In all there are about 230 packages installed using about 469MB of disk space. You can probably trim that down by a hundred packages or so if you try really, really hard but you'll be getting rid of stuff like man-pages. Without knowing how low you want to get I can't really advise. In the past I have created a minimal OS Template but I don't think they get used much.
To create your own OS Template just create a container from the desired OS Template and then remove what software you don't want. Then stop the container... and clean up a few things (like getting rid of the ssh keys that were generated, etc) and then just .tar.gz the private dir up and you have a new OS Template. It is that simple. So, what stuff do you have to clean up? Container specific stuff like:
1) ssh keys in /etc/ssh/
2) /etc/hosts, /etc/resolv.conf, /etc/sysconfig/network, /etc/sysconfig/network-scripts/ifcfg-ven et0:0
3) Files in /var/log
That's about it. Have fun.
In the Fedora 10 i386 OS Template the Apache related packages (httpd and httpd-tools) installed take up about 3MB of disk space. A container made from the OS Template uses about 50MB of RAM. To remember httpd and httpd-tools you can just "yum remove httpd httpd-tools" and in a few seconds they are gone.
In all there are about 230 packages installed using about 469MB of disk space. You can probably trim that down by a hundred packages or so if you try really, really hard but you'll be getting rid of stuff like man-pages. Without knowing how low you want to get I can't really advise. In the past I have created a minimal OS Template but I don't think they get used much.
To create your own OS Template just create a container from the desired OS Template and then remove what software you don't want. Then stop the container... and clean up a few things (like getting rid of the ssh keys that were generated, etc) and then just .tar.gz the private dir up and you have a new OS Template. It is that simple. So, what stuff do you have to clean up? Container specific stuff like:
1) ssh keys in /etc/ssh/
2) /etc/hosts, /etc/resolv.conf, /etc/sysconfig/network, /etc/sysconfig/network-scripts/ifcfg-ven
3) Files in /var/log
That's about it. Have fun.
"just create a container from the desired OS Template"
thats not from scratch, sorry.
i think i will have a howto for this soon ;-)
thats not from scratch, sorry.
i think i will have a howto for this soon ;-)
There are wiki pages on how to create an OS Template from scratch. The vzpkg build system that is part of OpenVZ is broken. vzpkg2 is a third-party OS Template build system that was 95% done but then got abandoned by the developer. Various other recipes exist for various distros... for creating your own from scratch. Use those if you like.
The easiest way is to start with an official OS Template, assuming one exists for the distro you want, and then create a container out of that, modified it as desired, clean it up, and tar.gz it.
Before there was an official OS Template for Fedora 10, I made mine by taking the OS Template for Fedora 9, creating a container from it, upgrading it, cleaning it up, and then tar.gz it. Works for me.
The easiest way is to start with an official OS Template, assuming one exists for the distro you want, and then create a container out of that, modified it as desired, clean it up, and tar.gz it.
Before there was an official OS Template for Fedora 10, I made mine by taking the OS Template for Fedora 9, creating a container from it, upgrading it, cleaning it up, and then tar.gz it. Works for me.
Ok i got it now ;-)
I have a script now for building Centos 5.3 and Fedora 10 templates within minutes without a real installation as suggested in the wiki. The templates are blank with yum now.
The only thing is left is the Fedora 10 network startup, i can activate it when i restart it inside vps. Any suggestion how to fix this? There was a way by modifing /etc/init.d/network but this seems not to match here...
dowdle can you pm me your ICQ or MSN? Maybe i can contribute some things to the wiki...
I have a script now for building Centos 5.3 and Fedora 10 templates within minutes without a real installation as suggested in the wiki. The templates are blank with yum now.
The only thing is left is the Fedora 10 network startup, i can activate it when i restart it inside vps. Any suggestion how to fix this? There was a way by modifing /etc/init.d/network but this seems not to match here...
dowdle can you pm me your ICQ or MSN? Maybe i can contribute some things to the wiki...
(Anonymous) on June 10th, 2009 - 07:41 pm
opensuse 11.1 x86_64 bugs
opensuse 11.1 x86_64 bugs
Hi,
I've tried out the new opensuse 11.1 x86_64 template and there are some problems that haven't been mentioned so far afaik.
- the package yast2-ncurses-pkg is not installed in the template, therefore the whole yast install frontend is missing
- when you want to install something (an rpm using the rpm command or yast which seems to use the rpm command in the backend, too) you always get an error that 'package XY is intended for x86_64 architecture', even if your host system is a 64bit system and the 'arch' command reports x86_64.
----
using 2.6.24-ovz-5.7-default
opensuse
I've tried out the new opensuse 11.1 x86_64 template and there are some problems that haven't been mentioned so far afaik.
- the package yast2-ncurses-pkg is not installed in the template, therefore the whole yast install frontend is missing
- when you want to install something (an rpm using the rpm command or yast which seems to use the rpm command in the backend, too) you always get an error that 'package XY is intended for x86_64 architecture', even if your host system is a 64bit system and the 'arch' command reports x86_64.
----
using 2.6.24-ovz-5.7-default
opensuse
(Anonymous) on July 8th, 2009 - 11:36 am
Re: opensuse 11.1 x86_64 bugs
Re: opensuse 11.1 x86_64 bugs
I've got the same problem, anybody in OpenVZ is looking into this problem?
