Re: OpenVZ (was: systemd effectively mandatory now due to GNOME)
On 10/24/2013 06:46 PM, Ben Hutchings wrote: On Thu, 2013-10-24 at 11:59 +0200, Adam Borowski wrote: On Thu, Oct 24, 2013 at 09:11:30AM +0100, Jonathan Dowland wrote: On Thu, Oct 24, 2013 at 02:09:46AM +0200, Adam Borowski wrote: And I for one heavily use vservers It's a professional shame of mine that we are still trying to get rid of some old vserver instances at $WORK. lxc is still nowhere close to vserver (or openvz) functionality. [...] I'm not sure whether that's still true, but anyway: OpenVZ is in mainline Linux now. Oh, I'm surprised! I thought it would never get in, since we had LXC. Thanks for sharing this info. How much of it is in? All of it? Or just a subset? You'll need to wait for Linux 3.12 in Debian, as we can't enable CONFIG_USER_NS before then What's that for? Thomas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52692bcc.1080...@debian.org
Re: OpenVZ (was: systemd effectively mandatory now due to GNOME)
On Thu, 2013-10-24 at 22:16 +0800, Thomas Goirand wrote: On 10/24/2013 06:46 PM, Ben Hutchings wrote: On Thu, 2013-10-24 at 11:59 +0200, Adam Borowski wrote: On Thu, Oct 24, 2013 at 09:11:30AM +0100, Jonathan Dowland wrote: On Thu, Oct 24, 2013 at 02:09:46AM +0200, Adam Borowski wrote: And I for one heavily use vservers It's a professional shame of mine that we are still trying to get rid of some old vserver instances at $WORK. lxc is still nowhere close to vserver (or openvz) functionality. [...] I'm not sure whether that's still true, but anyway: OpenVZ is in mainline Linux now. Oh, I'm surprised! I thought it would never get in, since we had LXC. The mainline implementation of containers, which is made up of multiple types of control groups and namespaces, supports both LXC and OpenVZ (and Google's resource control, and systemd-nspawn, and yet other tools). Thanks for sharing this info. How much of it is in? All of it? Or just a subset? James Bottomley of Parallels talked about this in Edinburgh and said everything was in by 3.9. You'll need to wait for Linux 3.12 in Debian, as we can't enable CONFIG_USER_NS before then What's that for? User namespaces, i.e. user IDs and capabilities (the privileges that root normally has) in a container are distinguished from those in the outer system. This is essential for virtual private servers. Every filesystem implementation needs to make this distinction and not all of them were converted to do so before 3.12. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Re: OpenVZ
On 10/25/2013 12:30 AM, Ben Hutchings wrote: On Thu, 2013-10-24 at 22:16 +0800, Thomas Goirand wrote: On 10/24/2013 06:46 PM, Ben Hutchings wrote: On Thu, 2013-10-24 at 11:59 +0200, Adam Borowski wrote: On Thu, Oct 24, 2013 at 09:11:30AM +0100, Jonathan Dowland wrote: On Thu, Oct 24, 2013 at 02:09:46AM +0200, Adam Borowski wrote: And I for one heavily use vservers It's a professional shame of mine that we are still trying to get rid of some old vserver instances at $WORK. lxc is still nowhere close to vserver (or openvz) functionality. [...] I'm not sure whether that's still true, but anyway: OpenVZ is in mainline Linux now. Oh, I'm surprised! I thought it would never get in, since we had LXC. The mainline implementation of containers, which is made up of multiple types of control groups and namespaces, supports both LXC and OpenVZ (and Google's resource control, and systemd-nspawn, and yet other tools). Thanks for sharing this info. How much of it is in? All of it? Or just a subset? James Bottomley of Parallels talked about this in Edinburgh and said everything was in by 3.9. You'll need to wait for Linux 3.12 in Debian, as we can't enable CONFIG_USER_NS before then What's that for? User namespaces, i.e. user IDs and capabilities (the privileges that root normally has) in a container are distinguished from those in the outer system. This is essential for virtual private servers. Every filesystem implementation needs to make this distinction and not all of them were converted to do so before 3.12. Ben. I would very much welcome the return of OpenVZ in Debian via backports, when it's ready! Hoping that this may happen before the EOL of Squeeze, to assure continuity of production, for those using it. Thomas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/526a0327.9020...@debian.org
Re: openvz, was: Re: Bug#672695: wordpress: no sane way for security updates in stable releases
On Mon, May 14, 2012 at 04:37:23PM +0200, Toni Mueller wrote: This reminds me: is anyone going to bring back vserver or openvz in some I'm for having openvz back, then. Are you ready to do the required work? Can we have this in a separate thread, please? Do we have any practical results to discuss there? -- WBR, wRAR signature.asc Description: Digital signature
Re: OpenVZ - deb-packages
Hi, On Wed, 14 Oct 2009, Dmitry E. Oboukhov wrote: I need OpenVZ 2.6.27 with ppp-features available. I was on the point of building the package, but I am not very good in building of kernels and the current openvz is built somehow strange: apt-get source linux-image-2.6.26-2-openvz-686 gets an src-package with no mentions of openvz in debian/control in it. Kernel packages are special: http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage 1. Have I understood correctly that openvz doesn't have its own Source in Debian now and it is simply added/removed from linux-source as the need arises? How should I act and with whom should I communicate if I want to add something to the package? The main source is the linux-2.6 source package. You should talk to its maintainers (people reachable on debian-ker...@lists.debian.org). 2. May be somebody has already built openvz 2.6.27 (with ppp-features). Could You share the link on repository? I have built a 2.6.26 openvz kernel with the ppp support (a single supplementary patch): The patch on the source package: https://svn.ac-grenoble.fr/svn/slis/slis/sources/trunk/backports/patches/linux-2.6_2.6.26-15~slis41+1.patch The source package: http://ftp.slis.fr/slis/pool/main/l/linux-2.6/linux-2.6_2.6.26-15~slis41+1.dsc The binary package: http://ftp.slis.fr/slis/pool/main/l/linux-2.6/linux-image-2.6.26-slis.1-openvz-686_2.6.26-15~slis41+1_i386.deb I would like this patch to be added in a point release update given it's only a supplementary feature in the -openvz kernel and should not disturb anything else. But it's not in line with the traditional stable update policy so I did not bother to propose it up to now. Dann, what's your stance on this ? Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: OpenVZ - deb-packages
On Wed, Oct 14, 2009 at 02:00:28PM +0200, Raphael Hertzog wrote: Hi, On Wed, 14 Oct 2009, Dmitry E. Oboukhov wrote: I need OpenVZ 2.6.27 with ppp-features available. I was on the point of building the package, but I am not very good in building of kernels and the current openvz is built somehow strange: apt-get source linux-image-2.6.26-2-openvz-686 gets an src-package with no mentions of openvz in debian/control in it. Kernel packages are special: http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage 1. Have I understood correctly that openvz doesn't have its own Source in Debian now and it is simply added/removed from linux-source as the need arises? How should I act and with whom should I communicate if I want to add something to the package? The main source is the linux-2.6 source package. You should talk to its maintainers (people reachable on debian-ker...@lists.debian.org). 2. May be somebody has already built openvz 2.6.27 (with ppp-features). Could You share the link on repository? I have built a 2.6.26 openvz kernel with the ppp support (a single supplementary patch): The patch on the source package: https://svn.ac-grenoble.fr/svn/slis/slis/sources/trunk/backports/patches/linux-2.6_2.6.26-15~slis41+1.patch The source package: http://ftp.slis.fr/slis/pool/main/l/linux-2.6/linux-2.6_2.6.26-15~slis41+1.dsc The binary package: http://ftp.slis.fr/slis/pool/main/l/linux-2.6/linux-image-2.6.26-slis.1-openvz-686_2.6.26-15~slis41+1_i386.deb I would like this patch to be added in a point release update given it's only a supplementary feature in the -openvz kernel and should not disturb anything else. But it's not in line with the traditional stable update policy so I did not bother to propose it up to now. Dann, what's your stance on this ? I'm taking care of openvz, please file a bug report with severity important including the patch or link to patch, so that it can be added. if it does not break ABI it is easiest to add to next stable release, if it does i'll add it to the queued ABI breaking patches. did you test that? thanks + kind regards -- maks -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: OpenVZ - deb-packages
On Wed, 14 Oct 2009, maximilian attems wrote: I'm taking care of openvz, please file a bug report with severity important including the patch or link to patch, so that it can be added. Will do. if it does not break ABI it is easiest to add to next stable release, if it does i'll add it to the queued ABI breaking patches. did you test that? No, I had to change the abiname anyway as I wanted different package names for the target derivative distribution to avoid unwanted cross-upgrades. How can I test that ? Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
