It might also be helpful to know what version of ACS as well.
Some indication of your plan/desire to upgrade ACS, hypervisor, or
management server operating system might be helpful.
There is a big difference between the situation where someone is running
ACS 4.9x on CentOS 6 and wants to upgrade to ACS 4.12 while keeping
CentOS 6 and another environment where the planned upgrade to ACS4.12
will be done at the same time as an upgrade to CentOS 7.x.
Is it fair to say that any proposed changes in this area will occur in
4.12 at the earliest and will not likely occur before summer 2018?
Ron
On 17/01/2018 4:23 AM, Paul Angus wrote:
Thanks Eric,
As you'll see from the intro email to this thread, the purpose here is to
ensure that we don't strand a 'non-trivial' number of users by dropping support
for any given hypervisor, or management server operating system.
Hence the request to users to let the community know what they are using, so
that a fact-based community consensus can be reached.
Kind regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-----Original Message-----
From: Eric Lee Green [mailto:eric.lee.gr...@gmail.com]
Sent: 16 January 2018 23:36
To: us...@cloudstack.apache.org
Subject: Re: [PROPOSE] EOL for supported OSes & Hypervisors
This is the type of discussion that I wanted to open - the argument
that I see for earlier dropping of v6 is that - Between May 2018 and
q2 2020 RHEL/CentOS 6.x will only receive security and mission
critical updates, meanwhile packages on which we depend or may want to
utilise in the future are been deprecated or not developed for v6.x
But this has always been the case for Centos 6.x. It is running antique
versions of everything, and has been doing so for quite some time. It is, for
example, running versions of Gnome and init that have been obsolete for years.
Same deal with the version of MySQL that it comes with.
The reality is that Centos 6.x guest support, at the very least, needs to be
tested with each new version of Cloudstack until final EOL of Centos 6 in Q2
2020. New versions of Cloudstack with new features not supported by Centos 6
(such as LVM support for KVM, which requires the LIO storage stack) can require
Centos 7 or later, but the last Cloudstack version that supports Centos 6.x as
its server host should continue to receive bug fixes until Centos 6.x is EOL.
Making someone's IT investment obsolete is a way to irrelevancy.
Cloudstack is already an also-ran in the cloud marketplace. Making someone's IT
investment obsolete before the official EOL time for their IT investment is a
good way to have a mass migration away from your technology.
This doesn't particularly affect me since my Centos 6 virtualization hosts are
not running Cloudstack and are going to be re-imaged to Centos
7 before being added to the Cloudstack cluster, but ignoring the IT environment that
people actually live in, as versus the one we wish existed, is annoying regardless. A
friend of mine once said of the state of ERP software, "enterprise software is dog
food if dog food was being designed by cats." I.e., the people writing the software
rarely have any understanding of how it is actually used by real life enterprises in real
life environments. Don't be those people.
On 01/16/2018 09:58 AM, Paul Angus wrote:
Hi Eric,
This is the type of discussion that I wanted to open - the argument
that I see for earlier dropping of v6 is that - Between May 2018 and q2 2020
RHEL/CentOS 6.x will only receive security and mission critical updates,
meanwhile packages on which we depend or may want to utilise in the future are
been deprecated or not developed for v6.x Also the testing and development
burden on the CloudStack community increases as we try to maintain backward
compatibility while including new versions.
Needing installation documentation for centos 7 is a great point, and something
that we need to address regardless.
Does anyone else have a view, I'd really like to here from a wide range of
people.
Kind regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
-----Original Message-----
From: Eric Green [mailto:eric.lee.gr...@gmail.com]
Sent: 12 January 2018 17:24
To: us...@cloudstack.apache.org
Cc: dev@cloudstack.apache.org
Subject: Re: [PROPOSE] EOL for supported OSes & Hypervisors
Official EOL for Centos 6 / RHEL 6 as declared by Red Hat Software is
11/30/2020. Jumping the gun a bit there, padme.
People on Centos 6 should certainly be working on a migration strategy right
now, but the end is not here *yet*. Furthermore, the install documentation is
still written for Centos 6 rather than Centos 7. That needs to be fixed before
discontinuing support for Centos 6, eh?
On Jan 12, 2018, at 04:35, Rohit Yadav <rohit.ya...@shapeblue.com> wrote:
+1 I've updated the page with upcoming Ubuntu 18.04 LTS.
After 4.11, I think 4.12 (assuming releases by mid of 2018) should remove
"declared" (they might still work with 4.12+ but in docs and by project we
should officially support them) support for following:
a. Hypervisor:
XenServer - 6.2, 6.5,
KVM - CentOS6, RHEL6, Ubuntu12.04 (I think this is already removed,
packages don't work I think?)
vSphere/Vmware - 4.x, 5.0, 5.1, 5.5
b. Remove packaging for CentOS6.x, RHEL 6.x (the el6 packages), and Ubuntu
12.04 (any non-systemd debian distro).
Thoughts, comments?
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
