Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi, > Am 08.06.2016 um 09:08 schrieb Ashley Moravek > : > > Actually that might be the #1 issue with current Debian Stable - it uses > older libvirt 1.2.9 and VZ team would have to recompile their own and roll it > to all users... otherwise no parallels+VMs tools. when I'm correct they contributed all changes to libvirt upstream. For a project I stopped in the meantime, I already compiled newer libvirt versions on Debian Jessie, it should be possible to do this for using VZ7 too. I'm still seeking for a solution how to install VZ7 in the environment I have, as there is no simple way to do this. Perhaps it would work for me to compile all the needed stuff on a Debian based system. I need to check with a VM how far I can get with compiling and if there is other stuff that might require fixes for Debian. Another option might be to create another install image from a already installed VZ7 that runs in a VM. I'll see what might work. Regards Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Scott, my affected server has a Intel Xeon E3 1245v2 CPU. That's some generations before skylake. Regards, Volker > Am 08.07.2016 um 17:23 schrieb Scott Dowdle : > > Greetings, > > Regarding the won't-boot-after-kernel-upgrade issue... I wonder if it is > related to Skylake processors and a recent microcode_ctl update that Fedora > recently reported affects all of their current releases as well as other > distros? > > For more info see: > > PSA: Failure to boot after kernel update on Skylake systems > https://www.happyassassin.net/2016/07/07/psa-failure-to-boot-after-kernel-update-on-skylake-systems/ > > TYL, > -- > Scott Dowdle > 704 Church Street > Belgrade, MT 59714 > (406)388-0827 [home] > (406)994-3931 [work] > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Greetings, Regarding the won't-boot-after-kernel-upgrade issue... I wonder if it is related to Skylake processors and a recent microcode_ctl update that Fedora recently reported affects all of their current releases as well as other distros? For more info see: PSA: Failure to boot after kernel update on Skylake systems https://www.happyassassin.net/2016/07/07/psa-failure-to-boot-after-kernel-update-on-skylake-systems/ TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 07/08/2016 12:22 AM, Volker Janzen wrote: Hi Denis, as far as I can see, vzdeploy already installed the VZ7 repository. I just do not know which packages are now required. E.g. I had to install prlctl manual. That command is complaining Parallels Server is missing. Seem to be a dependency problem. virtuozzo-release package is installed, too, I assumed this package should have dependencies to everything I need. I'm afraid it doesn't. Currently we don't have an officially approved command(s) to turn VzLinux or CentOS into VZ, but you can try to install "vz" package group: # yum groupinstall vz It should bring everything necessary to build containers. In addition, you can install "ps" group to get packages necessary to run VMs. -- Regards, Denis Silakov Senior Software Architect Virtuozzo ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Denis, as far as I can see, vzdeploy already installed the VZ7 repository. I just do not know which packages are now required. E.g. I had to install prlctl manual. That command is complaining Parallels Server is missing. Seem to be a dependency problem. virtuozzo-release package is installed, too, I assumed this package should have dependencies to everything I need. Regards, Volker > Am 07.07.2016 um 16:28 schrieb Denis Silakov : > > ... Note that vzdeploy by itself in its current state only adds vzlinux repo > to your system. You can then run "yum update" to really install VzLinux > packages instead of CentOS ones. Then you should add Virtuozzo repositories > and install Vz7 packages. > >> On 07/07/2016 03:47 PM, Volker Janzen wrote: >> Hi Denis, >> >> I managed to use the script on one server, but i had the problem after >> reboot, that I have no clue how to continue. There seem to be essential >> packages missing to run VZ7. >> >> >> Regards >> Volker >> >> >>> Am 07.06.2016 um 09:42 schrieb Denis Silakov : >>> >>> >>> On 06/06/2016 09:59 PM, Volker Janzen wrote: > As you know Virtuozzo 7 based on VzLinux distribution. I forgot another question: is there a hardware requirement / compatibility list for VzLinux? As of it's not the same as CentOS, the requirements may be different. Is there software raid support in bare metall installer? Or is hardware raid a requirement? >>> Requirements are the same as for CentOS/RHEL. Installer functionality is >>> also the same as in CentOS. >>> >>> And actually one can run a script named vzdeploy >>> (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or >>> Scientific Linux installation into VzLinux one. This script is not >>> thoroughly tested yet, so use with care. >>> >>> -- >>> Regards, >>> Denis Silakov >>> Senior Software Architect >>> Virtuozzo > > -- > Regards, > Denis Silakov > Senior Software Architect > Virtuozzo > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Denis, one server did not boot at all. Technican told there was a call trace from kernel, but they will not give more details. Need to get one VZ7 running, perhaps I can find the error on this server. One server did boot. Will reply for this in other email. Regards Volker > Am 07.07.2016 um 14:50 schrieb Denis Silakov : > > What kind of problem? Did you manage to boot at all? > >> On 07/07/2016 03:47 PM, Volker Janzen wrote: >> Hi Denis, >> >> I managed to use the script on one server, but i had the problem after >> reboot, that I have no clue how to continue. There seem to be essential >> packages missing to run VZ7. >> >> >> Regards >> Volker >> >> >>> Am 07.06.2016 um 09:42 schrieb Denis Silakov : >>> >>> >>> On 06/06/2016 09:59 PM, Volker Janzen wrote: > As you know Virtuozzo 7 based on VzLinux distribution. I forgot another question: is there a hardware requirement / compatibility list for VzLinux? As of it's not the same as CentOS, the requirements may be different. Is there software raid support in bare metall installer? Or is hardware raid a requirement? >>> Requirements are the same as for CentOS/RHEL. Installer functionality is >>> also the same as in CentOS. >>> >>> And actually one can run a script named vzdeploy >>> (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or >>> Scientific Linux installation into VzLinux one. This script is not >>> thoroughly tested yet, so use with care. >>> >>> -- >>> Regards, >>> Denis Silakov >>> Senior Software Architect >>> Virtuozzo > > -- > Regards, > Denis Silakov > Senior Software Architect > Virtuozzo > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
... Note that vzdeploy by itself in its current state only adds vzlinux repo to your system. You can then run "yum update" to really install VzLinux packages instead of CentOS ones. Then you should add Virtuozzo repositories and install Vz7 packages. On 07/07/2016 03:47 PM, Volker Janzen wrote: Hi Denis, I managed to use the script on one server, but i had the problem after reboot, that I have no clue how to continue. There seem to be essential packages missing to run VZ7. Regards Volker Am 07.06.2016 um 09:42 schrieb Denis Silakov : On 06/06/2016 09:59 PM, Volker Janzen wrote: As you know Virtuozzo 7 based on VzLinux distribution. I forgot another question: is there a hardware requirement / compatibility list for VzLinux? As of it's not the same as CentOS, the requirements may be different. Is there software raid support in bare metall installer? Or is hardware raid a requirement? Requirements are the same as for CentOS/RHEL. Installer functionality is also the same as in CentOS. And actually one can run a script named vzdeploy (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or Scientific Linux installation into VzLinux one. This script is not thoroughly tested yet, so use with care. -- Regards, Denis Silakov Senior Software Architect Virtuozzo -- Regards, Denis Silakov Senior Software Architect Virtuozzo ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Denis, I managed to use the script on one server, but i had the problem after reboot, that I have no clue how to continue. There seem to be essential packages missing to run VZ7. Regards Volker > Am 07.06.2016 um 09:42 schrieb Denis Silakov : > > > On 06/06/2016 09:59 PM, Volker Janzen wrote: >>> As you know Virtuozzo 7 based on VzLinux distribution. >> I forgot another question: is there a hardware requirement / compatibility >> list for VzLinux? As of it's not the same as CentOS, the requirements may be >> different. Is there software raid support in bare metall installer? Or is >> hardware raid a requirement? > > Requirements are the same as for CentOS/RHEL. Installer functionality is also > the same as in CentOS. > > And actually one can run a script named vzdeploy > (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or > Scientific Linux installation into VzLinux one. This script is not thoroughly > tested yet, so use with care. > > -- > Regards, > Denis Silakov > Senior Software Architect > Virtuozzo > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
What kind of problem? Did you manage to boot at all? On 07/07/2016 03:47 PM, Volker Janzen wrote: Hi Denis, I managed to use the script on one server, but i had the problem after reboot, that I have no clue how to continue. There seem to be essential packages missing to run VZ7. Regards Volker Am 07.06.2016 um 09:42 schrieb Denis Silakov : On 06/06/2016 09:59 PM, Volker Janzen wrote: As you know Virtuozzo 7 based on VzLinux distribution. I forgot another question: is there a hardware requirement / compatibility list for VzLinux? As of it's not the same as CentOS, the requirements may be different. Is there software raid support in bare metall installer? Or is hardware raid a requirement? Requirements are the same as for CentOS/RHEL. Installer functionality is also the same as in CentOS. And actually one can run a script named vzdeploy (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or Scientific Linux installation into VzLinux one. This script is not thoroughly tested yet, so use with care. -- Regards, Denis Silakov Senior Software Architect Virtuozzo -- Regards, Denis Silakov Senior Software Architect Virtuozzo ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Denis, > Requirements are the same as for CentOS/RHEL. Installer functionality is also > the same as in CentOS. > > And actually one can run a script named vzdeploy > (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or > Scientific Linux installation into VzLinux one. This script is not thoroughly > tested yet, so use with care. my first attempts with the script were sobering. I used a fresh CentOS 7.2 install. The script succeeded, but after reboot, the kernel shows a calltrace on boot. Rebooting with default kernel did not work. Something got broken. It will be annoying or perhaps impossible to find this kind of error. I have only servers with no direct access, it will now be even harder to test VZ7. I'm not sure if it will be usable under these circumstances for me in production. Regards, Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
I had an even simpler question: Let's say we have 2 OVZ 7 beta servers; will it be possible to live migrate all CTs away from one beta node to another, install OVZ 7 release on the first node, then live-migrate the CTs back to that node? Jake On Wed, Jun 8, 2016 at 11:23 AM, Sergey Bronnikov wrote: > Anna, > please answer on question regarding upgrade from pre-release Vz7 versions. > > On 09:43 Mon 06 Jun , jjs - mainphrame wrote: >> Hi Sergey, >> >> I suppose one could still migrate CTs from an OVZ7 pre-release to a >> newly installed OVZ7, is that a reasonable assumption? Is live >> migration likely to work in this scenario? >> >> Jake >> >> On Sun, Jun 5, 2016 at 3:55 AM, Sergey Bronnikov wrote: >> > Hello, Volker >> > >> > On 22:06 Fri 03 Jun , Volker Janzen wrote: >> >> Hi, >> >> >> >> > We are going to release Virtuozzo 7 and OpenVZ 7 not later than this >> >> > July. >> >> > Thank you for your interest and stay tuned! >> >> >> >> when I setup VZ 7 beta now, is it possible to upgrade this to the stable >> >> release when it's released? >> > >> > Unfortunately no. We don't support upgrade from pre-release version to the >> > final >> > one. >> > >> >> It also seems to lack some documentation for my use cases, but I need to >> >> start >> >> with VZ7 sooner or later. >> > >> > What usecases are you talking about? >> > >> >> Regards, >> >>Volker >> >> >> >> >> >> > -- >> >> > Best regards, >> >> > Vladimir Porokhov >> >> > >> >> > >> >> > >> >> > >> >> >> On 03.06.16, 18:04, "Scott Dowdle" > >> >> of dow...@montanalinux.org> wrote: >> >> >> >> >> >> Greetings, >> >> >> >> >> >> - Original Message - >> >> >>> we need to prepare a new setup composed of a few nodes (probably 5) >> >> >>> for August this year. >> >> >>> >> >> >>> If I interpreted the wii page correctly, the next VZ7 release will be >> >> >>> a stable one. As you can imagine, we're very tempted to wait for it >> >> >>> instead of deploying on OpenVZ and then migrating everything some >> >> >>> months later. >> >> >>> >> >> >>> The only problem is... we have no idea at all about the actual >> >> >>> planned release date. >> >> >>> >> >> >>> Can anyone shed some light on this? Even knowing the quarter (say, >> >> >>> Q3 vs Q4) would be of great help to us. >> >> >>> >> >> >>> (Disclaimer: I realise there are many factors involved, that >> >> >>> stability comes at a price of a long(er) development time and I'm >> >> >>> not asking for any commitment to an actual date. Just a few hints >> >> >>> on 'how close we are' would be more than enough :-) >> >> >> >> >> >> I don't know the answer... as a user and not a dev... but I would say >> >> >> deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get >> >> >> to know it (or do that with the pre-releases)... and when you feel >> >> >> comfortable with it, migrate the containers from OL to V7... and then >> >> >> you can wipe your OL hosts and turn them into V7 hosts. You'd only >> >> >> really need one spare and then just cycle through them one by one... >> >> >> but I realize I've always operated at a very low scale and there are >> >> >> some really big scale operators out there. >> >> >> >> >> >> In any event... who is ready to totally convert even on day one of a >> >> >> GA? Who even advises doing so even if it is convenient? I'm fairly >> >> >> confident that the transition from OL to V7 with container migration >> >> >> should be fairly smooth... even without live migration it shouldn't be >> >> >> too much trouble if planned for. >> >> >> >> >> >> TYL, >> >> >> -- >> >> >> Scott Dowdle >> >> >> 704 Church Street >> >> >> Belgrade, MT 59714 >> >> >> (406)388-0827 [home] >> >> >> (406)994-3931 [work] >> >> >> ___ >> >> >> Users mailing list >> >> >> Users@openvz.org >> >> >> https://lists.openvz.org/mailman/listinfo/users >> >> > >> >> > ___ >> >> > Users mailing list >> >> > Users@openvz.org >> >> > https://lists.openvz.org/mailman/listinfo/users >> >> > >> >> >> >> >> >> ___ >> >> Users mailing list >> >> Users@openvz.org >> >> https://lists.openvz.org/mailman/listinfo/users >> > >> > -- >> > sergeyb@ >> > ___ >> > Users mailing list >> > Users@openvz.org >> > https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Anna, please answer on question regarding upgrade from pre-release Vz7 versions. On 09:43 Mon 06 Jun , jjs - mainphrame wrote: > Hi Sergey, > > I suppose one could still migrate CTs from an OVZ7 pre-release to a > newly installed OVZ7, is that a reasonable assumption? Is live > migration likely to work in this scenario? > > Jake > > On Sun, Jun 5, 2016 at 3:55 AM, Sergey Bronnikov wrote: > > Hello, Volker > > > > On 22:06 Fri 03 Jun , Volker Janzen wrote: > >> Hi, > >> > >> > We are going to release Virtuozzo 7 and OpenVZ 7 not later than this > >> > July. > >> > Thank you for your interest and stay tuned! > >> > >> when I setup VZ 7 beta now, is it possible to upgrade this to the stable > >> release when it's released? > > > > Unfortunately no. We don't support upgrade from pre-release version to the > > final > > one. > > > >> It also seems to lack some documentation for my use cases, but I need to > >> start > >> with VZ7 sooner or later. > > > > What usecases are you talking about? > > > >> Regards, > >>Volker > >> > >> > >> > -- > >> > Best regards, > >> > Vladimir Porokhov > >> > > >> > > >> > > >> > > >> >> On 03.06.16, 18:04, "Scott Dowdle" >> >> of dow...@montanalinux.org> wrote: > >> >> > >> >> Greetings, > >> >> > >> >> - Original Message - > >> >>> we need to prepare a new setup composed of a few nodes (probably 5) > >> >>> for August this year. > >> >>> > >> >>> If I interpreted the wii page correctly, the next VZ7 release will be > >> >>> a stable one. As you can imagine, we're very tempted to wait for it > >> >>> instead of deploying on OpenVZ and then migrating everything some > >> >>> months later. > >> >>> > >> >>> The only problem is... we have no idea at all about the actual > >> >>> planned release date. > >> >>> > >> >>> Can anyone shed some light on this? Even knowing the quarter (say, > >> >>> Q3 vs Q4) would be of great help to us. > >> >>> > >> >>> (Disclaimer: I realise there are many factors involved, that > >> >>> stability comes at a price of a long(er) development time and I'm > >> >>> not asking for any commitment to an actual date. Just a few hints > >> >>> on 'how close we are' would be more than enough :-) > >> >> > >> >> I don't know the answer... as a user and not a dev... but I would say > >> >> deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get > >> >> to know it (or do that with the pre-releases)... and when you feel > >> >> comfortable with it, migrate the containers from OL to V7... and then > >> >> you can wipe your OL hosts and turn them into V7 hosts. You'd only > >> >> really need one spare and then just cycle through them one by one... > >> >> but I realize I've always operated at a very low scale and there are > >> >> some really big scale operators out there. > >> >> > >> >> In any event... who is ready to totally convert even on day one of a > >> >> GA? Who even advises doing so even if it is convenient? I'm fairly > >> >> confident that the transition from OL to V7 with container migration > >> >> should be fairly smooth... even without live migration it shouldn't be > >> >> too much trouble if planned for. > >> >> > >> >> TYL, > >> >> -- > >> >> Scott Dowdle > >> >> 704 Church Street > >> >> Belgrade, MT 59714 > >> >> (406)388-0827 [home] > >> >> (406)994-3931 [work] > >> >> ___ > >> >> Users mailing list > >> >> Users@openvz.org > >> >> https://lists.openvz.org/mailman/listinfo/users > >> > > >> > ___ > >> > Users mailing list > >> > Users@openvz.org > >> > https://lists.openvz.org/mailman/listinfo/users > >> > > >> > >> > >> ___ > >> Users mailing list > >> Users@openvz.org > >> https://lists.openvz.org/mailman/listinfo/users > > > > -- > > sergeyb@ > > ___ > > Users mailing list > > Users@openvz.org > > https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Yes, I've submitted quite a few PRs related to porting to Debian, they all got accepted (mostly related to bash not being the default /bin/sh in Debian), just as some Makefile changes due to different Debian paths (like systemd). We've got running VZ7 on stock Debian Jessie (systemd, etc) but without Parallels tools (as those need custom libvirt patches to version which is not in Debian Stable). Normal containers with libvzctl+vzctl are working perfectly fine, we've got a few servers in prod on VZ7 for internal use. Actually that might be the #1 issue with current Debian Stable - it uses older libvirt 1.2.9 and VZ team would have to recompile their own and roll it to all users... otherwise no parallels+VMs tools. Best Regards, Ashley On 06/07/2016 09:47 PM, Pavel Gashev wrote: Those could be the same way. One can maintain its own distro for bare metal, but support other distros. It's an Open Source. I believe OpenVZ will accept patches related to other distros. Why not? On 07/06/16 11:07, "users-boun...@openvz.org on behalf of Narcis Garcia" wrote: I see two ways: A) Support main GNU/Linux distros (much time of development) B) Maintain own GNU/Linux ~ VzLinux (much time of development) = supporting a maintained zoo or maintaining own animal at home Ubuntu can have an analogous relation with Debian as VzLinux with RHEL. They have much time of development too. El 07/06/16 a les 02:44, Raghavendra Bhat ha escrit: spameden posts Please understand me correctly, we don't want to support a variety of all Linux zoo. It requires much more time of development, testing and support. That's a shame. Another nail in the coffin of OpenVZ.. :( Sergey as spameden aptly posts, unsupported GNU/Linux should not happen as Virtuozzo runs on top of many, many different distributions. At least Parallels OpenVZ Project does. Try to be as portable as you can, VZ7 should not get isolated and unused due to your rigid stance. It might be a nightmare to support various distros but it enhances the reach of VZ (Virtuozzo). You have to seriously consider support. Your product will get rugged in the process of testing, development and support. ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users -- Ashley Moravek System administrator Seznam.cz, a.s. Radlická 3294/10 150 00 Praha 5 ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Those could be the same way. One can maintain its own distro for bare metal, but support other distros. It's an Open Source. I believe OpenVZ will accept patches related to other distros. Why not? On 07/06/16 11:07, "users-boun...@openvz.org on behalf of Narcis Garcia" wrote: >I see two ways: >A) Support main GNU/Linux distros (much time of development) >B) Maintain own GNU/Linux ~ VzLinux (much time of development) > >= supporting a maintained zoo or maintaining own animal at home > >Ubuntu can have an analogous relation with Debian as VzLinux with RHEL. >They have much time of development too. > > >El 07/06/16 a les 02:44, Raghavendra Bhat ha escrit: >> spameden posts >> Please understand me correctly, we don't want to support a variety of all Linux zoo. It requires much more time of development, testing and support. >>> >>> That's a shame. Another nail in the coffin of OpenVZ.. :( >>> >> >> Sergey as spameden aptly posts, unsupported GNU/Linux should not >> happen as Virtuozzo runs on top of many, many different distributions. >> At least Parallels OpenVZ Project does. Try to be as portable as you >> can, VZ7 should not get isolated and unused due to your rigid stance. >> It might be a nightmare to support various distros but it enhances the >> reach of VZ (Virtuozzo). >> >> You have to seriously consider support. Your product will get rugged >> in the process of testing, development and support. >> >___ >Users mailing list >Users@openvz.org >https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Thanks for that info - vzdeploy changes the picture considerably, removing a lot of objections to the requirements. Jake On Tue, Jun 7, 2016 at 1:53 AM, Sergey Bronnikov wrote: > On 20:41 Mon 06 Jun , Volker Janzen wrote: >> So this sentence from the quick Installation guide is just false: >> "Alternatively, one can install OpenVZ on a pre-installed RPM based Linux >> distribution. Supported Linux distributions: Cloud Linux 7.*, CentOS 7.*, >> Scientific Linux 7.* etc" >> Source: https://openvz.org/Quick_installation_of_Virtuozzo_7 > > Page has been updated. > >> You're telling now it's not an alternative. It should be removed from the >> guide, it's a huge change in the plans on how to deploy VZ7. For now, I was >> able >> to fire up a CentOS 6 host and then follow the guide for installing OpenVZ. >> With >> VZ7, I will need to be able to install from my own ISO image, this might >> cause >> problems with the hosters I use and I really need to evaluate if this is a >> good >> way to go. I really prefer OpenVZ container in favour of lxc and I'd like to >> stay with it, but I also need an easy way to fire up a new host system. >> >> > Please understand me correctly, we don't want to support a variety of all >> > Linux zoo. >> > It requires much more time of development, testing and support. >> >> It is okay to do that. You're not alone with that. But the install guide >> should not state an alternative in the setup guide, that is no alternative. I >> will now need to re-evaluate VZ7 usage completly. >> >> Regards, >> Volker > > -- > sergeyb@ > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Denis, > And actually one can run a script named vzdeploy > (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or > Scientific Linux installation into VzLinux one. This script is not thoroughly > tested yet, so use with care. this is a good way to start for me, because I'll always start from a fresh CentOS install. I'll test it, is there anything to take care of and / or verify if it has succeeded? Regards Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 20:59 Mon 06 Jun , Volker Janzen wrote: > Hi Sergey, > > > As you know Virtuozzo 7 based on VzLinux distribution. > > I forgot another question: is there a hardware requirement / compatibility > list for VzLinux? As of it's not the same as CentOS, the requirements may be > different. Is there software raid support in bare metall installer? Or is > hardware raid a requirement? As far as I know Hardware Compatibility List is the same as for RHEL. Because VzLinux and Virtuozzo kernel based on RHEL kernel. > Regards > Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 06/07/2016 11:35 AM, Volker Janzen wrote: Hi Denis, And actually one can run a script named vzdeploy (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or Scientific Linux installation into VzLinux one. This script is not thoroughly tested yet, so use with care. this is a good way to start for me, because I'll always start from a fresh CentOS install. I'll test it, is there anything to take care of and / or verify if it has succeeded? The main thing to check is that there are no errors from yum during upgrade. This can happen in case you install custom packages (we shouldn't break there dependencies, but who knows - maybe some package has requirement on a package with "el7" in its suffix?) or if a divergence appears between CentOS and VzLinux (though normally this shouldn't happen). After update you should see /etc/vzlinux-release file and all base packages should be replaced with the ones from VzLinux (this can be easily checked by distsuffix - VzLinux packages ends with "vl7"). -- Regards, Denis Silakov Senior Software Architect Virtuozzo ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
I see two ways: A) Support main GNU/Linux distros (much time of development) B) Maintain own GNU/Linux ~ VzLinux (much time of development) = supporting a maintained zoo or maintaining own animal at home Ubuntu can have an analogous relation with Debian as VzLinux with RHEL. They have much time of development too. El 07/06/16 a les 02:44, Raghavendra Bhat ha escrit: > spameden posts > >>> Please understand me correctly, we don't want to support a variety of all >>> Linux zoo. >>> It requires much more time of development, testing and support. >> >> That's a shame. Another nail in the coffin of OpenVZ.. :( >> > > Sergey as spameden aptly posts, unsupported GNU/Linux should not > happen as Virtuozzo runs on top of many, many different distributions. > At least Parallels OpenVZ Project does. Try to be as portable as you > can, VZ7 should not get isolated and unused due to your rigid stance. > It might be a nightmare to support various distros but it enhances the > reach of VZ (Virtuozzo). > > You have to seriously consider support. Your product will get rugged > in the process of testing, development and support. > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 20:41 Mon 06 Jun , Volker Janzen wrote: > So this sentence from the quick Installation guide is just false: > "Alternatively, one can install OpenVZ on a pre-installed RPM based Linux > distribution. Supported Linux distributions: Cloud Linux 7.*, CentOS 7.*, > Scientific Linux 7.* etc" > Source: https://openvz.org/Quick_installation_of_Virtuozzo_7 Page has been updated. > You're telling now it's not an alternative. It should be removed from the > guide, it's a huge change in the plans on how to deploy VZ7. For now, I was > able > to fire up a CentOS 6 host and then follow the guide for installing OpenVZ. > With > VZ7, I will need to be able to install from my own ISO image, this might cause > problems with the hosters I use and I really need to evaluate if this is a > good > way to go. I really prefer OpenVZ container in favour of lxc and I'd like to > stay with it, but I also need an easy way to fire up a new host system. > > > Please understand me correctly, we don't want to support a variety of all > > Linux zoo. > > It requires much more time of development, testing and support. > > It is okay to do that. You're not alone with that. But the install guide > should not state an alternative in the setup guide, that is no alternative. I > will now need to re-evaluate VZ7 usage completly. > > Regards, > Volker -- sergeyb@ ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi, there are arguments for using a single / own distribution or supporting many different onces. It's up to the project what they want to support. When they use there own distro, it's up to them how to handle major changes e.g. switching init system, introducing new major releases of required tools. Seeing there is a script to get started from CentOS will ease usage. It should be easy to fire up a new host with CentOS then run the script to have vzlinux installed. Concern may rise, if there are issues with the custom distribution. From what has been written on the mailing list, the changes are related to VZ7 itself. It will be interesting to see if stuff like EPEL will still work, to allow installation of nagios and it's plugins. And of course how fast security related errors are fixed. We have to wait to see how this works. Will there be an commercial and open source user repository or will there be only one? We'll see. Regards, Volker > Am 07.06.2016 um 10:07 schrieb Narcis Garcia : > > I see two ways: > A) Support main GNU/Linux distros (much time of development) > B) Maintain own GNU/Linux ~ VzLinux (much time of development) > > = supporting a maintained zoo or maintaining own animal at home > > Ubuntu can have an analogous relation with Debian as VzLinux with RHEL. > They have much time of development too. > > > El 07/06/16 a les 02:44, Raghavendra Bhat ha escrit: >> spameden posts >> Please understand me correctly, we don't want to support a variety of all Linux zoo. It requires much more time of development, testing and support. >>> >>> That's a shame. Another nail in the coffin of OpenVZ.. :( >> >> Sergey as spameden aptly posts, unsupported GNU/Linux should not >> happen as Virtuozzo runs on top of many, many different distributions. >> At least Parallels OpenVZ Project does. Try to be as portable as you >> can, VZ7 should not get isolated and unused due to your rigid stance. >> It might be a nightmare to support various distros but it enhances the >> reach of VZ (Virtuozzo). >> >> You have to seriously consider support. Your product will get rugged >> in the process of testing, development and support. > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 06/06/2016 09:59 PM, Volker Janzen wrote: As you know Virtuozzo 7 based on VzLinux distribution. I forgot another question: is there a hardware requirement / compatibility list for VzLinux? As of it's not the same as CentOS, the requirements may be different. Is there software raid support in bare metall installer? Or is hardware raid a requirement? Requirements are the same as for CentOS/RHEL. Installer functionality is also the same as in CentOS. And actually one can run a script named vzdeploy (http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy) to turn his CentOS or Scientific Linux installation into VzLinux one. This script is not thoroughly tested yet, so use with care. -- Regards, Denis Silakov Senior Software Architect Virtuozzo ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Le 06/06/2016 20:41, Volker Janzen a écrit : Hi Sergey, I forgot to mention one important thing in my previous answer. As you know Virtuozzo 7 based on VzLinux distribution. VzLinux is a Linux distribution similar to CentOS but it is not the same. VzLinux is not just rebuilded RPM packages from CentOS. Some RPM packages in VzLinux contains fixes or changes specific to Virtuozzo which are absent in RHEL/CentOS. So this sentence from the quick Installation guide is just false: "Alternatively, one can install OpenVZ on a pre-installed RPM based Linux distribution. Supported Linux distributions: Cloud Linux 7.*, CentOS 7.*, Scientific Linux 7.* etc" Source: https://openvz.org/Quick_installation_of_Virtuozzo_7 You're telling now it's not an alternative. It should be removed from the guide, it's a huge change in the plans on how to deploy VZ7. For now, I was able to fire up a CentOS 6 host and then follow the guide for installing OpenVZ. With VZ7, I will need to be able to install from my own ISO image, this might cause problems with the hosters I use and I really need to evaluate if this is a good way to go. I really prefer OpenVZ container in favour of lxc and I'd like to stay with it, but I also need an easy way to fire up a new host system. +1 we really need to fire up HN from automatic deployement tools, here we use cobbler + PXE to instanciate our servers. We do have centos7 template ready to go , we just add few shell lines in a snippet of our kickstart to transform those bare centos 7 system to VZ . we don't want to maitained a new distribution in cobbler/kickstart ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
spameden posts >> Please understand me correctly, we don't want to support a variety of all >> Linux zoo. >> It requires much more time of development, testing and support. > > That's a shame. Another nail in the coffin of OpenVZ.. :( > Sergey as spameden aptly posts, unsupported GNU/Linux should not happen as Virtuozzo runs on top of many, many different distributions. At least Parallels OpenVZ Project does. Try to be as portable as you can, VZ7 should not get isolated and unused due to your rigid stance. It might be a nightmare to support various distros but it enhances the reach of VZ (Virtuozzo). You have to seriously consider support. Your product will get rugged in the process of testing, development and support. -- Regards Raghavendra Bhat gpg --keyserver pgp.mit.edu --recv-keys 80D98731 gpg --fingerprint 80D98731 ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 06/06/2016 07:13 PM, Сергей Мамонов wrote: > Yes, i know it's still possible to create an image which will be compacted not that efficiently, but this becomes quite a rare case. But in irl - get random prodaction node and first container with max delta (data vs image size) - ploop-balloon discard /vz/private/93713/root.hdd/DiskDescriptor.xml --stat Balloon size:0MB Data size: 30845MB Ploop size: 51200MB Image size: 47546MB ploop-balloon discard /vz/private/93713/root.hdd/DiskDescriptor.xml --defrag ... ploop-balloon discard /vz/private/93713/root.hdd/DiskDescriptor.xml --stat Balloon size:0MB Data size: 30845MB Ploop size: 51200MB Image size: 47433MB Sergey, good! You are welcome to upload the image data: We've already done one more step further, interesting to know if it will be big or small one in your case. Anyone else? And already have 17Gb wasted space for 30Gb data after compact with defrag. ( on node openvz 6 - 2.6.32-042stab114.5 kernel, ploop-1.15-1.x86_64 and e4defrag2 builded from https://github.com/dmonakhov/e2fsprogs/tree/e4defrag2 with commits from 16 May). In irl we have significan overhead on disk operations on compact ploop images. In irl we regular have ploop images which we cannot umount - https://bugs.openvz.org/browse/OVZ-6689 !!! And from time to time backup and compact failed with strange situations like - https://bugs.openvz.org/browse/OVZ-6547 And this is a good illustration why Virtuozzo 7 is so different from OpenVZ 6. Getting free and commercial tools code more and more different lead to issues we don't face in commercial product. i believe OpenVZ users will really benefit in stability from Virtuozzo 7, where the code is exactly same both in commercial and free versions. -- Konstantin 2016-06-06 18:13 GMT+03:00 Konstantin Khorenko mailto:khore...@virtuozzo.com>>: On 06/06/2016 02:23 PM, Volker Janzen wrote: Hi Sergey, On 14:39 Sun 05 Jun , Volker Janzen wrote: Unfortunately no. We don't support upgrade from pre-release version to the final one. When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? There is only one supported configuration for new installations - clean Virtuozzo 7 installation. okay I see. My setup will be unsupported if installed on plain CentOS 7 either way. It also seems to lack some documentation for my use cases, but I need to start with VZ7 sooner or later. What usecases are you talking about? My current OpenVZ setup has LVM involved. I want to be able to use simfs based storage on an underlaying LVM volume. Why do you prefer simfs instead of ploop? Did you see comparison simfs vs ploop? https://openvz.org/CT_storage_backends I think you asked me about this some time ago. The matrix states: Reliability Low: big amount of files produce ext4 corruption so often Why should I use something that tells me it's not reliable? Even according to https://github.com/pavel-odintsov/OpenVZ_ZFS/blob/master/openvz_storage_backends.md (which seems to be used as a source of recent page update) this row is incorrect, this info has just been added by Narcis Garcia and is to be corrected. i don't want to start a holly war here, i won't tell that ZFS is worse or whatever, i just know that we really do power crash testing and know the results. And i'm certain that our default suggested solution is good and stable. Yes, there are drawbacks - the most important one now is usage overhead (sic!, not stability for a long time already), and we improve it. And gained quite a good progress. Just did a ploop compaction of my personal work Container, created 03.07.2014 (lot of gits, makes, etc.): # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml --defrag ... # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml --stat Balloon size:0MB Data size: 29189MB Ploop size: 102400MB Image size: 29057MB Yes, i know it's still possible to create an image which will be compacted not that efficiently, but this becomes quite a rare case. Do you have such an image? Send it to us. Thank you. P.S. in fact we don't need full image in most cases, only metadata is essential, so if you worry about data and confidentiality, no problem here: # e2image -r /dev/ploopXXp1 - | bzip2 > image.e2i.bz2 -- Best regards, Konstantin Khorenko, Virtuozzo Linux Kernel Team The /vz partition has also the big advantage of using LVM snapshots and it allows rsync of the container data to another host with less overhead. Also the need to compress the plo
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
> Please understand me correctly, we don't want to support a variety of all Linux zoo. > It requires much more time of development, testing and support. That's a shame. Another nail in the coffin of OpenVZ.. :( 2016-06-06 19:43 GMT+03:00 jjs - mainphrame : > Hi Sergey, > > I suppose one could still migrate CTs from an OVZ7 pre-release to a > newly installed OVZ7, is that a reasonable assumption? Is live > migration likely to work in this scenario? > > Jake > > On Sun, Jun 5, 2016 at 3:55 AM, Sergey Bronnikov > wrote: > > Hello, Volker > > > > On 22:06 Fri 03 Jun , Volker Janzen wrote: > >> Hi, > >> > >> > We are going to release Virtuozzo 7 and OpenVZ 7 not later than this > July. > >> > Thank you for your interest and stay tuned! > >> > >> when I setup VZ 7 beta now, is it possible to upgrade this to the stable > >> release when it's released? > > > > Unfortunately no. We don't support upgrade from pre-release version to > the final > > one. > > > >> It also seems to lack some documentation for my use cases, but I need > to start > >> with VZ7 sooner or later. > > > > What usecases are you talking about? > > > >> Regards, > >>Volker > >> > >> > >> > -- > >> > Best regards, > >> > Vladimir Porokhov > >> > > >> > > >> > > >> > > >> >> On 03.06.16, 18:04, "Scott Dowdle" behalf of dow...@montanalinux.org> wrote: > >> >> > >> >> Greetings, > >> >> > >> >> - Original Message - > >> >>> we need to prepare a new setup composed of a few nodes (probably 5) > >> >>> for August this year. > >> >>> > >> >>> If I interpreted the wii page correctly, the next VZ7 release will > be > >> >>> a stable one. As you can imagine, we're very tempted to wait for it > >> >>> instead of deploying on OpenVZ and then migrating everything some > >> >>> months later. > >> >>> > >> >>> The only problem is... we have no idea at all about the actual > >> >>> planned release date. > >> >>> > >> >>> Can anyone shed some light on this? Even knowing the quarter (say, > >> >>> Q3 vs Q4) would be of great help to us. > >> >>> > >> >>> (Disclaimer: I realise there are many factors involved, that > >> >>> stability comes at a price of a long(er) development time and I'm > >> >>> not asking for any commitment to an actual date. Just a few hints > >> >>> on 'how close we are' would be more than enough :-) > >> >> > >> >> I don't know the answer... as a user and not a dev... but I would > say deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get > to know it (or do that with the pre-releases)... and when you feel > comfortable with it, migrate the containers from OL to V7... and then you > can wipe your OL hosts and turn them into V7 hosts. You'd only really need > one spare and then just cycle through them one by one... but I realize I've > always operated at a very low scale and there are some really big scale > operators out there. > >> >> > >> >> In any event... who is ready to totally convert even on day one of a > GA? Who even advises doing so even if it is convenient? I'm fairly > confident that the transition from OL to V7 with container migration should > be fairly smooth... even without live migration it shouldn't be too much > trouble if planned for. > >> >> > >> >> TYL, > >> >> -- > >> >> Scott Dowdle > >> >> 704 Church Street > >> >> Belgrade, MT 59714 > >> >> (406)388-0827 [home] > >> >> (406)994-3931 [work] > >> >> ___ > >> >> Users mailing list > >> >> Users@openvz.org > >> >> https://lists.openvz.org/mailman/listinfo/users > >> > > >> > ___ > >> > Users mailing list > >> > Users@openvz.org > >> > https://lists.openvz.org/mailman/listinfo/users > >> > > >> > >> > >> ___ > >> Users mailing list > >> Users@openvz.org > >> https://lists.openvz.org/mailman/listinfo/users > > > > -- > > sergeyb@ > > ___ > > Users mailing list > > Users@openvz.org > > https://lists.openvz.org/mailman/listinfo/users > > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 06/06/2016 06:13 PM, Konstantin Khorenko wrote: On 06/06/2016 02:23 PM, Volker Janzen wrote: Hi Sergey, On 14:39 Sun 05 Jun , Volker Janzen wrote: Unfortunately no. We don't support upgrade from pre-release version to the final one. When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? There is only one supported configuration for new installations - clean Virtuozzo 7 installation. okay I see. My setup will be unsupported if installed on plain CentOS 7 either way. It also seems to lack some documentation for my use cases, but I need to start with VZ7 sooner or later. What usecases are you talking about? My current OpenVZ setup has LVM involved. I want to be able to use simfs based storage on an underlaying LVM volume. Why do you prefer simfs instead of ploop? Did you see comparison simfs vs ploop? https://openvz.org/CT_storage_backends I think you asked me about this some time ago. The matrix states: Reliability Low: big amount of files produce ext4 corruption so often Why should I use something that tells me it's not reliable? Even according to https://github.com/pavel-odintsov/OpenVZ_ZFS/blob/master/openvz_storage_backends.md (which seems to be used as a source of recent page update) this row is incorrect, this info has just been added by Narcis Garcia and is to be corrected. i don't want to start a holly war here, i won't tell that ZFS is worse or whatever, i just know that we really do power crash testing and know the results. And i'm certain that our default suggested solution is good and stable. Yes, there are drawbacks - the most important one now is usage overhead (sic!, not stability for a long time already), and we improve it. And gained quite a good progress. Just did a ploop compaction of my personal work Container, created 03.07.2014 (lot of gits, makes, etc.): # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml --defrag ... # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml --stat Balloon size:0MB Data size: 29189MB Ploop size: 102400MB Image size: 29057MB Yes, i know it's still possible to create an image which will be compacted not that efficiently, but this becomes quite a rare case. Do you have such an image? Send it to us. Thank you. P.S. in fact we don't need full image in most cases, only metadata is essential, so if you worry about data and confidentiality, no problem here: # e2image -r /dev/ploopXXp1 - | bzip2 > image.e2i.bz2 Sorry, better in qcow2 format, much less in size: # e2image -Q /dev/ploopXXp1 - | bzip2 > image.qcow2.bz2 -- Best regards, Konstantin Khorenko, Virtuozzo Linux Kernel Team The /vz partition has also the big advantage of using LVM snapshots and it allows rsync of the container data to another host with less overhead. Also the need to compress the ploop files does not seem to be something I'm willing to do. Regards Volker And I want to be able to setup KVM based VMs that have a LVM based disk, too. In best case KVM VMs can be created from a template, as with the container VMs. Den, is it possible in Vz7? Regards Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users . ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 13:23 Mon 06 Jun , Volker Janzen wrote: > Hi Sergey, > > > On 14:39 Sun 05 Jun , Volker Janzen wrote: > >>> > >>> Unfortunately no. We don't support upgrade from pre-release version to > >>> the final one. > >> > >> When I use a CentOS 7 as base system and install VZ7 afterward it's not > >> possible to upgrade, too? > > > > There is only one supported configuration for new installations - > > clean Virtuozzo 7 installation. > > okay I see. My setup will be unsupported if installed on plain CentOS 7 > either way. I forgot to mention one important thing in my previous answer. As you know Virtuozzo 7 based on VzLinux distribution. VzLinux is a Linux distribution similar to CentOS but it is not the same. VzLinux is not just rebuilded RPM packages from CentOS. Some RPM packages in VzLinux contains fixes or changes specific to Virtuozzo which are absent in RHEL/CentOS. Just for example: - we don't use stock rsync, it includes implementation of additional option which makes container live migration possible. - vzprocps packages are stock ps/top utilities with our patches to support containers monitoring - AFAIK we have patches in gparted package and so on. - Virtuozzo contains the package ext4defrag required to working with ploop images If you have time to fight with troubles which may happen in Vz installed on top of CentOS or any other RPM based Linux distribution - it is your choice. Please understand me correctly, we don't want to support a variety of all Linux zoo. It requires much more time of development, testing and support. > It also seems to lack some documentation for my use cases, but I need to > start > with VZ7 sooner or later. > >>> > >>> What usecases are you talking about? > >> > >> My current OpenVZ setup has LVM involved. > >> I want to be able to use simfs based storage on an underlaying LVM volume. > > > > Why do you prefer simfs instead of ploop? Did you see comparison simfs vs > > ploop? > > https://openvz.org/CT_storage_backends > > I think you asked me about this some time ago. The matrix states: Reliability > Low: big amount of files produce ext4 corruption so often > > Why should I use something that tells me it's not reliable? > > The /vz partition has also the big advantage of using LVM snapshots and it > allows rsync of the container data to another host with less overhead. > > Also the need to compress the ploop files does not seem to be something I'm > willing to do. > > > Regards >Volker > > > > >> And I want to be able to setup KVM based VMs that have a LVM based disk, > >> too. > >> In best case KVM VMs can be created from a template, as with the container > >> VMs. > > > > Den, is it possible in Vz7? > > > >> Regards > >> Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Sergey, > As you know Virtuozzo 7 based on VzLinux distribution. I forgot another question: is there a hardware requirement / compatibility list for VzLinux? As of it's not the same as CentOS, the requirements may be different. Is there software raid support in bare metall installer? Or is hardware raid a requirement? Regards Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Sergey, I suppose one could still migrate CTs from an OVZ7 pre-release to a newly installed OVZ7, is that a reasonable assumption? Is live migration likely to work in this scenario? Jake On Sun, Jun 5, 2016 at 3:55 AM, Sergey Bronnikov wrote: > Hello, Volker > > On 22:06 Fri 03 Jun , Volker Janzen wrote: >> Hi, >> >> > We are going to release Virtuozzo 7 and OpenVZ 7 not later than this July. >> > Thank you for your interest and stay tuned! >> >> when I setup VZ 7 beta now, is it possible to upgrade this to the stable >> release when it's released? > > Unfortunately no. We don't support upgrade from pre-release version to the > final > one. > >> It also seems to lack some documentation for my use cases, but I need to >> start >> with VZ7 sooner or later. > > What usecases are you talking about? > >> Regards, >>Volker >> >> >> > -- >> > Best regards, >> > Vladimir Porokhov >> > >> > >> > >> > >> >> On 03.06.16, 18:04, "Scott Dowdle" > >> dow...@montanalinux.org> wrote: >> >> >> >> Greetings, >> >> >> >> - Original Message - >> >>> we need to prepare a new setup composed of a few nodes (probably 5) >> >>> for August this year. >> >>> >> >>> If I interpreted the wii page correctly, the next VZ7 release will be >> >>> a stable one. As you can imagine, we're very tempted to wait for it >> >>> instead of deploying on OpenVZ and then migrating everything some >> >>> months later. >> >>> >> >>> The only problem is... we have no idea at all about the actual >> >>> planned release date. >> >>> >> >>> Can anyone shed some light on this? Even knowing the quarter (say, >> >>> Q3 vs Q4) would be of great help to us. >> >>> >> >>> (Disclaimer: I realise there are many factors involved, that >> >>> stability comes at a price of a long(er) development time and I'm >> >>> not asking for any commitment to an actual date. Just a few hints >> >>> on 'how close we are' would be more than enough :-) >> >> >> >> I don't know the answer... as a user and not a dev... but I would say >> >> deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get to >> >> know it (or do that with the pre-releases)... and when you feel >> >> comfortable with it, migrate the containers from OL to V7... and then you >> >> can wipe your OL hosts and turn them into V7 hosts. You'd only really >> >> need one spare and then just cycle through them one by one... but I >> >> realize I've always operated at a very low scale and there are some >> >> really big scale operators out there. >> >> >> >> In any event... who is ready to totally convert even on day one of a GA? >> >> Who even advises doing so even if it is convenient? I'm fairly confident >> >> that the transition from OL to V7 with container migration should be >> >> fairly smooth... even without live migration it shouldn't be too much >> >> trouble if planned for. >> >> >> >> TYL, >> >> -- >> >> Scott Dowdle >> >> 704 Church Street >> >> Belgrade, MT 59714 >> >> (406)388-0827 [home] >> >> (406)994-3931 [work] >> >> ___ >> >> Users mailing list >> >> Users@openvz.org >> >> https://lists.openvz.org/mailman/listinfo/users >> > >> > ___ >> > Users mailing list >> > Users@openvz.org >> > https://lists.openvz.org/mailman/listinfo/users >> > >> >> >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users > > -- > sergeyb@ > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Sergey, >> On 13:23 Mon 06 Jun , Volker Janzen wrote: >> Hi Sergey, >> >>> On 14:39 Sun 05 Jun , Volker Janzen wrote: > > Unfortunately no. We don't support upgrade from pre-release version to > the final one. When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? >>> >>> There is only one supported configuration for new installations - >>> clean Virtuozzo 7 installation. >> >> okay I see. My setup will be unsupported if installed on plain CentOS 7 >> either way. > > I forgot to mention one important thing in my previous answer. As you know > Virtuozzo 7 based on VzLinux distribution. VzLinux is a Linux distribution > similar > to CentOS but it is not the same. VzLinux is not just rebuilded RPM packages > from CentOS. Some RPM packages in VzLinux contains fixes or changes specific > to > Virtuozzo which are absent in RHEL/CentOS. So this sentence from the quick Installation guide is just false: "Alternatively, one can install OpenVZ on a pre-installed RPM based Linux distribution. Supported Linux distributions: Cloud Linux 7.*, CentOS 7.*, Scientific Linux 7.* etc" Source: https://openvz.org/Quick_installation_of_Virtuozzo_7 You're telling now it's not an alternative. It should be removed from the guide, it's a huge change in the plans on how to deploy VZ7. For now, I was able to fire up a CentOS 6 host and then follow the guide for installing OpenVZ. With VZ7, I will need to be able to install from my own ISO image, this might cause problems with the hosters I use and I really need to evaluate if this is a good way to go. I really prefer OpenVZ container in favour of lxc and I'd like to stay with it, but I also need an easy way to fire up a new host system. > Please understand me correctly, we don't want to support a variety of all > Linux zoo. > It requires much more time of development, testing and support. It is okay to do that. You're not alone with that. But the install guide should not state an alternative in the setup guide, that is no alternative. I will now need to re-evaluate VZ7 usage completly. Regards, Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 06/06/2016 02:23 PM, Volker Janzen wrote: Hi Sergey, On 14:39 Sun 05 Jun , Volker Janzen wrote: Unfortunately no. We don't support upgrade from pre-release version to the final one. When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? There is only one supported configuration for new installations - clean Virtuozzo 7 installation. okay I see. My setup will be unsupported if installed on plain CentOS 7 either way. It also seems to lack some documentation for my use cases, but I need to start with VZ7 sooner or later. What usecases are you talking about? My current OpenVZ setup has LVM involved. I want to be able to use simfs based storage on an underlaying LVM volume. Why do you prefer simfs instead of ploop? Did you see comparison simfs vs ploop? https://openvz.org/CT_storage_backends I think you asked me about this some time ago. The matrix states: Reliability Low: big amount of files produce ext4 corruption so often Why should I use something that tells me it's not reliable? Even according to https://github.com/pavel-odintsov/OpenVZ_ZFS/blob/master/openvz_storage_backends.md (which seems to be used as a source of recent page update) this row is incorrect, this info has just been added by Narcis Garcia and is to be corrected. i don't want to start a holly war here, i won't tell that ZFS is worse or whatever, i just know that we really do power crash testing and know the results. And i'm certain that our default suggested solution is good and stable. Yes, there are drawbacks - the most important one now is usage overhead (sic!, not stability for a long time already), and we improve it. And gained quite a good progress. Just did a ploop compaction of my personal work Container, created 03.07.2014 (lot of gits, makes, etc.): # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml --defrag ... # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml --stat Balloon size:0MB Data size: 29189MB Ploop size: 102400MB Image size: 29057MB Yes, i know it's still possible to create an image which will be compacted not that efficiently, but this becomes quite a rare case. Do you have such an image? Send it to us. Thank you. P.S. in fact we don't need full image in most cases, only metadata is essential, so if you worry about data and confidentiality, no problem here: # e2image -r /dev/ploopXXp1 - | bzip2 > image.e2i.bz2 -- Best regards, Konstantin Khorenko, Virtuozzo Linux Kernel Team The /vz partition has also the big advantage of using LVM snapshots and it allows rsync of the container data to another host with less overhead. Also the need to compress the ploop files does not seem to be something I'm willing to do. Regards Volker And I want to be able to setup KVM based VMs that have a LVM based disk, too. In best case KVM VMs can be created from a template, as with the container VMs. Den, is it possible in Vz7? Regards Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
> Yes, i know it's still possible to create an image which will be compacted not that efficiently, but this becomes quite a rare case. But in irl - get random prodaction node and first container with max delta (data vs image size) - ploop-balloon discard /vz/private/93713/root.hdd/DiskDescriptor.xml --stat Balloon size:0MB Data size: 30845MB Ploop size: 51200MB Image size: 47546MB ploop-balloon discard /vz/private/93713/root.hdd/DiskDescriptor.xml --defrag ... ploop-balloon discard /vz/private/93713/root.hdd/DiskDescriptor.xml --stat Balloon size:0MB Data size: 30845MB Ploop size: 51200MB Image size: 47433MB And already have 17Gb wasted space for 30Gb data after compact with defrag. ( on node openvz 6 - 2.6.32-042stab114.5 kernel, ploop-1.15-1.x86_64 and e4defrag2 builded from https://github.com/dmonakhov/e2fsprogs/tree/e4defrag2 with commits from 16 May). In irl we have significan overhead on disk operations on compact ploop images. In irl we regular have ploop images which we cannot umount - https://bugs.openvz.org/browse/OVZ-6689 !!! And from time to time backup and compact failed with strange situations like - https://bugs.openvz.org/browse/OVZ-6547 2016-06-06 18:13 GMT+03:00 Konstantin Khorenko : > On 06/06/2016 02:23 PM, Volker Janzen wrote: > >> Hi Sergey, >> >> On 14:39 Sun 05 Jun , Volker Janzen wrote: >>> > Unfortunately no. We don't support upgrade from pre-release version to > the final one. > When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? >>> >>> There is only one supported configuration for new installations - >>> clean Virtuozzo 7 installation. >>> >> >> okay I see. My setup will be unsupported if installed on plain CentOS 7 >> either way. >> >> >>> It also seems to lack some documentation for my use cases, but I need to >> start >> with VZ7 sooner or later. >> > > What usecases are you talking about? > My current OpenVZ setup has LVM involved. I want to be able to use simfs based storage on an underlaying LVM volume. >>> >>> Why do you prefer simfs instead of ploop? Did you see comparison simfs >>> vs ploop? >>> https://openvz.org/CT_storage_backends >>> >> >> I think you asked me about this some time ago. The matrix states: >> Reliability >> Low: big amount of files produce ext4 corruption so often >> >> Why should I use something that tells me it's not reliable? >> > > Even according to > > https://github.com/pavel-odintsov/OpenVZ_ZFS/blob/master/openvz_storage_backends.md > (which seems to be used as a source of recent page update) this row is > incorrect, this info has just been added by Narcis Garcia and is to be > corrected. > > i don't want to start a holly war here, i won't tell that ZFS is worse or > whatever, > i just know that we really do power crash testing and know the results. > And i'm certain that our default suggested solution is good and stable. > > Yes, there are drawbacks - the most important one now is usage overhead > (sic!, not stability for a long time already), and we improve it. > And gained quite a good progress. Just did a ploop compaction of my > personal work Container, created 03.07.2014 (lot of gits, makes, etc.): > > # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml > --defrag > ... > # ploop-balloon discard /vz/private/105/root.hdd/DiskDescriptor.xml --stat > Balloon size:0MB > Data size: 29189MB > Ploop size: 102400MB > Image size: 29057MB > > Yes, i know it's still possible to create an image which will be compacted > not that efficiently, but this becomes quite a rare case. > Do you have such an image? Send it to us. > > Thank you. > > P.S. in fact we don't need full image in most cases, only metadata is > essential, so if you worry about data and confidentiality, no problem here: > # e2image -r /dev/ploopXXp1 - | bzip2 > image.e2i.bz2 > > -- > Best regards, > > Konstantin Khorenko, > Virtuozzo Linux Kernel Team > > > The /vz partition has also the big advantage of using LVM snapshots and it >> allows rsync of the container data to another host with less overhead. >> >> Also the need to compress the ploop files does not seem to be something >> I'm willing to do. >> >> >> Regards >> Volker >> >> >>> And I want to be able to setup KVM based VMs that have a LVM based disk, too. In best case KVM VMs can be created from a template, as with the container VMs. >>> >>> Den, is it possible in Vz7? >>> >>> Regards Volker >>> ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Sergey, do you mean that supported distribution for OpenVZ/Virtuozzo will be (or is) VzLinux OS? Could you document this GNU/Linux distribution with a Wikipedia article? Thanks. El 06/06/16 a les 15:33, Sergey Bronnikov ha escrit: > On 13:23 Mon 06 Jun , Volker Janzen wrote: >> Hi Sergey, >> >>> On 14:39 Sun 05 Jun , Volker Janzen wrote: > > Unfortunately no. We don't support upgrade from pre-release version to > the final one. When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? >>> >>> There is only one supported configuration for new installations - >>> clean Virtuozzo 7 installation. >> >> okay I see. My setup will be unsupported if installed on plain CentOS 7 >> either way. > > I forgot to mention one important thing in my previous answer. As you know > Virtuozzo 7 based on VzLinux distribution. VzLinux is a Linux distribution > similar > to CentOS but it is not the same. VzLinux is not just rebuilded RPM packages > from CentOS. Some RPM packages in VzLinux contains fixes or changes specific > to > Virtuozzo which are absent in RHEL/CentOS. > > Just for example: > - we don't use stock rsync, it includes implementation of additional option > which makes > container live migration possible. > - vzprocps packages are stock ps/top utilities with our patches to support > containers monitoring > - AFAIK we have patches in gparted package > and so on. > - Virtuozzo contains the package ext4defrag required to working with ploop > images > > If you have time to fight with troubles which may happen in Vz installed on > top of CentOS > or any other RPM based Linux distribution - it is your choice. > > Please understand me correctly, we don't want to support a variety of all > Linux zoo. > It requires much more time of development, testing and support. > >> It also seems to lack some documentation for my use cases, but I need to >> start >> with VZ7 sooner or later. > > What usecases are you talking about? My current OpenVZ setup has LVM involved. I want to be able to use simfs based storage on an underlaying LVM volume. >>> >>> Why do you prefer simfs instead of ploop? Did you see comparison simfs vs >>> ploop? >>> https://openvz.org/CT_storage_backends >> >> I think you asked me about this some time ago. The matrix states: Reliability >> Low: big amount of files produce ext4 corruption so often >> >> Why should I use something that tells me it's not reliable? >> >> The /vz partition has also the big advantage of using LVM snapshots and it >> allows rsync of the container data to another host with less overhead. >> >> Also the need to compress the ploop files does not seem to be something I'm >> willing to do. >> >> >> Regards >>Volker >> >>> And I want to be able to setup KVM based VMs that have a LVM based disk, too. In best case KVM VMs can be created from a template, as with the container VMs. >>> >>> Den, is it possible in Vz7? >>> Regards Volker > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Sergey, > On 14:39 Sun 05 Jun , Volker Janzen wrote: >>> >>> Unfortunately no. We don't support upgrade from pre-release version to the >>> final one. >> >> When I use a CentOS 7 as base system and install VZ7 afterward it's not >> possible to upgrade, too? > > There is only one supported configuration for new installations - > clean Virtuozzo 7 installation. okay I see. My setup will be unsupported if installed on plain CentOS 7 either way. > It also seems to lack some documentation for my use cases, but I need to start with VZ7 sooner or later. >>> >>> What usecases are you talking about? >> >> My current OpenVZ setup has LVM involved. >> I want to be able to use simfs based storage on an underlaying LVM volume. > > Why do you prefer simfs instead of ploop? Did you see comparison simfs vs > ploop? > https://openvz.org/CT_storage_backends I think you asked me about this some time ago. The matrix states: Reliability Low: big amount of files produce ext4 corruption so often Why should I use something that tells me it's not reliable? The /vz partition has also the big advantage of using LVM snapshots and it allows rsync of the container data to another host with less overhead. Also the need to compress the ploop files does not seem to be something I'm willing to do. Regards Volker > >> And I want to be able to setup KVM based VMs that have a LVM based disk, too. >> In best case KVM VMs can be created from a template, as with the container >> VMs. > > Den, is it possible in Vz7? > >> Regards >> Volker > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Color coding on this page is also strange. Even advantages of simfs are marked red and disadvantages of ploop - green :-) -Original Message- From: users-boun...@openvz.org [mailto:users-boun...@openvz.org] On Behalf Of Narcis Garcia Sent: Monday, June 6, 2016 14:43 To: users@openvz.org Subject: Re: [Users] New setup - deploy OpenVZ or wait for VZ7? Why the CT_storage_backends page is not showing any "No" in the ploop column, and all "No"s in simfs columns are red (eg.compaction) The "qcow format" row is redundant, as it could be "can use same host filesystem". The "No problems" row seems to be written to put a "Yes" in the "good" column. Similar to the "Better security" label. I'm going to enhance the comparison style in this page. El 06/06/16 a les 12:51, Sergey Bronnikov ha escrit: > Hi, Volker > > On 14:39 Sun 05 Jun , Volker Janzen wrote: >>> >>> Unfortunately no. We don't support upgrade from pre-release version to the >>> final one. >> >> When I use a CentOS 7 as base system and install VZ7 afterward it's not >> possible to upgrade, too? > > There is only one supported configuration for new installations - > clean Virtuozzo 7 installation. > >>>> It also seems to lack some documentation for my use cases, but I need to >>>> start >>>> with VZ7 sooner or later. >>> >>> What usecases are you talking about? >> >> My current OpenVZ setup has LVM involved. >> I want to be able to use simfs based storage on an underlaying LVM volume. > > Why do you prefer simfs instead of ploop? Did you see comparison simfs vs > ploop? > https://openvz.org/CT_storage_backends > >> And I want to be able to setup KVM based VMs that have a LVM based disk, too. >> In best case KVM VMs can be created from a template, as with the container >> VMs. > > Den, is it possible in Vz7? > >> Regards >>Volker > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Why the CT_storage_backends page is not showing any "No" in the ploop column, and all "No"s in simfs columns are red (eg.compaction) The "qcow format" row is redundant, as it could be "can use same host filesystem". The "No problems" row seems to be written to put a "Yes" in the "good" column. Similar to the "Better security" label. I'm going to enhance the comparison style in this page. El 06/06/16 a les 12:51, Sergey Bronnikov ha escrit: > Hi, Volker > > On 14:39 Sun 05 Jun , Volker Janzen wrote: >>> >>> Unfortunately no. We don't support upgrade from pre-release version to the >>> final one. >> >> When I use a CentOS 7 as base system and install VZ7 afterward it's not >> possible to upgrade, too? > > There is only one supported configuration for new installations - > clean Virtuozzo 7 installation. > It also seems to lack some documentation for my use cases, but I need to start with VZ7 sooner or later. >>> >>> What usecases are you talking about? >> >> My current OpenVZ setup has LVM involved. >> I want to be able to use simfs based storage on an underlaying LVM volume. > > Why do you prefer simfs instead of ploop? Did you see comparison simfs vs > ploop? > https://openvz.org/CT_storage_backends > >> And I want to be able to setup KVM based VMs that have a LVM based disk, too. >> In best case KVM VMs can be created from a template, as with the container >> VMs. > > Den, is it possible in Vz7? > >> Regards >>Volker > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
On 06/06/2016 01:51 PM, Sergey Bronnikov wrote: Hi, Volker On 14:39 Sun 05 Jun , Volker Janzen wrote: Unfortunately no. We don't support upgrade from pre-release version to the final one. When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? There is only one supported configuration for new installations - clean Virtuozzo 7 installation. It also seems to lack some documentation for my use cases, but I need to start with VZ7 sooner or later. What usecases are you talking about? My current OpenVZ setup has LVM involved. I want to be able to use simfs based storage on an underlaying LVM volume. Why do you prefer simfs instead of ploop? Did you see comparison simfs vs ploop? https://openvz.org/CT_storage_backends And I want to be able to setup KVM based VMs that have a LVM based disk, too. In best case KVM VMs can be created from a template, as with the container VMs. Den, is it possible in Vz7? this is a matter of internal configuration, which is not related to the emulation at all. Den ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi, Volker On 14:39 Sun 05 Jun , Volker Janzen wrote: > > > > Unfortunately no. We don't support upgrade from pre-release version to the > > final one. > > When I use a CentOS 7 as base system and install VZ7 afterward it's not > possible to upgrade, too? There is only one supported configuration for new installations - clean Virtuozzo 7 installation. > >> It also seems to lack some documentation for my use cases, but I need to > >> start > >> with VZ7 sooner or later. > > > > What usecases are you talking about? > > My current OpenVZ setup has LVM involved. > I want to be able to use simfs based storage on an underlaying LVM volume. Why do you prefer simfs instead of ploop? Did you see comparison simfs vs ploop? https://openvz.org/CT_storage_backends > And I want to be able to setup KVM based VMs that have a LVM based disk, too. > In best case KVM VMs can be created from a template, as with the container > VMs. Den, is it possible in Vz7? > Regards >Volker ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Sergey, > Hello, Volker > >> On 22:06 Fri 03 Jun , Volker Janzen wrote: >> Hi, >> >>> We are going to release Virtuozzo 7 and OpenVZ 7 not later than this July. >>> Thank you for your interest and stay tuned! >> >> when I setup VZ 7 beta now, is it possible to upgrade this to the stable >> release when it's released? > > Unfortunately no. We don't support upgrade from pre-release version to the > final one. When I use a CentOS 7 as base system and install VZ7 afterward it's not possible to upgrade, too? >> It also seems to lack some documentation for my use cases, but I need to >> start >> with VZ7 sooner or later. > > What usecases are you talking about? My current OpenVZ setup has LVM involved. I want to be able to use simfs based storage on an underlaying LVM volume. And I want to be able to setup KVM based VMs that have a LVM based disk, too. In best case KVM VMs can be created from a template, as with the container VMs. Regards Volker >> >> >>> -- >>> Best regards, >>> Vladimir Porokhov >>> >>> >>> >>> On 03.06.16, 18:04, "Scott Dowdle" >>> dow...@montanalinux.org> wrote: Greetings, - Original Message - > we need to prepare a new setup composed of a few nodes (probably 5) > for August this year. > > If I interpreted the wii page correctly, the next VZ7 release will be > a stable one. As you can imagine, we're very tempted to wait for it > instead of deploying on OpenVZ and then migrating everything some > months later. > > The only problem is... we have no idea at all about the actual > planned release date. > > Can anyone shed some light on this? Even knowing the quarter (say, > Q3 vs Q4) would be of great help to us. > > (Disclaimer: I realise there are many factors involved, that > stability comes at a price of a long(er) development time and I'm > not asking for any commitment to an actual date. Just a few hints > on 'how close we are' would be more than enough :-) I don't know the answer... as a user and not a dev... but I would say deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get to know it (or do that with the pre-releases)... and when you feel comfortable with it, migrate the containers from OL to V7... and then you can wipe your OL hosts and turn them into V7 hosts. You'd only really need one spare and then just cycle through them one by one... but I realize I've always operated at a very low scale and there are some really big scale operators out there. In any event... who is ready to totally convert even on day one of a GA? Who even advises doing so even if it is convenient? I'm fairly confident that the transition from OL to V7 with container migration should be fairly smooth... even without live migration it shouldn't be too much trouble if planned for. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users >>> >>> ___ >>> Users mailing list >>> Users@openvz.org >>> https://lists.openvz.org/mailman/listinfo/users >> >> >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users > > -- > sergeyb@ > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hello, Volker On 22:06 Fri 03 Jun , Volker Janzen wrote: > Hi, > > > We are going to release Virtuozzo 7 and OpenVZ 7 not later than this July. > > Thank you for your interest and stay tuned! > > when I setup VZ 7 beta now, is it possible to upgrade this to the stable > release when it's released? Unfortunately no. We don't support upgrade from pre-release version to the final one. > It also seems to lack some documentation for my use cases, but I need to start > with VZ7 sooner or later. What usecases are you talking about? > Regards, >Volker > > > > -- > > Best regards, > > Vladimir Porokhov > > > > > > > > > >> On 03.06.16, 18:04, "Scott Dowdle" >> dow...@montanalinux.org> wrote: > >> > >> Greetings, > >> > >> - Original Message - > >>> we need to prepare a new setup composed of a few nodes (probably 5) > >>> for August this year. > >>> > >>> If I interpreted the wii page correctly, the next VZ7 release will be > >>> a stable one. As you can imagine, we're very tempted to wait for it > >>> instead of deploying on OpenVZ and then migrating everything some > >>> months later. > >>> > >>> The only problem is... we have no idea at all about the actual > >>> planned release date. > >>> > >>> Can anyone shed some light on this? Even knowing the quarter (say, > >>> Q3 vs Q4) would be of great help to us. > >>> > >>> (Disclaimer: I realise there are many factors involved, that > >>> stability comes at a price of a long(er) development time and I'm > >>> not asking for any commitment to an actual date. Just a few hints > >>> on 'how close we are' would be more than enough :-) > >> > >> I don't know the answer... as a user and not a dev... but I would say > >> deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get to > >> know it (or do that with the pre-releases)... and when you feel > >> comfortable with it, migrate the containers from OL to V7... and then you > >> can wipe your OL hosts and turn them into V7 hosts. You'd only really > >> need one spare and then just cycle through them one by one... but I > >> realize I've always operated at a very low scale and there are some really > >> big scale operators out there. > >> > >> In any event... who is ready to totally convert even on day one of a GA? > >> Who even advises doing so even if it is convenient? I'm fairly confident > >> that the transition from OL to V7 with container migration should be > >> fairly smooth... even without live migration it shouldn't be too much > >> trouble if planned for. > >> > >> TYL, > >> -- > >> Scott Dowdle > >> 704 Church Street > >> Belgrade, MT 59714 > >> (406)388-0827 [home] > >> (406)994-3931 [work] > >> ___ > >> Users mailing list > >> Users@openvz.org > >> https://lists.openvz.org/mailman/listinfo/users > > > > ___ > > Users mailing list > > Users@openvz.org > > https://lists.openvz.org/mailman/listinfo/users > > > > > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users -- sergeyb@ ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
I'm not much proficient in english, but I understand that Scott points to OpenVZ/Virtuozzo own distribution as the most reasonable way for releases of the major version 7. This means the following scenario: KVM, LXC, UML, Xen, etc with no specific GNU/Linux distribution (packaged for everyone), but to exist separate OpenVZ GNU/Linux and Virtuozo GNU/Linux distributions focused on specific containerization (Proxmox style). As Linux is not a complete operating system, OpenVZ is not a complete oiperating system too. The GNU/Linux distribution is what completes the operating system, with packages about firewall, mail transport, etc. An OpenVZ GNU/Linux means maintaining everything for a distribution, and people who prefers Debian stable-style packages will not find same consistency level in another distribution not focused in this chapter for environment software. El 04/06/16 a les 00:25, Scott Dowdle ha escrit: > Greetings, > > The sub-subject of this should be: OpenVZ/Virtozzo 7 packages distro packages? > > - Original Message - >> Is it possible to build kernel packages/userspace utilities for >> debian jessie as well ? >> >> Right now there is only kernel/userspaces utilities for debian wheezy >> and userspace only for debian jessie. > > Before I start my semi-rant, I want to make it clear that I'm just a user and > I have no idea what Virtuozzo's plans are. Clear? Ok. Now to start. > > Will there be packages OpenVZ/Virtozzo 7 packages for other distros? I don't > think it is a good idea. As you know, V7 is its own distro... rebuilt from > EL7 (CentOS). It supports both containers and KVM virtual machines... and > offers its own library based tools as well as integrates with libvirt (and > the goal is to upstream the libvirt stuff although I don't know the status of > that). There are a lot more userland tools than the small handful of things > used in OpenVZ Legacy. I believe there are also some lower level distro > packages that have been modified to meet the needs of V7. > > The host node is for running VMs and containers... not other services... not > user accounts... just for virtualization. The strength of say Debian... is > that it is built for a wide range of arches and has a very, very big package > collection. None of that is needed for a V7 virtualization host. Debian is > a "universal OS" aka general purpose. What Virtozzo is offering is a distro > built just for the purpose. > > The work involved in building all of the V7 packages for other distros would > be significant. Then what about the (probably very small number of) distro > packages that V7 would want/need to replace? What about testing it? Both > KVM VMs and containers? How big is that test matrix going to be? Your > distro already has libvirt and KVM packages but you aren't going to try and > use those are you? You want the ones tested with V7. > > Red Hat bought Qumranet... and is the main driving force behind KVM, libvirt, > a significant chunk of every mainline Linux kernel's development (#1 > identifiable company on most all kernel releases)... they ship and support > KVM. They have their own virtualization products built on top of it (well > several if you count OpenShift and all of its flavors and RHEV). They are > the main driving force behind gcc and glibc, etc. They sponsor a lot of > work. RHEL and the EL clones are supported for a long time. Their kernels > are supported for a long time. It is the most appropriate platform (in my > opinion) for building on top of especially when that product is related to a > core competency of EL which is KVM, libvirt, etc. > > When you have a product that has a lot of packages and requires it to all > work together well... trying to shoehorn those all onto multiple distros is a > lot of work. There are two basic approaches... bundle everything you use... > and totally ignore what the underlying distro provides... OR support a > limited number of distros and build specifically for them (the Zimbra > approach... with the number of supported distros dwindling over time). I > don't think either of those would be a good approach giving the nature of a > newish company with a new major release coming out. > > How long is it taking Virtuozzo to get the product to the market after EL7 > was initially released? How long of a lifespan does it have left on that > platform? Compare that to the lifespan of other distros. If V7 was targeted > at a Debian release how much life would that version of Debian have left in > it? It seems to me that about half of the distro lifespan would be devel > time leaving only half of it for deployment time. > > Are Red Hat, Gentoo, SUSE users demanding that Proxmox VE make packages for > them? Not really. Proxmox VE is derived from Debian and can probably be > used easily on any Debian-based distro that uses the stock Debian repos... > but anything else... forget about it
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Wow. Thanks to everyone for sharing their suggestions and thanks to Sergey and Vladimir for chiming in and bringing insiders' knowledge to this thread ;-) In our particular use case, we've decided to go like this: • deploy the beta versions for the new setup • make sure that they work in our intended setup • contribute bug reports, testing, etc. to the final version • deploy the stable VZ7 in production Also Spameden's suggestion is sound: newer hardware calls for more recent kernels. At the end of the day, we just have to continue what we're doing: in fact, some bug reports do not carry my name specifically but come from our team :-) Best, Corrado Fiore ___ > On 4 Jun 2016, at 1:30 AM, jjs - mainphrame wrote: > > Greetings - > > Based on our experience with OVZ 7 over the past several months, it's > already good enough for our needs, where OVZ 7 CTs have been handling > smtp, pop3/imap, spam/virus scanning for several domains, database, > dns and build host duties with very few issues, and those issues that > have occurred, have had easy workarounds. we do have some redundancy > in the form of multiple CTs on separate hosts, and round robin DNS > entries to eliminate single points of failure, but that's just good > practice. > > YMMV of course, we're only using containers and not VMs, and certainly > a Fortune 100 company would want to move much more slowly and > cautiously than we have. > > Jake > > > On Fri, Jun 3, 2016 at 12:40 AM, Corrado Fiore wrote: >> Dear All, >> >> we need to prepare a new setup composed of a few nodes (probably 5) for >> August this year. >> >> If I interpreted the wii page correctly, the next VZ7 release will be a >> stable one. As you can imagine, we're very tempted to wait for it instead >> of deploying on OpenVZ and then migrating everything some months later. >> >> The only problem is... we have no idea at all about the actual planned >> release date. >> >> Can anyone shed some light on this? Even knowing the quarter (say, Q3 vs >> Q4) would be of great help to us. >> >> (Disclaimer: I realise there are many factors involved, that stability >> comes at a price of a long(er) development time and I'm not asking for any >> commitment to an actual date. Just a few hints on 'how close we are' would >> be more than enough :-) >> >> Thanks a lot, >> Corrado Fiore >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Greetings, The sub-subject of this should be: OpenVZ/Virtozzo 7 packages distro packages? - Original Message - > Is it possible to build kernel packages/userspace utilities for > debian jessie as well ? > > Right now there is only kernel/userspaces utilities for debian wheezy > and userspace only for debian jessie. Before I start my semi-rant, I want to make it clear that I'm just a user and I have no idea what Virtuozzo's plans are. Clear? Ok. Now to start. Will there be packages OpenVZ/Virtozzo 7 packages for other distros? I don't think it is a good idea. As you know, V7 is its own distro... rebuilt from EL7 (CentOS). It supports both containers and KVM virtual machines... and offers its own library based tools as well as integrates with libvirt (and the goal is to upstream the libvirt stuff although I don't know the status of that). There are a lot more userland tools than the small handful of things used in OpenVZ Legacy. I believe there are also some lower level distro packages that have been modified to meet the needs of V7. The host node is for running VMs and containers... not other services... not user accounts... just for virtualization. The strength of say Debian... is that it is built for a wide range of arches and has a very, very big package collection. None of that is needed for a V7 virtualization host. Debian is a "universal OS" aka general purpose. What Virtozzo is offering is a distro built just for the purpose. The work involved in building all of the V7 packages for other distros would be significant. Then what about the (probably very small number of) distro packages that V7 would want/need to replace? What about testing it? Both KVM VMs and containers? How big is that test matrix going to be? Your distro already has libvirt and KVM packages but you aren't going to try and use those are you? You want the ones tested with V7. Red Hat bought Qumranet... and is the main driving force behind KVM, libvirt, a significant chunk of every mainline Linux kernel's development (#1 identifiable company on most all kernel releases)... they ship and support KVM. They have their own virtualization products built on top of it (well several if you count OpenShift and all of its flavors and RHEV). They are the main driving force behind gcc and glibc, etc. They sponsor a lot of work. RHEL and the EL clones are supported for a long time. Their kernels are supported for a long time. It is the most appropriate platform (in my opinion) for building on top of especially when that product is related to a core competency of EL which is KVM, libvirt, etc. When you have a product that has a lot of packages and requires it to all work together well... trying to shoehorn those all onto multiple distros is a lot of work. There are two basic approaches... bundle everything you use... and totally ignore what the underlying distro provides... OR support a limited number of distros and build specifically for them (the Zimbra approach... with the number of supported distros dwindling over time). I don't think either of those would be a good approach giving the nature of a newish company with a new major release coming out. How long is it taking Virtuozzo to get the product to the market after EL7 was initially released? How long of a lifespan does it have left on that platform? Compare that to the lifespan of other distros. If V7 was targeted at a Debian release how much life would that version of Debian have left in it? It seems to me that about half of the distro lifespan would be devel time leaving only half of it for deployment time. Are Red Hat, Gentoo, SUSE users demanding that Proxmox VE make packages for them? Not really. Proxmox VE is derived from Debian and can probably be used easily on any Debian-based distro that uses the stock Debian repos... but anything else... forget about it. Now having said all of that... if you can make a compelling argument on why Debian (for the host node) would be a better distro to build upon for this use case (or any other distro), I'm all eyes/ears. Or if someone wants to take all of the code and built packages on their own for other distros that's fine... but expecting Virtuozzo to do it I think is asking too much. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi, > We are going to release Virtuozzo 7 and OpenVZ 7 not later than this July. > Thank you for your interest and stay tuned! when I setup VZ 7 beta now, is it possible to upgrade this to the stable release when it's released? It also seems to lack some documentation for my use cases, but I need to start with VZ7 sooner or later. Regards, Volker > -- > Best regards, > Vladimir Porokhov > > > > >> On 03.06.16, 18:04, "Scott Dowdle" > dow...@montanalinux.org> wrote: >> >> Greetings, >> >> - Original Message - >>> we need to prepare a new setup composed of a few nodes (probably 5) >>> for August this year. >>> >>> If I interpreted the wii page correctly, the next VZ7 release will be >>> a stable one. As you can imagine, we're very tempted to wait for it >>> instead of deploying on OpenVZ and then migrating everything some >>> months later. >>> >>> The only problem is... we have no idea at all about the actual >>> planned release date. >>> >>> Can anyone shed some light on this? Even knowing the quarter (say, >>> Q3 vs Q4) would be of great help to us. >>> >>> (Disclaimer: I realise there are many factors involved, that >>> stability comes at a price of a long(er) development time and I'm >>> not asking for any commitment to an actual date. Just a few hints >>> on 'how close we are' would be more than enough :-) >> >> I don't know the answer... as a user and not a dev... but I would say deploy >> OpenVZ Legacy now... and when V7 goes GA... test it out... get to know it >> (or do that with the pre-releases)... and when you feel comfortable with it, >> migrate the containers from OL to V7... and then you can wipe your OL hosts >> and turn them into V7 hosts. You'd only really need one spare and then just >> cycle through them one by one... but I realize I've always operated at a >> very low scale and there are some really big scale operators out there. >> >> In any event... who is ready to totally convert even on day one of a GA? >> Who even advises doing so even if it is convenient? I'm fairly confident >> that the transition from OL to V7 with container migration should be fairly >> smooth... even without live migration it shouldn't be too much trouble if >> planned for. >> >> TYL, >> -- >> Scott Dowdle >> 704 Church Street >> Belgrade, MT 59714 >> (406)388-0827 [home] >> (406)994-3931 [work] >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users > > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
2016-06-03 19:17 GMT+03:00 vladimir.porok...@gmail.com < vladimir.porok...@gmail.com>: > Hi Guys! > > We are going to release Virtuozzo 7 and OpenVZ 7 not later than this July. > Thank you for your interest and stay tuned! > -- > Best regards, > Vladimir Porokhov > Is it possible to build kernel packages/userspace utilities for debian jessie as well ? Right now there is only kernel/userspaces utilities for debian wheezy and userspace only for debian jessie. Thanks > > > > > On 03.06.16, 18:04, "Scott Dowdle" dow...@montanalinux.org> wrote: > > >Greetings, > > > >- Original Message - > >> we need to prepare a new setup composed of a few nodes (probably 5) > >> for August this year. > >> > >> If I interpreted the wii page correctly, the next VZ7 release will be > >> a stable one. As you can imagine, we're very tempted to wait for it > >> instead of deploying on OpenVZ and then migrating everything some > >> months later. > >> > >> The only problem is... we have no idea at all about the actual > >> planned release date. > >> > >> Can anyone shed some light on this? Even knowing the quarter (say, > >> Q3 vs Q4) would be of great help to us. > >> > >> (Disclaimer: I realise there are many factors involved, that > >> stability comes at a price of a long(er) development time and I'm > >> not asking for any commitment to an actual date. Just a few hints > >> on 'how close we are' would be more than enough :-) > > > >I don't know the answer... as a user and not a dev... but I would say > deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get to > know it (or do that with the pre-releases)... and when you feel comfortable > with it, migrate the containers from OL to V7... and then you can wipe your > OL hosts and turn them into V7 hosts. You'd only really need one spare and > then just cycle through them one by one... but I realize I've always > operated at a very low scale and there are some really big scale operators > out there. > > > >In any event... who is ready to totally convert even on day one of a GA? > Who even advises doing so even if it is convenient? I'm fairly confident > that the transition from OL to V7 with container migration should be fairly > smooth... even without live migration it shouldn't be too much trouble if > planned for. > > > >TYL, > >-- > >Scott Dowdle > >704 Church Street > >Belgrade, MT 59714 > >(406)388-0827 [home] > >(406)994-3931 [work] > >___ > >Users mailing list > >Users@openvz.org > >https://lists.openvz.org/mailman/listinfo/users > > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Greetings - Based on our experience with OVZ 7 over the past several months, it's already good enough for our needs, where OVZ 7 CTs have been handling smtp, pop3/imap, spam/virus scanning for several domains, database, dns and build host duties with very few issues, and those issues that have occurred, have had easy workarounds. we do have some redundancy in the form of multiple CTs on separate hosts, and round robin DNS entries to eliminate single points of failure, but that's just good practice. YMMV of course, we're only using containers and not VMs, and certainly a Fortune 100 company would want to move much more slowly and cautiously than we have. Jake On Fri, Jun 3, 2016 at 12:40 AM, Corrado Fiore wrote: > Dear All, > > we need to prepare a new setup composed of a few nodes (probably 5) for > August this year. > > If I interpreted the wii page correctly, the next VZ7 release will be a > stable one. As you can imagine, we're very tempted to wait for it instead of > deploying on OpenVZ and then migrating everything some months later. > > The only problem is... we have no idea at all about the actual planned > release date. > > Can anyone shed some light on this? Even knowing the quarter (say, Q3 vs Q4) > would be of great help to us. > > (Disclaimer: I realise there are many factors involved, that stability comes > at a price of a long(er) development time and I'm not asking for any > commitment to an actual date. Just a few hints on 'how close we are' would > be more than enough :-) > > Thanks a lot, > Corrado Fiore > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi Guys! We are going to release Virtuozzo 7 and OpenVZ 7 not later than this July. Thank you for your interest and stay tuned! -- Best regards, Vladimir Porokhov On 03.06.16, 18:04, "Scott Dowdle" wrote: >Greetings, > >- Original Message - >> we need to prepare a new setup composed of a few nodes (probably 5) >> for August this year. >> >> If I interpreted the wii page correctly, the next VZ7 release will be >> a stable one. As you can imagine, we're very tempted to wait for it >> instead of deploying on OpenVZ and then migrating everything some >> months later. >> >> The only problem is... we have no idea at all about the actual >> planned release date. >> >> Can anyone shed some light on this? Even knowing the quarter (say, >> Q3 vs Q4) would be of great help to us. >> >> (Disclaimer: I realise there are many factors involved, that >> stability comes at a price of a long(er) development time and I'm >> not asking for any commitment to an actual date. Just a few hints >> on 'how close we are' would be more than enough :-) > >I don't know the answer... as a user and not a dev... but I would say deploy >OpenVZ Legacy now... and when V7 goes GA... test it out... get to know it (or >do that with the pre-releases)... and when you feel comfortable with it, >migrate the containers from OL to V7... and then you can wipe your OL hosts >and turn them into V7 hosts. You'd only really need one spare and then just >cycle through them one by one... but I realize I've always operated at a very >low scale and there are some really big scale operators out there. > >In any event... who is ready to totally convert even on day one of a GA? Who >even advises doing so even if it is convenient? I'm fairly confident that the >transition from OL to V7 with container migration should be fairly smooth... >even without live migration it shouldn't be too much trouble if planned for. > >TYL, >-- >Scott Dowdle >704 Church Street >Belgrade, MT 59714 >(406)388-0827 [home] >(406)994-3931 [work] >___ >Users mailing list >Users@openvz.org >https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Greetings, - Original Message - > we need to prepare a new setup composed of a few nodes (probably 5) > for August this year. > > If I interpreted the wii page correctly, the next VZ7 release will be > a stable one. As you can imagine, we're very tempted to wait for it > instead of deploying on OpenVZ and then migrating everything some > months later. > > The only problem is... we have no idea at all about the actual > planned release date. > > Can anyone shed some light on this? Even knowing the quarter (say, > Q3 vs Q4) would be of great help to us. > > (Disclaimer: I realise there are many factors involved, that > stability comes at a price of a long(er) development time and I'm > not asking for any commitment to an actual date. Just a few hints > on 'how close we are' would be more than enough :-) I don't know the answer... as a user and not a dev... but I would say deploy OpenVZ Legacy now... and when V7 goes GA... test it out... get to know it (or do that with the pre-releases)... and when you feel comfortable with it, migrate the containers from OL to V7... and then you can wipe your OL hosts and turn them into V7 hosts. You'd only really need one spare and then just cycle through them one by one... but I realize I've always operated at a very low scale and there are some really big scale operators out there. In any event... who is ready to totally convert even on day one of a GA? Who even advises doing so even if it is convenient? I'm fairly confident that the transition from OL to V7 with container migration should be fairly smooth... even without live migration it shouldn't be too much trouble if planned for. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
2016-06-03 17:14 GMT+03:00 Narcis Garcia : > We still deploy OpenVZ/6 because we use Debian repositories. > Our needings are covered with "oldstable" at all. > I have no information about OpenVZ/7 binary repositories for Debian. > > > El 03/06/16 a les 09:40, Corrado Fiore ha escrit: > > Dear All, > > > > we need to prepare a new setup composed of a few nodes (probably 5) for > August this year. > > > > If I interpreted the wii page correctly, the next VZ7 release will be a > stable one. As you can imagine, we're very tempted to wait for it instead > of deploying on OpenVZ and then migrating everything some months later. > > > > The only problem is... we have no idea at all about the actual planned > release date. > > > > Can anyone shed some light on this? Even knowing the quarter (say, Q3 > vs Q4) would be of great help to us. > It really depends on your hardware. If you're using modern hardware I'd not recommend using CentOS 6/Debian Wheezy (OpenVZ old kernel). VZ7 is still in beta, so using it in production is very risky. Also, if you're using dm-crypt with Full Disk Encryption there might be a slowdown with 2.6.32 kernel because it doesn't support TRIM for encrypted devices. I've been using myself OpenVZ for number of years and really don't like specific kernel binding (e.g. for OpenVZ 2.6.32 rhel6 and for VZ7 3.10 rhel7). The only alternative for modern hardware (e.g. NVME PCI-E ssds or some modern SSDs) is to use upstream distro kernel with LXC/KVM. > > > (Disclaimer: I realise there are many factors involved, that stability > comes at a price of a long(er) development time and I'm not asking for any > commitment to an actual date. Just a few hints on 'how close we are' would > be more than enough :-) > > > > Thanks a lot, > > Corrado Fiore > > ___ > > Users mailing list > > Users@openvz.org > > https://lists.openvz.org/mailman/listinfo/users > > > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
Hi, Corrado! On 15:40 Fri 03 Jun , Corrado Fiore wrote: > Dear All, > > we need to prepare a new setup composed of a few nodes (probably 5) for August > this year. Good news :) > If I interpreted the wii page correctly, the next VZ7 release will be a stable > one. As you can imagine, we're very tempted to wait for it instead of > deploying > on OpenVZ and then migrating everything some months later. Yes, we are very close to the final release of Virtuozzo 7. We have released all planned beta versions and our next public version will be RTM. Right now engineers busy with final testing and bugfixing before release and we publish each new Vz7 build on download.openvz.org (https://download.openvz.org/virtuozzo/releases/7.0-rtm/x86_64/iso/). I highly recommend to try published pre-RTM builds because one of them will be final and we interested in fixing most of a bugs prior to release. So the answer is: wait for final release and then deploy it instead of current version of OpenVZ. > The only problem is... we have no idea at all about the actual planned > release date. Unfortunately I cannot provide exact dates for the release. > Can anyone shed some light on this? Even knowing the quarter (say, Q3 vs Q4) > would be of great help to us. > > (Disclaimer: I realise there are many factors involved, that stability comes > at a price of a long(er) development time and I'm not asking for any > commitment > to an actual date. Just a few hints on 'how close we are' would be more than > enough :-) > > Thanks a lot, > Corrado Fiore > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] New setup - deploy OpenVZ or wait for VZ7?
We still deploy OpenVZ/6 because we use Debian repositories. Our needings are covered with "oldstable" at all. I have no information about OpenVZ/7 binary repositories for Debian. El 03/06/16 a les 09:40, Corrado Fiore ha escrit: > Dear All, > > we need to prepare a new setup composed of a few nodes (probably 5) for > August this year. > > If I interpreted the wii page correctly, the next VZ7 release will be a > stable one. As you can imagine, we're very tempted to wait for it instead of > deploying on OpenVZ and then migrating everything some months later. > > The only problem is... we have no idea at all about the actual planned > release date. > > Can anyone shed some light on this? Even knowing the quarter (say, Q3 vs Q4) > would be of great help to us. > > (Disclaimer: I realise there are many factors involved, that stability comes > at a price of a long(er) development time and I'm not asking for any > commitment to an actual date. Just a few hints on 'how close we are' would > be more than enough :-) > > Thanks a lot, > Corrado Fiore > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
[Users] New setup - deploy OpenVZ or wait for VZ7?
Dear All, we need to prepare a new setup composed of a few nodes (probably 5) for August this year. If I interpreted the wii page correctly, the next VZ7 release will be a stable one. As you can imagine, we're very tempted to wait for it instead of deploying on OpenVZ and then migrating everything some months later. The only problem is... we have no idea at all about the actual planned release date. Can anyone shed some light on this? Even knowing the quarter (say, Q3 vs Q4) would be of great help to us. (Disclaimer: I realise there are many factors involved, that stability comes at a price of a long(er) development time and I'm not asking for any commitment to an actual date. Just a few hints on 'how close we are' would be more than enough :-) Thanks a lot, Corrado Fiore ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
