You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Rohit Yadav <ro...@shapeblue.com> on 2019/04/15 07:44:58 UTC

[DISCUSS] Remove support for el6 packaging in 4.13/4.14

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.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Pierre-Luc Dion <pd...@apache.org>.
I agree, it should simplify builds too.


On Mon, Apr 15, 2019 at 7:17 AM Andrija Panic <an...@gmail.com>
wrote:

> +1
>
> CentOS 6 was a pain to make any newer features works, in regards to ancient
> qemu/libvirt and so on.
>
> On Mon, 15 Apr 2019 at 10:05, Wido den Hollander <wi...@widodh.nl> wrote:
>
> >
> >
> > On 4/15/19 9:44 AM, 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?
> >
> > I agree! EL6 is just no longer suited for development. Good suggestion.
> >
> > Wido
> >
> > >
> > >
> > > [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.yadav@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> >
>
>
> --
>
> Andrija Panić
>

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Andrija Panic <an...@gmail.com>.
+1

CentOS 6 was a pain to make any newer features works, in regards to ancient
qemu/libvirt and so on.

On Mon, 15 Apr 2019 at 10:05, Wido den Hollander <wi...@widodh.nl> wrote:

>
>
> On 4/15/19 9:44 AM, 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?
>
> I agree! EL6 is just no longer suited for development. Good suggestion.
>
> Wido
>
> >
> >
> > [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.yadav@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>


-- 

Andrija Panić

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Wido den Hollander <wi...@widodh.nl>.

On 4/15/19 9:44 AM, 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?

I agree! EL6 is just no longer suited for development. Good suggestion.

Wido

> 
> 
> [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.yadav@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>   
>  
> 
> 

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Simon Weller <sw...@ena.com.INVALID>.
+1.


________________________________
From: Nux! <nu...@li.nux.ro>
Sent: Monday, April 15, 2019 8:20 AM
To: dev
Cc: users
Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

+1, EL6 is in its last phase of support.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Rohit Yadav" <ro...@shapeblue.com>
> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
> Sent: Monday, 15 April, 2019 08:44:58
> Subject: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

> 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.yadav@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Simon Weller <sw...@ena.com.INVALID>.
+1.


________________________________
From: Nux! <nu...@li.nux.ro>
Sent: Monday, April 15, 2019 8:20 AM
To: dev
Cc: users
Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

+1, EL6 is in its last phase of support.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Rohit Yadav" <ro...@shapeblue.com>
> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
> Sent: Monday, 15 April, 2019 08:44:58
> Subject: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

> 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.yadav@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Nux! <nu...@li.nux.ro>.
+1, EL6 is in its last phase of support.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Rohit Yadav" <ro...@shapeblue.com>
> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
> Sent: Monday, 15 April, 2019 08:44:58
> Subject: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

> 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.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Andrija Panic <an...@gmail.com>.
+1


On Tue, May 21, 2019, 13:43 Sven Vogel <S....@ewerk.com> wrote:

> +1
>
> Von meinem iPhone gesendet
>
>
> __
>
> Sven Vogel
> Teamlead Platform
>
> EWERK RZ GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 11
> F +49 341 42649 - 18
> S.Vogel@ewerk.com
> www.ewerk.com
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Frank Richter, Gerhard Hoyer
> Registergericht: Leipzig HRB 17023
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 21.05.2019 um 12:44 schrieb Boris Stoyanov <
> boris.stoyanov@shapeblue.com>:
> >
> > +1
> >
> > —Bobby
> >
> >
> > boris.stoyanov@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >> On 21 May 2019, at 13:31, Wei ZHOU <us...@gmail.com> wrote:
> >>
> >> +1
> >>
> >> -Wei
> >>
> >> Rohit Yadav <ro...@shapeblue.com> 于2019年5月21日周二 上午11:40写道:
> >>
> >>> All,
> >>>
> >>>
> >>> Thank you for your feedback and discussions. From what we've discussed
> so
> >>> far, we've lazy consensus that nobody wants to use el6 or are limited
> to
> >>> upgrade to el7/el8 due to potential risks.
> >>>
> >>>
> >>> Moving forward I put forth the following for voting:
> >>>
> >>>
> >>> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last
> ones
> >>> to support el6 packaging both for the management server and KVM host,
> but
> >>> users are discouraged from using them
> >>>
> >>> - Next major release (4.13.0.0) will document in its release notes that
> >>> we'll stop supporting centos6/rhel6 packaging in future versions, i.e.
> 4.14
> >>> and onwards
> >>>
> >>> - After 4.13.0.0 is released, we will remove el6 related specs,
> packaging
> >>> scripts etc. from the codebase in the master branch
> >>>
> >>>
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove (and reason why)
> >>>
> >>>
> >>> ** PMCs kindly add binding to your votes, thanks.
> >>>
> >>>
> >>> Thanks.
> >>>
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Rohit Yadav
> >>>
> >>> Software Architect, ShapeBlue
> >>>
> >>> https://www.shapeblue.com
> >>>
> >>>
> >>> ________________________________
> >>> From: Erik Weber <te...@gmail.com>
> >>> Sent: Wednesday, April 24, 2019 19:32
> >>> To: dev
> >>> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
> >>>
> >>> CentOS7 was released 5 years ago, upgrading is long overdue anyway.
> >>> Realistically the next CloudStack release won't be out the door for
> >>> another ~4-6 months either.
> >>>
> >>> --
> >>> Erik
> >>>
> >>> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
> >>> <rw...@artifact-software.com> wrote:
> >>>>
> >>>> According to https://en.wikipedia.org/wiki/CentOS
> >>>>
> >>>> CentOS 6 EOL is 2020
> >>>> CentOS 7 EOL is 2024
> >>>>
> >>>>
> >>>> +1 for removing support for CentOS 6.
> >>>>
> >>>> As Erik pointed out the sites running CentOS6 will have to move soon
> in
> >>>> any event and it is probably better to do it now when there is still a
> >>>> lot of current expertise and information available about how to do it
> >>>> and how to make any changes to applications.
> >>>>
> >>>> Upgrading in a project that is under your control is usually easier
> than
> >>>> one forced on you by a security issue or an operational failure.
> >>>>
> >>>> Ron
> >>>>
> >>>>> On 4/24/19 3:24 AM, Erik Weber wrote:
> >>>>> 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.
> >>>>>
> >>>
> >>> rohit.yadav@shapeblue.com
> >>> www.shapeblue.com
> >>> Amadeus House, Floral Street, London  WC2E 9DPUK
> >>> @shapeblue
> >>>
> >>>
> >>>
> >>>
> >
>

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Sven Vogel <S....@ewerk.com>.
+1

Von meinem iPhone gesendet


__

Sven Vogel
Teamlead Platform

EWERK RZ GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 11
F +49 341 42649 - 18
S.Vogel@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter, Gerhard Hoyer
Registergericht: Leipzig HRB 17023

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 20000-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen Dank.

The contents of this e-mail (including any attachments) are confidential and may be legally privileged. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system. Thank you.
> Am 21.05.2019 um 12:44 schrieb Boris Stoyanov <bo...@shapeblue.com>:
>
> +1
>
> —Bobby
>
>
> boris.stoyanov@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>> On 21 May 2019, at 13:31, Wei ZHOU <us...@gmail.com> wrote:
>>
>> +1
>>
>> -Wei
>>
>> Rohit Yadav <ro...@shapeblue.com> 于2019年5月21日周二 上午11:40写道:
>>
>>> All,
>>>
>>>
>>> Thank you for your feedback and discussions. From what we've discussed so
>>> far, we've lazy consensus that nobody wants to use el6 or are limited to
>>> upgrade to el7/el8 due to potential risks.
>>>
>>>
>>> Moving forward I put forth the following for voting:
>>>
>>>
>>> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones
>>> to support el6 packaging both for the management server and KVM host, but
>>> users are discouraged from using them
>>>
>>> - Next major release (4.13.0.0) will document in its release notes that
>>> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14
>>> and onwards
>>>
>>> - After 4.13.0.0 is released, we will remove el6 related specs, packaging
>>> scripts etc. from the codebase in the master branch
>>>
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>>
>>> ** PMCs kindly add binding to your votes, thanks.
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Rohit Yadav
>>>
>>> Software Architect, ShapeBlue
>>>
>>> https://www.shapeblue.com
>>>
>>>
>>> ________________________________
>>> From: Erik Weber <te...@gmail.com>
>>> Sent: Wednesday, April 24, 2019 19:32
>>> To: dev
>>> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
>>>
>>> CentOS7 was released 5 years ago, upgrading is long overdue anyway.
>>> Realistically the next CloudStack release won't be out the door for
>>> another ~4-6 months either.
>>>
>>> --
>>> Erik
>>>
>>> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
>>> <rw...@artifact-software.com> wrote:
>>>>
>>>> According to https://en.wikipedia.org/wiki/CentOS
>>>>
>>>> CentOS 6 EOL is 2020
>>>> CentOS 7 EOL is 2024
>>>>
>>>>
>>>> +1 for removing support for CentOS 6.
>>>>
>>>> As Erik pointed out the sites running CentOS6 will have to move soon in
>>>> any event and it is probably better to do it now when there is still a
>>>> lot of current expertise and information available about how to do it
>>>> and how to make any changes to applications.
>>>>
>>>> Upgrading in a project that is under your control is usually easier than
>>>> one forced on you by a security issue or an operational failure.
>>>>
>>>> Ron
>>>>
>>>>> On 4/24/19 3:24 AM, Erik Weber wrote:
>>>>> 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.
>>>>>
>>>
>>> rohit.yadav@shapeblue.com
>>> www.shapeblue.com
>>> Amadeus House, Floral Street, London  WC2E 9DPUK
>>> @shapeblue
>>>
>>>
>>>
>>>
>

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Boris Stoyanov <bo...@shapeblue.com>.
+1

—Bobby


boris.stoyanov@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

> On 21 May 2019, at 13:31, Wei ZHOU <us...@gmail.com> wrote:
> 
> +1
> 
> -Wei
> 
> Rohit Yadav <ro...@shapeblue.com> 于2019年5月21日周二 上午11:40写道:
> 
>> All,
>> 
>> 
>> Thank you for your feedback and discussions. From what we've discussed so
>> far, we've lazy consensus that nobody wants to use el6 or are limited to
>> upgrade to el7/el8 due to potential risks.
>> 
>> 
>> Moving forward I put forth the following for voting:
>> 
>> 
>> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones
>> to support el6 packaging both for the management server and KVM host, but
>> users are discouraged from using them
>> 
>> - Next major release (4.13.0.0) will document in its release notes that
>> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14
>> and onwards
>> 
>> - After 4.13.0.0 is released, we will remove el6 related specs, packaging
>> scripts etc. from the codebase in the master branch
>> 
>> 
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>> 
>> 
>> ** PMCs kindly add binding to your votes, thanks.
>> 
>> 
>> Thanks.
>> 
>> 
>> 
>> Regards,
>> 
>> Rohit Yadav
>> 
>> Software Architect, ShapeBlue
>> 
>> https://www.shapeblue.com
>> 
>> 
>> ________________________________
>> From: Erik Weber <te...@gmail.com>
>> Sent: Wednesday, April 24, 2019 19:32
>> To: dev
>> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
>> 
>> CentOS7 was released 5 years ago, upgrading is long overdue anyway.
>> Realistically the next CloudStack release won't be out the door for
>> another ~4-6 months either.
>> 
>> --
>> Erik
>> 
>> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
>> <rw...@artifact-software.com> wrote:
>>> 
>>> According to https://en.wikipedia.org/wiki/CentOS
>>> 
>>> CentOS 6 EOL is 2020
>>> CentOS 7 EOL is 2024
>>> 
>>> 
>>> +1 for removing support for CentOS 6.
>>> 
>>> As Erik pointed out the sites running CentOS6 will have to move soon in
>>> any event and it is probably better to do it now when there is still a
>>> lot of current expertise and information available about how to do it
>>> and how to make any changes to applications.
>>> 
>>> Upgrading in a project that is under your control is usually easier than
>>> one forced on you by a security issue or an operational failure.
>>> 
>>> Ron
>>> 
>>> On 4/24/19 3:24 AM, Erik Weber wrote:
>>>> 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.
>>>> 
>> 
>> rohit.yadav@shapeblue.com
>> www.shapeblue.com
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>> @shapeblue
>> 
>> 
>> 
>> 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Wei ZHOU <us...@gmail.com>.
+1

-Wei

Rohit Yadav <ro...@shapeblue.com> 于2019年5月21日周二 上午11:40写道:

> All,
>
>
> Thank you for your feedback and discussions. From what we've discussed so
> far, we've lazy consensus that nobody wants to use el6 or are limited to
> upgrade to el7/el8 due to potential risks.
>
>
> Moving forward I put forth the following for voting:
>
>
> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones
> to support el6 packaging both for the management server and KVM host, but
> users are discouraged from using them
>
> - Next major release (4.13.0.0) will document in its release notes that
> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14
> and onwards
>
> - After 4.13.0.0 is released, we will remove el6 related specs, packaging
> scripts etc. from the codebase in the master branch
>
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> ** PMCs kindly add binding to your votes, thanks.
>
>
> Thanks.
>
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
>
> ________________________________
> From: Erik Weber <te...@gmail.com>
> Sent: Wednesday, April 24, 2019 19:32
> To: dev
> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
>
> CentOS7 was released 5 years ago, upgrading is long overdue anyway.
> Realistically the next CloudStack release won't be out the door for
> another ~4-6 months either.
>
> --
> Erik
>
> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
> <rw...@artifact-software.com> wrote:
> >
> > According to https://en.wikipedia.org/wiki/CentOS
> >
> > CentOS 6 EOL is 2020
> > CentOS 7 EOL is 2024
> >
> >
> > +1 for removing support for CentOS 6.
> >
> > As Erik pointed out the sites running CentOS6 will have to move soon in
> > any event and it is probably better to do it now when there is still a
> > lot of current expertise and information available about how to do it
> > and how to make any changes to applications.
> >
> > Upgrading in a project that is under your control is usually easier than
> > one forced on you by a security issue or an operational failure.
> >
> > Ron
> >
> > On 4/24/19 3:24 AM, Erik Weber wrote:
> > > 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.
> > >
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Rohit Yadav <ro...@shapeblue.com>.
All,


Thanks for voting. Based on the voting, we have an 11/11 majority and agree that el6 support (management server, usage server, KVM host) will be removed in future CloudStack 4.14. I'll submit a PR after 4.13.


For reference, the vote counts are as follows:


1 x +1 (binding) - Paul


10 x +1 - Dag, Anurag, Wei, Bobby, Erik, Sven, Andrija, Wido, Pierre-Luc, Gregor


0 x 0 - none


0 x -1 - none



Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

________________________________
From: Riepl, Gregor (SWISS TXT) <Gr...@swisstxt.ch>
Sent: Tuesday, May 21, 2019 7:56:11 PM
To: users@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Rohit Yadav <ro...@shapeblue.com>.
All,


Thanks for voting. Based on the voting, we have an 11/11 majority and agree that el6 support (management server, usage server, KVM host) will be removed in future CloudStack 4.14. I'll submit a PR after 4.13.


For reference, the vote counts are as follows:


1 x +1 (binding) - Paul


10 x +1 - Dag, Anurag, Wei, Bobby, Erik, Sven, Andrija, Wido, Pierre-Luc, Gregor


0 x 0 - none


0 x -1 - none



Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

________________________________
From: Riepl, Gregor (SWISS TXT) <Gr...@swisstxt.ch>
Sent: Tuesday, May 21, 2019 7:56:11 PM
To: users@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by "Riepl, Gregor (SWISS TXT)" <Gr...@swisstxt.ch>.
+1

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by "Riepl, Gregor (SWISS TXT)" <Gr...@swisstxt.ch>.
+1

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Erik Weber <te...@gmail.com>.
+1

Erik

tir. 21. mai 2019 kl. 11:40 skrev Rohit Yadav <ro...@shapeblue.com>:

> All,
>
>
> Thank you for your feedback and discussions. From what we've discussed so
> far, we've lazy consensus that nobody wants to use el6 or are limited to
> upgrade to el7/el8 due to potential risks.
>
>
> Moving forward I put forth the following for voting:
>
>
> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones
> to support el6 packaging both for the management server and KVM host, but
> users are discouraged from using them
>
> - Next major release (4.13.0.0) will document in its release notes that
> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14
> and onwards
>
> - After 4.13.0.0 is released, we will remove el6 related specs, packaging
> scripts etc. from the codebase in the master branch
>
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
> ** PMCs kindly add binding to your votes, thanks.
>
>
> Thanks.
>
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
>
> ________________________________
> From: Erik Weber <te...@gmail.com>
> Sent: Wednesday, April 24, 2019 19:32
> To: dev
> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
>
> CentOS7 was released 5 years ago, upgrading is long overdue anyway.
> Realistically the next CloudStack release won't be out the door for
> another ~4-6 months either.
>
> --
> Erik
>
> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
> <rw...@artifact-software.com> wrote:
> >
> > According to https://en.wikipedia.org/wiki/CentOS
> >
> > CentOS 6 EOL is 2020
> > CentOS 7 EOL is 2024
> >
> >
> > +1 for removing support for CentOS 6.
> >
> > As Erik pointed out the sites running CentOS6 will have to move soon in
> > any event and it is probably better to do it now when there is still a
> > lot of current expertise and information available about how to do it
> > and how to make any changes to applications.
> >
> > Upgrading in a project that is under your control is usually easier than
> > one forced on you by a security issue or an operational failure.
> >
> > Ron
> >
> > On 4/24/19 3:24 AM, Erik Weber wrote:
> > > 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.
> > >
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

RE: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Paul Angus <pa...@shapeblue.com>.
+1 (Binding)

paul.angus@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-----Original Message-----
From: Anurag Awasthi <An...@shapeblue.com> 
Sent: 21 May 2019 10:55
To: users@cloudstack.apache.org; dev <de...@cloudstack.apache.org>
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

________________________________
From: Dag Sonstebo <Da...@shapeblue.com>
Sent: Tuesday, May 21, 2019 3:22 PM
To: users@cloudstack.apache.org; dev
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 21/05/2019, 10:40, "Rohit Yadav" <ro...@shapeblue.com> wrote:

    All,


    Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.


    Moving forward I put forth the following for voting:


    - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them

    - Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards

    - After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch


    [ ] +1 approve
    [ ] +0 no opinion
    [ ] -1 disapprove (and reason why)


    ** PMCs kindly add binding to your votes, thanks.


    Thanks.



    Regards,

    Rohit Yadav

    Software Architect, ShapeBlue

    https://www.shapeblue.com


    ________________________________
    From: Erik Weber <te...@gmail.com>
    Sent: Wednesday, April 24, 2019 19:32
    To: dev
    Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

    CentOS7 was released 5 years ago, upgrading is long overdue anyway.
    Realistically the next CloudStack release won't be out the door for
    another ~4-6 months either.

    --
    Erik

    On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
    <rw...@artifact-software.com> wrote:
    >
    > According to https://en.wikipedia.org/wiki/CentOS
    >
    > CentOS 6 EOL is 2020
    > CentOS 7 EOL is 2024
    >
    >
    > +1 for removing support for CentOS 6.
    >
    > As Erik pointed out the sites running CentOS6 will have to move soon in
    > any event and it is probably better to do it now when there is still a
    > lot of current expertise and information available about how to do it
    > and how to make any changes to applications.
    >
    > Upgrading in a project that is under your control is usually easier than
    > one forced on you by a security issue or an operational failure.
    >
    > Ron
    >
    > On 4/24/19 3:24 AM, Erik Weber wrote:
    > > 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.
    > >

    rohit.yadav@shapeblue.com
    www.shapeblue.com<http://www.shapeblue.com>
    Amadeus House, Floral Street, London  WC2E 9DPUK
    @shapeblue






Dag.Sonstebo@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue




Anurag.Awasthi@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
  
 


RE: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Paul Angus <pa...@shapeblue.com>.
+1 (Binding)

paul.angus@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-----Original Message-----
From: Anurag Awasthi <An...@shapeblue.com> 
Sent: 21 May 2019 10:55
To: users@cloudstack.apache.org; dev <de...@cloudstack.apache.org>
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

________________________________
From: Dag Sonstebo <Da...@shapeblue.com>
Sent: Tuesday, May 21, 2019 3:22 PM
To: users@cloudstack.apache.org; dev
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 21/05/2019, 10:40, "Rohit Yadav" <ro...@shapeblue.com> wrote:

    All,


    Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.


    Moving forward I put forth the following for voting:


    - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them

    - Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards

    - After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch


    [ ] +1 approve
    [ ] +0 no opinion
    [ ] -1 disapprove (and reason why)


    ** PMCs kindly add binding to your votes, thanks.


    Thanks.



    Regards,

    Rohit Yadav

    Software Architect, ShapeBlue

    https://www.shapeblue.com


    ________________________________
    From: Erik Weber <te...@gmail.com>
    Sent: Wednesday, April 24, 2019 19:32
    To: dev
    Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

    CentOS7 was released 5 years ago, upgrading is long overdue anyway.
    Realistically the next CloudStack release won't be out the door for
    another ~4-6 months either.

    --
    Erik

    On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
    <rw...@artifact-software.com> wrote:
    >
    > According to https://en.wikipedia.org/wiki/CentOS
    >
    > CentOS 6 EOL is 2020
    > CentOS 7 EOL is 2024
    >
    >
    > +1 for removing support for CentOS 6.
    >
    > As Erik pointed out the sites running CentOS6 will have to move soon in
    > any event and it is probably better to do it now when there is still a
    > lot of current expertise and information available about how to do it
    > and how to make any changes to applications.
    >
    > Upgrading in a project that is under your control is usually easier than
    > one forced on you by a security issue or an operational failure.
    >
    > Ron
    >
    > On 4/24/19 3:24 AM, Erik Weber wrote:
    > > 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.
    > >

    rohit.yadav@shapeblue.com
    www.shapeblue.com<http://www.shapeblue.com>
    Amadeus House, Floral Street, London  WC2E 9DPUK
    @shapeblue






Dag.Sonstebo@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue




Anurag.Awasthi@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
  
 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Anurag Awasthi <An...@shapeblue.com>.
+1

________________________________
From: Dag Sonstebo <Da...@shapeblue.com>
Sent: Tuesday, May 21, 2019 3:22 PM
To: users@cloudstack.apache.org; dev
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 21/05/2019, 10:40, "Rohit Yadav" <ro...@shapeblue.com> wrote:

    All,


    Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.


    Moving forward I put forth the following for voting:


    - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them

    - Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards

    - After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch


    [ ] +1 approve
    [ ] +0 no opinion
    [ ] -1 disapprove (and reason why)


    ** PMCs kindly add binding to your votes, thanks.


    Thanks.



    Regards,

    Rohit Yadav

    Software Architect, ShapeBlue

    https://www.shapeblue.com


    ________________________________
    From: Erik Weber <te...@gmail.com>
    Sent: Wednesday, April 24, 2019 19:32
    To: dev
    Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

    CentOS7 was released 5 years ago, upgrading is long overdue anyway.
    Realistically the next CloudStack release won't be out the door for
    another ~4-6 months either.

    --
    Erik

    On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
    <rw...@artifact-software.com> wrote:
    >
    > According to https://en.wikipedia.org/wiki/CentOS
    >
    > CentOS 6 EOL is 2020
    > CentOS 7 EOL is 2024
    >
    >
    > +1 for removing support for CentOS 6.
    >
    > As Erik pointed out the sites running CentOS6 will have to move soon in
    > any event and it is probably better to do it now when there is still a
    > lot of current expertise and information available about how to do it
    > and how to make any changes to applications.
    >
    > Upgrading in a project that is under your control is usually easier than
    > one forced on you by a security issue or an operational failure.
    >
    > Ron
    >
    > On 4/24/19 3:24 AM, Erik Weber wrote:
    > > 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.
    > >

    rohit.yadav@shapeblue.com
    www.shapeblue.com<http://www.shapeblue.com>
    Amadeus House, Floral Street, London  WC2E 9DPUK
    @shapeblue






Dag.Sonstebo@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




Anurag.Awasthi@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Anurag Awasthi <An...@shapeblue.com>.
+1

________________________________
From: Dag Sonstebo <Da...@shapeblue.com>
Sent: Tuesday, May 21, 2019 3:22 PM
To: users@cloudstack.apache.org; dev
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 21/05/2019, 10:40, "Rohit Yadav" <ro...@shapeblue.com> wrote:

    All,


    Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.


    Moving forward I put forth the following for voting:


    - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them

    - Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards

    - After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch


    [ ] +1 approve
    [ ] +0 no opinion
    [ ] -1 disapprove (and reason why)


    ** PMCs kindly add binding to your votes, thanks.


    Thanks.



    Regards,

    Rohit Yadav

    Software Architect, ShapeBlue

    https://www.shapeblue.com


    ________________________________
    From: Erik Weber <te...@gmail.com>
    Sent: Wednesday, April 24, 2019 19:32
    To: dev
    Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

    CentOS7 was released 5 years ago, upgrading is long overdue anyway.
    Realistically the next CloudStack release won't be out the door for
    another ~4-6 months either.

    --
    Erik

    On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
    <rw...@artifact-software.com> wrote:
    >
    > According to https://en.wikipedia.org/wiki/CentOS
    >
    > CentOS 6 EOL is 2020
    > CentOS 7 EOL is 2024
    >
    >
    > +1 for removing support for CentOS 6.
    >
    > As Erik pointed out the sites running CentOS6 will have to move soon in
    > any event and it is probably better to do it now when there is still a
    > lot of current expertise and information available about how to do it
    > and how to make any changes to applications.
    >
    > Upgrading in a project that is under your control is usually easier than
    > one forced on you by a security issue or an operational failure.
    >
    > Ron
    >
    > On 4/24/19 3:24 AM, Erik Weber wrote:
    > > 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.
    > >

    rohit.yadav@shapeblue.com
    www.shapeblue.com<http://www.shapeblue.com>
    Amadeus House, Floral Street, London  WC2E 9DPUK
    @shapeblue






Dag.Sonstebo@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




Anurag.Awasthi@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Dag Sonstebo <Da...@shapeblue.com>.
+1 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 21/05/2019, 10:40, "Rohit Yadav" <ro...@shapeblue.com> wrote:

    All,
    
    
    Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.
    
    
    Moving forward I put forth the following for voting:
    
    
    - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them
    
    - Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards
    
    - After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch
    
    
    [ ] +1 approve
    [ ] +0 no opinion
    [ ] -1 disapprove (and reason why)
    
    
    ** PMCs kindly add binding to your votes, thanks.
    
    
    Thanks.
    
    
    
    Regards,
    
    Rohit Yadav
    
    Software Architect, ShapeBlue
    
    https://www.shapeblue.com
    
    
    ________________________________
    From: Erik Weber <te...@gmail.com>
    Sent: Wednesday, April 24, 2019 19:32
    To: dev
    Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
    
    CentOS7 was released 5 years ago, upgrading is long overdue anyway.
    Realistically the next CloudStack release won't be out the door for
    another ~4-6 months either.
    
    --
    Erik
    
    On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
    <rw...@artifact-software.com> wrote:
    >
    > According to https://en.wikipedia.org/wiki/CentOS
    >
    > CentOS 6 EOL is 2020
    > CentOS 7 EOL is 2024
    >
    >
    > +1 for removing support for CentOS 6.
    >
    > As Erik pointed out the sites running CentOS6 will have to move soon in
    > any event and it is probably better to do it now when there is still a
    > lot of current expertise and information available about how to do it
    > and how to make any changes to applications.
    >
    > Upgrading in a project that is under your control is usually easier than
    > one forced on you by a security issue or an operational failure.
    >
    > Ron
    >
    > On 4/24/19 3:24 AM, Erik Weber wrote:
    > > 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.
    > >
    
    rohit.yadav@shapeblue.com 
    www.shapeblue.com
    Amadeus House, Floral Street, London  WC2E 9DPUK
    @shapeblue
      
     
    
    


Dag.Sonstebo@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Dag Sonstebo <Da...@shapeblue.com>.
+1 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 21/05/2019, 10:40, "Rohit Yadav" <ro...@shapeblue.com> wrote:

    All,
    
    
    Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.
    
    
    Moving forward I put forth the following for voting:
    
    
    - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them
    
    - Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards
    
    - After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch
    
    
    [ ] +1 approve
    [ ] +0 no opinion
    [ ] -1 disapprove (and reason why)
    
    
    ** PMCs kindly add binding to your votes, thanks.
    
    
    Thanks.
    
    
    
    Regards,
    
    Rohit Yadav
    
    Software Architect, ShapeBlue
    
    https://www.shapeblue.com
    
    
    ________________________________
    From: Erik Weber <te...@gmail.com>
    Sent: Wednesday, April 24, 2019 19:32
    To: dev
    Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
    
    CentOS7 was released 5 years ago, upgrading is long overdue anyway.
    Realistically the next CloudStack release won't be out the door for
    another ~4-6 months either.
    
    --
    Erik
    
    On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
    <rw...@artifact-software.com> wrote:
    >
    > According to https://en.wikipedia.org/wiki/CentOS
    >
    > CentOS 6 EOL is 2020
    > CentOS 7 EOL is 2024
    >
    >
    > +1 for removing support for CentOS 6.
    >
    > As Erik pointed out the sites running CentOS6 will have to move soon in
    > any event and it is probably better to do it now when there is still a
    > lot of current expertise and information available about how to do it
    > and how to make any changes to applications.
    >
    > Upgrading in a project that is under your control is usually easier than
    > one forced on you by a security issue or an operational failure.
    >
    > Ron
    >
    > On 4/24/19 3:24 AM, Erik Weber wrote:
    > > 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.
    > >
    
    rohit.yadav@shapeblue.com 
    www.shapeblue.com
    Amadeus House, Floral Street, London  WC2E 9DPUK
    @shapeblue
      
     
    
    


Dag.Sonstebo@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Ron Wheeler <rw...@artifact-software.com>.
+1

On 2019-05-21 8:25 a.m., Pierre-Luc Dion wrote:
> +1
>
> On Tue, May 21, 2019 at 8:18 AM Wido den Hollander <wi...@widodh.nl> wrote:
>
>> +1
>>
>> On 5/21/19 11:40 AM, Rohit Yadav wrote:
>>> All,
>>>
>>>
>>> Thank you for your feedback and discussions. From what we've discussed
>> so far, we've lazy consensus that nobody wants to use el6 or are limited to
>> upgrade to el7/el8 due to potential risks.
>>>
>>> Moving forward I put forth the following for voting:
>>>
>>>
>>> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last
>> ones to support el6 packaging both for the management server and KVM host,
>> but users are discouraged from using them
>>> - Next major release (4.13.0.0) will document in its release notes that
>> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14
>> and onwards
>>> - After 4.13.0.0 is released, we will remove el6 related specs,
>> packaging scripts etc. from the codebase in the master branch
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>>
>>> ** PMCs kindly add binding to your votes, thanks.
>>>
>>>
>>> Thanks.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Rohit Yadav
>>>
>>> Software Architect, ShapeBlue
>>>
>>> https://www.shapeblue.com
>>>
>>>
>>> ________________________________
>>> From: Erik Weber <te...@gmail.com>
>>> Sent: Wednesday, April 24, 2019 19:32
>>> To: dev
>>> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
>>>
>>> CentOS7 was released 5 years ago, upgrading is long overdue anyway.
>>> Realistically the next CloudStack release won't be out the door for
>>> another ~4-6 months either.
>>>
>>> --
>>> Erik
>>>
>>> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
>>> <rw...@artifact-software.com> wrote:
>>>> According to https://en.wikipedia.org/wiki/CentOS
>>>>
>>>> CentOS 6 EOL is 2020
>>>> CentOS 7 EOL is 2024
>>>>
>>>>
>>>> +1 for removing support for CentOS 6.
>>>>
>>>> As Erik pointed out the sites running CentOS6 will have to move soon in
>>>> any event and it is probably better to do it now when there is still a
>>>> lot of current expertise and information available about how to do it
>>>> and how to make any changes to applications.
>>>>
>>>> Upgrading in a project that is under your control is usually easier than
>>>> one forced on you by a security issue or an operational failure.
>>>>
>>>> Ron
>>>>
>>>> On 4/24/19 3:24 AM, Erik Weber wrote:
>>>>> 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.
>>>>>
>>> rohit.yadav@shapeblue.com
>>> www.shapeblue.com
>>> Amadeus House, Floral Street, London  WC2E 9DPUK
>>> @shapeblue
>>>
>>>
>>>
>>>
-- 
Ron Wheeler
Artifact Software
438-345-3369
rwheeler@artifact-software.com


Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Pierre-Luc Dion <pd...@cloud.ca>.
+1

On Tue, May 21, 2019 at 8:18 AM Wido den Hollander <wi...@widodh.nl> wrote:

> +1
>
> On 5/21/19 11:40 AM, Rohit Yadav wrote:
> > All,
> >
> >
> > Thank you for your feedback and discussions. From what we've discussed
> so far, we've lazy consensus that nobody wants to use el6 or are limited to
> upgrade to el7/el8 due to potential risks.
> >
> >
> > Moving forward I put forth the following for voting:
> >
> >
> > - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last
> ones to support el6 packaging both for the management server and KVM host,
> but users are discouraged from using them
> >
> > - Next major release (4.13.0.0) will document in its release notes that
> we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14
> and onwards
> >
> > - After 4.13.0.0 is released, we will remove el6 related specs,
> packaging scripts etc. from the codebase in the master branch
> >
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> >
> > ** PMCs kindly add binding to your votes, thanks.
> >
> >
> > Thanks.
> >
> >
> >
> > Regards,
> >
> > Rohit Yadav
> >
> > Software Architect, ShapeBlue
> >
> > https://www.shapeblue.com
> >
> >
> > ________________________________
> > From: Erik Weber <te...@gmail.com>
> > Sent: Wednesday, April 24, 2019 19:32
> > To: dev
> > Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
> >
> > CentOS7 was released 5 years ago, upgrading is long overdue anyway.
> > Realistically the next CloudStack release won't be out the door for
> > another ~4-6 months either.
> >
> > --
> > Erik
> >
> > On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
> > <rw...@artifact-software.com> wrote:
> >>
> >> According to https://en.wikipedia.org/wiki/CentOS
> >>
> >> CentOS 6 EOL is 2020
> >> CentOS 7 EOL is 2024
> >>
> >>
> >> +1 for removing support for CentOS 6.
> >>
> >> As Erik pointed out the sites running CentOS6 will have to move soon in
> >> any event and it is probably better to do it now when there is still a
> >> lot of current expertise and information available about how to do it
> >> and how to make any changes to applications.
> >>
> >> Upgrading in a project that is under your control is usually easier than
> >> one forced on you by a security issue or an operational failure.
> >>
> >> Ron
> >>
> >> On 4/24/19 3:24 AM, Erik Weber wrote:
> >>> 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.
> >>>
> >
> > rohit.yadav@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>

Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Wido den Hollander <wi...@widodh.nl>.
+1

On 5/21/19 11:40 AM, Rohit Yadav wrote:
> All,
> 
> 
> Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.
> 
> 
> Moving forward I put forth the following for voting:
> 
> 
> - Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them
> 
> - Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards
> 
> - After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch
> 
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> 
> ** PMCs kindly add binding to your votes, thanks.
> 
> 
> Thanks.
> 
> 
> 
> Regards,
> 
> Rohit Yadav
> 
> Software Architect, ShapeBlue
> 
> https://www.shapeblue.com
> 
> 
> ________________________________
> From: Erik Weber <te...@gmail.com>
> Sent: Wednesday, April 24, 2019 19:32
> To: dev
> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
> 
> CentOS7 was released 5 years ago, upgrading is long overdue anyway.
> Realistically the next CloudStack release won't be out the door for
> another ~4-6 months either.
> 
> --
> Erik
> 
> On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
> <rw...@artifact-software.com> wrote:
>>
>> According to https://en.wikipedia.org/wiki/CentOS
>>
>> CentOS 6 EOL is 2020
>> CentOS 7 EOL is 2024
>>
>>
>> +1 for removing support for CentOS 6.
>>
>> As Erik pointed out the sites running CentOS6 will have to move soon in
>> any event and it is probably better to do it now when there is still a
>> lot of current expertise and information available about how to do it
>> and how to make any changes to applications.
>>
>> Upgrading in a project that is under your control is usually easier than
>> one forced on you by a security issue or an operational failure.
>>
>> Ron
>>
>> On 4/24/19 3:24 AM, Erik Weber wrote:
>>> 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.
>>>
> 
> rohit.yadav@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>   
>  
> 
> 

[VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Rohit Yadav <ro...@shapeblue.com>.
All,


Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.


Moving forward I put forth the following for voting:


- Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them

- Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards

- After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch


[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


** PMCs kindly add binding to your votes, thanks.


Thanks.



Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


________________________________
From: Erik Weber <te...@gmail.com>
Sent: Wednesday, April 24, 2019 19:32
To: dev
Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

CentOS7 was released 5 years ago, upgrading is long overdue anyway.
Realistically the next CloudStack release won't be out the door for
another ~4-6 months either.

--
Erik

On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
<rw...@artifact-software.com> wrote:
>
> According to https://en.wikipedia.org/wiki/CentOS
>
> CentOS 6 EOL is 2020
> CentOS 7 EOL is 2024
>
>
> +1 for removing support for CentOS 6.
>
> As Erik pointed out the sites running CentOS6 will have to move soon in
> any event and it is probably better to do it now when there is still a
> lot of current expertise and information available about how to do it
> and how to make any changes to applications.
>
> Upgrading in a project that is under your control is usually easier than
> one forced on you by a security issue or an operational failure.
>
> Ron
>
> On 4/24/19 3:24 AM, Erik Weber wrote:
> > 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.
> >

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


[VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

Posted by Rohit Yadav <ro...@shapeblue.com>.
All,


Thank you for your feedback and discussions. From what we've discussed so far, we've lazy consensus that nobody wants to use el6 or are limited to upgrade to el7/el8 due to potential risks.


Moving forward I put forth the following for voting:


- Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones to support el6 packaging both for the management server and KVM host, but users are discouraged from using them

- Next major release (4.13.0.0) will document in its release notes that we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and onwards

- After 4.13.0.0 is released, we will remove el6 related specs, packaging scripts etc. from the codebase in the master branch


[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


** PMCs kindly add binding to your votes, thanks.


Thanks.



Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


________________________________
From: Erik Weber <te...@gmail.com>
Sent: Wednesday, April 24, 2019 19:32
To: dev
Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

CentOS7 was released 5 years ago, upgrading is long overdue anyway.
Realistically the next CloudStack release won't be out the door for
another ~4-6 months either.

--
Erik

On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
<rw...@artifact-software.com> wrote:
>
> According to https://en.wikipedia.org/wiki/CentOS
>
> CentOS 6 EOL is 2020
> CentOS 7 EOL is 2024
>
>
> +1 for removing support for CentOS 6.
>
> As Erik pointed out the sites running CentOS6 will have to move soon in
> any event and it is probably better to do it now when there is still a
> lot of current expertise and information available about how to do it
> and how to make any changes to applications.
>
> Upgrading in a project that is under your control is usually easier than
> one forced on you by a security issue or an operational failure.
>
> Ron
>
> On 4/24/19 3:24 AM, Erik Weber wrote:
> > 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.
> >

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Erik Weber <te...@gmail.com>.
CentOS7 was released 5 years ago, upgrading is long overdue anyway.
Realistically the next CloudStack release won't be out the door for
another ~4-6 months either.

-- 
Erik

On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
<rw...@artifact-software.com> wrote:
>
> According to https://en.wikipedia.org/wiki/CentOS
>
> CentOS 6 EOL is 2020
> CentOS 7 EOL is 2024
>
>
> +1 for removing support for CentOS 6.
>
> As Erik pointed out the sites running CentOS6 will have to move soon in
> any event and it is probably better to do it now when there is still a
> lot of current expertise and information available about how to do it
> and how to make any changes to applications.
>
> Upgrading in a project that is under your control is usually easier than
> one forced on you by a security issue or an operational failure.
>
> Ron
>
> On 4/24/19 3:24 AM, Erik Weber wrote:
> > 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.
> >

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Ron Wheeler <rw...@artifact-software.com>.
According to https://en.wikipedia.org/wiki/CentOS

CentOS 6 EOL is 2020
CentOS 7 EOL is 2024


+1 for removing support for CentOS 6.

As Erik pointed out the sites running CentOS6 will have to move soon in 
any event and it is probably better to do it now when there is still a 
lot of current expertise and information available about how to do it 
and how to make any changes to applications.

Upgrading in a project that is under your control is usually easier than 
one forced on you by a security issue or an operational failure.

Ron

On 4/24/19 3:24 AM, Erik Weber wrote:
> 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.
>

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Erik Weber <te...@gmail.com>.
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....@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....@uplink.ua>
> > Sent: Friday, April 19, 2019 8:01:20 PM
> > To: users@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.yadav@shapeblue.com
> > > www.shapeblue.com<http://www.shapeblue.com>
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> >
> > --
> > V.Melnik
> >
> > rohit.yadav@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
>
> --
> V.Melnik

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Vladimir Melnik <v....@uplink.ua>.
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....@uplink.ua>
> Sent: Friday, April 19, 2019 8:01:20 PM
> To: users@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.yadav@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> 
> --
> V.Melnik
> 
> rohit.yadav@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>   
>  
> 

-- 
V.Melnik

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Vladimir Melnik <v....@uplink.ua>.
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....@uplink.ua>
> Sent: Friday, April 19, 2019 8:01:20 PM
> To: users@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.yadav@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> 
> --
> V.Melnik
> 
> rohit.yadav@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>   
>  
> 

-- 
V.Melnik

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rohit Yadav <ro...@shapeblue.com>.
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....@uplink.ua>
Sent: Friday, April 19, 2019 8:01:20 PM
To: users@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.yadav@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>

--
V.Melnik

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rafael Weingärtner <ra...@gmail.com>.
Agree to disagree, but C'est la vie ;)

On Sun, Apr 21, 2019 at 5:14 PM Rohit Yadav <ro...@shapeblue.com>
wrote:

> Rafael - you're digressing from the discussion. You're right with the
> semantic versioning definition but we don't really follow the referenced
> wiki/document by the word.
>
>
> The wiki has gone through several changes where they were not all agreed
> and voted on. Per the original intent and our understanding, the versioning
> scheme (since the first 4.0.0 release) we follow is "4.x.y.z" where a
> change in x makes it a major release, and when it's y is the minor release
> and z is for security release. Therefore, 4.11, 4.12, 4.13 are all major
> releases and all releases till date have been referenced, announced as such.
>
>
> The proposal of a 5.0.0 is a recent one, and has many potential ill
> effects on our community and our users, and therefore is greatly opposed.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> ________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Monday, April 22, 2019 12:50:49 AM
> To: dev
> Cc: users
> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
>
> Major? Have we discussed the 5.0.0 already?
> 4.13 is not a major release. At least, according with this page [1], 4.13
> is considered a minor one.
>
> > For those that may not be familiar with Semantic Versioning, the number
> > format is: X.Y.Z, where X is the major version, Y is the minor version, Z
> > is the patch number.
> >
>
> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
>
> On Fri, Apr 19, 2019 at 12:11 PM Andrija Panic <an...@gmail.com>
> wrote:
>
> > Hi Vladimir,
> >
> > is it possible that you upgrade management and hypervisors hosts for the
> > next major release - we are not talking removing packaging support for
> > current LTS release/updates but for the next MAJOR release.
> >
> > Upgrading management hosts is as simple as introducing additional ones
> and
> > removing old ones.
> >
> > Regards,
> > Andrija
> >
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> > On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua>
> wrote:
> >
> > > 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.yadav@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > >
> > > --
> > > V.Melnik
> > >
> >
> >
> > --
> >
> > Andrija Panić
> >
>
>
> --
> Rafael Weingärtner
>


-- 
Rafael Weingärtner

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rafael Weingärtner <ra...@gmail.com>.
Agree to disagree, but C'est la vie ;)

On Sun, Apr 21, 2019 at 5:14 PM Rohit Yadav <ro...@shapeblue.com>
wrote:

> Rafael - you're digressing from the discussion. You're right with the
> semantic versioning definition but we don't really follow the referenced
> wiki/document by the word.
>
>
> The wiki has gone through several changes where they were not all agreed
> and voted on. Per the original intent and our understanding, the versioning
> scheme (since the first 4.0.0 release) we follow is "4.x.y.z" where a
> change in x makes it a major release, and when it's y is the minor release
> and z is for security release. Therefore, 4.11, 4.12, 4.13 are all major
> releases and all releases till date have been referenced, announced as such.
>
>
> The proposal of a 5.0.0 is a recent one, and has many potential ill
> effects on our community and our users, and therefore is greatly opposed.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> ________________________________
> From: Rafael Weingärtner <ra...@gmail.com>
> Sent: Monday, April 22, 2019 12:50:49 AM
> To: dev
> Cc: users
> Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14
>
> Major? Have we discussed the 5.0.0 already?
> 4.13 is not a major release. At least, according with this page [1], 4.13
> is considered a minor one.
>
> > For those that may not be familiar with Semantic Versioning, the number
> > format is: X.Y.Z, where X is the major version, Y is the minor version, Z
> > is the patch number.
> >
>
> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
>
> On Fri, Apr 19, 2019 at 12:11 PM Andrija Panic <an...@gmail.com>
> wrote:
>
> > Hi Vladimir,
> >
> > is it possible that you upgrade management and hypervisors hosts for the
> > next major release - we are not talking removing packaging support for
> > current LTS release/updates but for the next MAJOR release.
> >
> > Upgrading management hosts is as simple as introducing additional ones
> and
> > removing old ones.
> >
> > Regards,
> > Andrija
> >
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
> > On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua>
> wrote:
> >
> > > 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.yadav@shapeblue.com
> > > > www.shapeblue.com<http://www.shapeblue.com>
> > > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > >
> > > --
> > > V.Melnik
> > >
> >
> >
> > --
> >
> > Andrija Panić
> >
>
>
> --
> Rafael Weingärtner
>


-- 
Rafael Weingärtner

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rohit Yadav <ro...@shapeblue.com>.
Rafael - you're digressing from the discussion. You're right with the semantic versioning definition but we don't really follow the referenced wiki/document by the word.


The wiki has gone through several changes where they were not all agreed and voted on. Per the original intent and our understanding, the versioning scheme (since the first 4.0.0 release) we follow is "4.x.y.z" where a change in x makes it a major release, and when it's y is the minor release and z is for security release. Therefore, 4.11, 4.12, 4.13 are all major releases and all releases till date have been referenced, announced as such.


The proposal of a 5.0.0 is a recent one, and has many potential ill effects on our community and our users, and therefore is greatly opposed.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Monday, April 22, 2019 12:50:49 AM
To: dev
Cc: users
Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Major? Have we discussed the 5.0.0 already?
4.13 is not a major release. At least, according with this page [1], 4.13
is considered a minor one.

> For those that may not be familiar with Semantic Versioning, the number
> format is: X.Y.Z, where X is the major version, Y is the minor version, Z
> is the patch number.
>

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases

On Fri, Apr 19, 2019 at 12:11 PM Andrija Panic <an...@gmail.com>
wrote:

> Hi Vladimir,
>
> is it possible that you upgrade management and hypervisors hosts for the
> next major release - we are not talking removing packaging support for
> current LTS release/updates but for the next MAJOR release.
>
> Upgrading management hosts is as simple as introducing additional ones and
> removing old ones.
>
> Regards,
> Andrija
>

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

> On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua> wrote:
>
> > 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.yadav@shapeblue.com
> > > www.shapeblue.com<http://www.shapeblue.com>
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> >
> > --
> > V.Melnik
> >
>
>
> --
>
> Andrija Panić
>


--
Rafael Weingärtner

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rohit Yadav <ro...@shapeblue.com>.
Rafael - you're digressing from the discussion. You're right with the semantic versioning definition but we don't really follow the referenced wiki/document by the word.


The wiki has gone through several changes where they were not all agreed and voted on. Per the original intent and our understanding, the versioning scheme (since the first 4.0.0 release) we follow is "4.x.y.z" where a change in x makes it a major release, and when it's y is the minor release and z is for security release. Therefore, 4.11, 4.12, 4.13 are all major releases and all releases till date have been referenced, announced as such.


The proposal of a 5.0.0 is a recent one, and has many potential ill effects on our community and our users, and therefore is greatly opposed.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

________________________________
From: Rafael Weingärtner <ra...@gmail.com>
Sent: Monday, April 22, 2019 12:50:49 AM
To: dev
Cc: users
Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Major? Have we discussed the 5.0.0 already?
4.13 is not a major release. At least, according with this page [1], 4.13
is considered a minor one.

> For those that may not be familiar with Semantic Versioning, the number
> format is: X.Y.Z, where X is the major version, Y is the minor version, Z
> is the patch number.
>

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases

On Fri, Apr 19, 2019 at 12:11 PM Andrija Panic <an...@gmail.com>
wrote:

> Hi Vladimir,
>
> is it possible that you upgrade management and hypervisors hosts for the
> next major release - we are not talking removing packaging support for
> current LTS release/updates but for the next MAJOR release.
>
> Upgrading management hosts is as simple as introducing additional ones and
> removing old ones.
>
> Regards,
> Andrija
>

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

> On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua> wrote:
>
> > 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.yadav@shapeblue.com
> > > www.shapeblue.com<http://www.shapeblue.com>
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> >
> > --
> > V.Melnik
> >
>
>
> --
>
> Andrija Panić
>


--
Rafael Weingärtner

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rafael Weingärtner <ra...@gmail.com>.
Major? Have we discussed the 5.0.0 already?
4.13 is not a major release. At least, according with this page [1], 4.13
is considered a minor one.

> For those that may not be familiar with Semantic Versioning, the number
> format is: X.Y.Z, where X is the major version, Y is the minor version, Z
> is the patch number.
>

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases

On Fri, Apr 19, 2019 at 12:11 PM Andrija Panic <an...@gmail.com>
wrote:

> Hi Vladimir,
>
> is it possible that you upgrade management and hypervisors hosts for the
> next major release - we are not talking removing packaging support for
> current LTS release/updates but for the next MAJOR release.
>
> Upgrading management hosts is as simple as introducing additional ones and
> removing old ones.
>
> Regards,
> Andrija
>
> On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua> wrote:
>
> > 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.yadav@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> >
> > --
> > V.Melnik
> >
>
>
> --
>
> Andrija Panić
>


-- 
Rafael Weingärtner

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rafael Weingärtner <ra...@gmail.com>.
Major? Have we discussed the 5.0.0 already?
4.13 is not a major release. At least, according with this page [1], 4.13
is considered a minor one.

> For those that may not be familiar with Semantic Versioning, the number
> format is: X.Y.Z, where X is the major version, Y is the minor version, Z
> is the patch number.
>

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases

On Fri, Apr 19, 2019 at 12:11 PM Andrija Panic <an...@gmail.com>
wrote:

> Hi Vladimir,
>
> is it possible that you upgrade management and hypervisors hosts for the
> next major release - we are not talking removing packaging support for
> current LTS release/updates but for the next MAJOR release.
>
> Upgrading management hosts is as simple as introducing additional ones and
> removing old ones.
>
> Regards,
> Andrija
>
> On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua> wrote:
>
> > 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.yadav@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> >
> > --
> > V.Melnik
> >
>
>
> --
>
> Andrija Panić
>


-- 
Rafael Weingärtner

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Andrija Panic <an...@gmail.com>.
Hi Vladimir,

is it possible that you upgrade management and hypervisors hosts for the
next major release - we are not talking removing packaging support for
current LTS release/updates but for the next MAJOR release.

Upgrading management hosts is as simple as introducing additional ones and
removing old ones.

Regards,
Andrija

On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua> wrote:

> 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.yadav@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
>
> --
> V.Melnik
>


-- 

Andrija Panić

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Rohit Yadav <ro...@shapeblue.com>.
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....@uplink.ua>
Sent: Friday, April 19, 2019 8:01:20 PM
To: users@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.yadav@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>

--
V.Melnik

rohit.yadav@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Andrija Panic <an...@gmail.com>.
Hi Vladimir,

is it possible that you upgrade management and hypervisors hosts for the
next major release - we are not talking removing packaging support for
current LTS release/updates but for the next MAJOR release.

Upgrading management hosts is as simple as introducing additional ones and
removing old ones.

Regards,
Andrija

On Fri, 19 Apr 2019 at 16:31, Vladimir Melnik <v....@uplink.ua> wrote:

> 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.yadav@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
>
> --
> V.Melnik
>


-- 

Andrija Panić

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Vladimir Melnik <v....@uplink.ua>.
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.yadav@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>   
>  
> 

-- 
V.Melnik

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Vladimir Melnik <v....@uplink.ua>.
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.yadav@shapeblue.com 
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>   
>  
> 

-- 
V.Melnik

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Nux! <nu...@li.nux.ro>.
+1, EL6 is in its last phase of support.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Rohit Yadav" <ro...@shapeblue.com>
> To: "dev" <de...@cloudstack.apache.org>, "users" <us...@cloudstack.apache.org>
> Sent: Monday, 15 April, 2019 08:44:58
> Subject: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

> 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.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue

Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

Posted by Wei ZHOU <us...@gmail.com>.
+1



Rohit Yadav <ro...@shapeblue.com> 于2019年4月15日周一 上午9:45写道:

> 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.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>