As an operations guy I can understand the want for future updates and not upgrading, but with the release plan of RHEL/CentOS I don't find it feasible.
RHEL6 is 8 years old (and is still running kernel 2.6!) and isn't scheduled to be fully EOL until 2024. It is true that upgrading requires some effort (and risk) from operators, but this is work they eventually have to do anyway, so it's not a matter of /if/ they have to do it, but rather when. It is also true that current CloudStack releases should continue to work, it's also possible that someone might back port future fixes to a RHEL6 compatible fork (you're more than welcome to). I'd vote +1 to remove support for el6 packaging. -- Erik On Mon, Apr 22, 2019 at 11:54 AM Vladimir Melnik <v.mel...@uplink.ua> wrote: > > Hi Rohit, > > I agree that being stuck to CentOS-6 is not the best strategy and I'd gladly > get rid of this old distro in my environments. It could be pretty easy to > upgrade the management servers, but upgrading the hosts means "cold" > migration from the CentOS6-based cluster to a CentOS7-based one (alas, "hot" > migration between different QEMUs won't work, I tried it before). So I'll > have to move ~100 VMs between the clusters, which means shutting them all > down one by one. That's scary :-) > > Maybe it would be possible to make ACS "know" what operating system is being > run, so ACS could only use the available features? It would be cool. > > On Sun, Apr 21, 2019 at 08:02:00PM +0000, Rohit Yadav wrote: > > Hi Vladimir, > > > > > > Thanks for sharing your opinion. I can understand the position of our > > conservative users such as yourself with respect to a potential upgrade, > > both the effort and the risks involved in doing the upgrades. > > > > > > That said, I would like to encourage you and other conservative users to > > consider upgrading because it becomes difficult to support older > > distributions moving forward especially when CentOS/RHEL 8 will arrive and > > it also hinders us to (a) support newer features wrt KVM and (b) forces us > > to depend on older distro-provided dependencies that CloudStack uses and > > potentially puts a cloud environment under security risks. > > > > > > As Andrija puts it, you can attempt to upgrade to CentOS7 based infra by > > doing a fresh installation and move to the new server/hosts in a rolling > > way. If you'd need any pointers in that regard I'm sure we can ask Andrija > > and others to share some details on how to do that. Meanwhile, you may also > > refer to my colleague Dag's talk on upgrade best practices from CCCNA17: > > https://www.slideshare.net/ShapeBlue/cccna17-cloudstack-upgrade-best-practicespdf > > > > > > I would like to hear again from you on this and see if we can all agree > > towards a decision that benefits all of our community. Thanks. > > > > > > Regards, > > > > Rohit Yadav > > > > Software Architect, ShapeBlue > > > > https://www.shapeblue.com > > > > ________________________________ > > From: Vladimir Melnik <v.mel...@uplink.ua> > > Sent: Friday, April 19, 2019 8:01:20 PM > > To: us...@cloudstack.apache.org > > Cc: dev@cloudstack.apache.org > > Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14 > > > > Dear colleagues, > > > > As for me, I still have 3 hosts running CentOS 6 and 2 management servers > > in one of my production environments. > > > > Also I have 1 management servers running CentOS 6 in another environment. > > > > If my voice counts, I'd propose -1. > > > > Thanks for attention :-) > > > > On Mon, Apr 15, 2019 at 07:44:58AM +0000, Rohit Yadav wrote: > > > All, > > > > > > > > > With CentOS8 around the corner to be released sometime around the summer, > > > I would like to propose to deprecate CentOS6 as support management server > > > host distro and KVM host distro. Non-systemd enabled Ubuntu releases have > > > been already deprecated [1]. > > > > > > > > > The older CentOS6 version would hold us back as we try to adapt, use and > > > support newer JRE version, kvm/libvirt version, the Linux kernel, and > > > several other older dependencies. Both CentOS6 and RHEL6 have reached EOL > > > on May 10th, 2017 wrt full updates [1]. > > > > > > > > > If we don't have any disagreements, I propose we remove el6 packaging > > > support in the next major release - 4.13. But, if there are users and > > > organisations that will be badly impacted, let 4.13 be the last of > > > releases to support el6 and we definitely remove el6 support in 4.14. > > > > > > What are your thoughts? > > > > > > > > > [1] EOL date wiki reference: > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hypervisor+and+Management+Server+OS+EOL+Dates > > > > > > > > > > > > Regards, > > > > > > Rohit Yadav > > > > > > Software Architect, ShapeBlue > > > > > > https://www.shapeblue.com > > > > > > rohit.ya...@shapeblue.com > > > www.shapeblue.com<http://www.shapeblue.com> > > > Amadeus House, Floral Street, London WC2E 9DPUK > > > @shapeblue > > > > > > > > > > > > > -- > > V.Melnik > > > > rohit.ya...@shapeblue.com > > www.shapeblue.com > > Amadeus House, Floral Street, London WC2E 9DPUK > > @shapeblue > > > > > > > > -- > V.Melnik
