From dev-return-110629-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Tue Jan 16 20:58:10 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 0B99F18065B for ; Tue, 16 Jan 2018 20:58:10 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id EFEA2160C34; Tue, 16 Jan 2018 19:58:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 40DF6160C1D for ; Tue, 16 Jan 2018 20:58:09 +0100 (CET) Received: (qmail 13293 invoked by uid 500); 16 Jan 2018 19:58:08 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 13280 invoked by uid 99); 16 Jan 2018 19:58:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jan 2018 19:58:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 581D8CEA50 for ; Tue, 16 Jan 2018 19:58:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ratGKHBSsWOS for ; Tue, 16 Jan 2018 19:58:06 +0000 (UTC) Received: from smtp.artifact-software.com (modemcable202.79-37-24.static.videotron.ca [24.37.79.202]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3B7265FBFA for ; Tue, 16 Jan 2018 19:58:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.artifact-software.com (Postfix) with ESMTP id 09B0F21C65AD for ; Tue, 16 Jan 2018 14:58:00 -0500 (EST) X-Virus-Scanned: amavisd-new at artifact-software.com Received: from smtp.artifact-software.com ([127.0.0.1]) by localhost (smtp.artifact-software.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IkRFu1tHV7EK for ; Tue, 16 Jan 2018 14:57:58 -0500 (EST) Received: from [192.168.3.196] (unknown [192.168.3.196]) by smtp.artifact-software.com (Postfix) with ESMTPSA id 186F020FD4ED for ; Tue, 16 Jan 2018 14:57:58 -0500 (EST) Reply-To: rwheeler@artifact-software.com Subject: Re: [PROPOSE] EOL for supported OSes & Hypervisors To: dev@cloudstack.apache.org References: <3C72A866-94A3-4491-A5A7-C6C051A88E95@gmail.com> From: Ron Wheeler Organization: Artifact Software Message-ID: Date: Tue, 16 Jan 2018 14:57:55 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-CA I am having a hard time imagining why a new Cloudstack user would want to use CentOS 6. I have not heard complaints from any forum about applications running on CentOS 6 that could not run on CentOS 7. It does have an impact of DevOps but even there it is pretty minor and well documented and once one gets one's head around systemctl, journalctl and firewalld, it really is a lot better As you pointed out, support for CentOS 7 is mandatory regardless of the decision on CentOS 6. It will be a big black mark against CloudStack if the current RedHat/CentOS release is not supported 2.5 years after its release. For existing Cloudstack users, is there a large risk that dropping official support for CentOS6 as a VM would result in a CentOS 6 VM not running after an upgrade to the latest Cloudstack? Is there anyone in the community that absolutely can not upgrade? Would they take over the testing of CentOS 6 if official support was dropped? Anyone using CentOS6 as a hypervisor will have to upgrade soon in any event and as you point out Cloudstack will soon be forced to move from CentOS 6 by dependencies dropping support for CentOS 6. It would seem to make sense to declare an EOL date for support for CentOS 6 as a hypervisor as soon as possible so that system administrators are put on notice. Ron On 16/01/2018 12:58 PM, Paul Angus wrote: > Hi Eric, > > This is the type of discussion that I wanted to open - the argument that I see for earlier dropping of v6 is that - Between May 2018 and q2 2020 RHEL/CentOS 6.x will only receive security and mission critical updates, meanwhile packages on which we depend or may want to utilise in the future are been deprecated or not developed for v6.x > Also the testing and development burden on the CloudStack community increases as we try to maintain backward compatibility while including new versions. > > Needing installation documentation for centos 7 is a great point, and something that we need to address regardless. > > > Does anyone else have a view, I'd really like to here from a wide range of people. > > Kind regards, > > Paul Angus > > paul.angus@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > > -----Original Message----- > From: Eric Green [mailto:eric.lee.green@gmail.com] > Sent: 12 January 2018 17:24 > To: users@cloudstack.apache.org > Cc: dev@cloudstack.apache.org > Subject: Re: [PROPOSE] EOL for supported OSes & Hypervisors > > Official EOL for Centos 6 / RHEL 6 as declared by Red Hat Software is 11/30/2020. Jumping the gun a bit there, padme. > > People on Centos 6 should certainly be working on a migration strategy right now, but the end is not here *yet*. Furthermore, the install documentation is still written for Centos 6 rather than Centos 7. That needs to be fixed before discontinuing support for Centos 6, eh? > >> On Jan 12, 2018, at 04:35, Rohit Yadav wrote: >> >> +1 I've updated the page with upcoming Ubuntu 18.04 LTS. >> >> >> After 4.11, I think 4.12 (assuming releases by mid of 2018) should remove "declared" (they might still work with 4.12+ but in docs and by project we should officially support them) support for following: >> >> >> a. Hypervisor: >> >> XenServer - 6.2, 6.5, >> >> KVM - CentOS6, RHEL6, Ubuntu12.04 (I think this is already removed, packages don't work I think?) >> >> vSphere/Vmware - 4.x, 5.0, 5.1, 5.5 >> >> >> b. Remove packaging for CentOS6.x, RHEL 6.x (the el6 packages), and Ubuntu 12.04 (any non-systemd debian distro). >> >> >> Thoughts, comments? >> -- Ron Wheeler President Artifact Software Inc email: rwheeler@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102