From henry at myvirtualserver.de Thu Apr 13 07:18:02 2017 From: henry at myvirtualserver.de (Henry Spanka) Date: Thu, 13 Apr 2017 16:18:02 +0200 Subject: [Users] Ubuntu 17.04 support for OpenVZ RHEL 6 Message-ID: Hello OpenVZ Users, Today Ubuntu 17.04 was released. Are there any plans to create an OpenVZ template for it? I?m aware that Ubuntu 17.04 uses systemd just like Ubuntu 16.04 and 16.10. However on Ubuntu 16.04 it was still possible to switch back to UNIX System V manually to allow it to work on RHEL 6. Does anybody know if this still applies to the just released version of Ubuntu? -----------------------------------------------------------------------------------------? If you have any further questions, please let us know.? Mit freundlichen Gr??en / With best regards? Henry Spanka | myVirtualserver Development Team? -------------- next part -------------- An HTML attachment was scrubbed... URL: From informatica at actiu.net Thu Apr 13 07:29:40 2017 From: informatica at actiu.net (Narcis Garcia) Date: Thu, 13 Apr 2017 16:29:40 +0200 Subject: [Users] Ubuntu 17.04 support for OpenVZ RHEL 6 In-Reply-To: Message-ID: Debian 8 uses systemd and I run it without problems in a OpenVZ/6 container. El 13/04/17 a les 16:18, Henry Spanka ha escrit: > Hello OpenVZ Users, > Today Ubuntu 17.04 was released. > Are there any plans to create an OpenVZ template for it? I?m aware that > Ubuntu 17.04 uses systemd just like Ubuntu 16.04 and 16.10. However on > Ubuntu 16.04 it was still possible to switch back to UNIX System V > manually to allow it to work on RHEL 6. Does anybody know if this still > applies to the just released version of Ubuntu? > > ----------------------------------------------------------------------------------------- > If you have any further questions, please let us know. > > Mit freundlichen Gr??en / With best regards > Henry Spanka | myVirtualserver Development Team > > > _______________________________________________ > Users mailing list > Users at openvz.org > https://lists.openvz.org/mailman/listinfo/users > From henry at myvirtualserver.de Thu Apr 13 10:18:47 2017 From: henry at myvirtualserver.de (Henry Spanka) Date: Thu, 13 Apr 2017 19:18:47 +0200 Subject: [Users] Ubuntu 17.04 support for OpenVZ RHEL 6 In-Reply-To: References: Message-ID: Hello, I know but I?m not sure if Ubuntu 17.04 is still compatible with System V. I?ll try to create a template when I have time and give you guys feedback. -----------------------------------------------------------------------------------------? If you have any further questions, please let us know.? Mit freundlichen Gr??en / With best regards? Henry Spanka | myVirtualserver Development Team? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dowdle at montanalinux.org Thu Apr 13 13:50:48 2017 From: dowdle at montanalinux.org (Scott Dowdle) Date: Thu, 13 Apr 2017 14:50:48 -0600 Subject: [Users] Ubuntu 17.04 support for OpenVZ RHEL 6 In-Reply-To: Message-ID: <11346353.20092.1492116648229.JavaMail.root@montanalinux.org> Greetings, ----- Original Message ----- > I know but I?m not sure if Ubuntu 17.04 is still compatible with > System V. > > I?ll try to create a template when I have time and give you guys > feedback. As previously mentioned, systemd-based distros run just fine on OpenVZ Legacy (aka EL6/2.6.32.x-based OpenVZ kernel)... and have for several years now (since 10 release of Fedora ago)... so I'm not sure why you keep mentioning it. If you are wondering if Ubuntu 17.04 can still be switched over to SysVinit, that's a different question, and unrelated to OpenVZ. The easiest way to get a 17.04 OS Template would be to create a 16.10 container and upgrade it, and if successful, make an OS Template from it. If you are unsure how to do that and want to learn, just ask. I think non-LTS releases of Ubuntu are only supported for 9 months... so very few people are interested in non-LTS releases for server stuff. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] From dowdle at montanalinux.org Thu Apr 13 15:27:11 2017 From: dowdle at montanalinux.org (Scott Dowdle) Date: Thu, 13 Apr 2017 16:27:11 -0600 Subject: [Users] Ubuntu 17.04 support for OpenVZ RHEL 6 In-Reply-To: Message-ID: <11084270.20666.1492122431416.JavaMail.root@montanalinux.org> Greetings, ----- Original Message ----- > Today Ubuntu 17.04 was released. > Are there any plans to create an OpenVZ template for it? I?m aware > that Ubuntu 17.04 uses systemd just like Ubuntu 16.04 and 16.10. Decided I'd give it a try. I'm not much of an Ubuntu user so I feel weird explaining all of this, but it did work for me. 1) Create a container from the beta Ubuntu 16.10 OS Template which uses systemd a) cd /vz/template/cache/ ; wget https://download.openvz.org/template/precreated/beta/ubuntu-16.10-x86_64.tar.gz b) There is a gpg signature file and you are encouraged to verify your download but I'll skip explaining that step c) vzctl create {ctid} --name {name} --hostname {hostname} --ipadd {n.n.n.n} --config {config} --ostemplate ubuntu-16.10-x86_64 I tab completed a lot of that in my shell session and manually typed it into this email so hopefully I didn't add a typo but you should already know how to create a container, right? 2) Start the container and enter it as root 3) Upgrade it like so: a) apt-get update && apt-get upgrade b) apt-get install update-manager-core c) do-release-upgrade -d At that point it should prompt you a few times for various upgrade related questions common to Ubuntu upgrades. When it starts installing, deleting, and upgrading packages... it will prompt for service config related issues a few times related to config file changes. I just went with the defaults. Eventually it complains that the kernel is older than should work... but that is fine. When all was done, I rebooted the container (systemctl reboot [again the container not the host]), entered it again, and verified that it was the 17.04 release (cat /etc/os-release) and that everything expected was running (pstree -nup). I verified that networking was still operational by doing another "apt-get update && apt-get upgrade" and it was able to pulled down the metadata and determine it was fully up-to-date. Now one can shut down the container (vzctl stop {ctid}), mount its disk (vzctl mount {ctid}), do a little clean up on the containers filesystem as desired, and then tar.xz|gz it up... naming it with the same OS Template naming pattern you'd expect and placing it in /vz/template/cache/. cd /vz/root/{ctid} ; tar -cvJf /vz/template/cache/ubuntu-17.04-x86_64.tar.xz . ; Then umount and destroy the upgraded container and make a new container with your new OS Template. I didn't try that last part but generally it just works. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work]