From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sage Weil Subject: Re: Can we drop ubuntu 14.04 (trusty) for kraken and lumninous? Date: Wed, 16 Nov 2016 20:48:13 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ceph-users-bounces-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org Sender: "ceph-users" To: Yuri Weinstein Cc: Vasu Kulkarni , David Galloway , "ceph-maintainers-Qp0mS5GaXlQ@public.gmane.org" , "Cerza, Zack" , "Development, Ceph" , "ceph-users-Qp0mS5GaXlQ@public.gmane.org" List-Id: ceph-devel.vger.kernel.org On Wed, 16 Nov 2016, Yuri Weinstein wrote: > Sage, > > We had discussed xenial support in sepia today and right now jobs > asking for it from smithi and mira nodes will fail because there are > no bare-metals provisioned for it. > > The question is - how do we split nodes between 14.04, 16.04 and centos ? Yeah. I thought we'd already split the bar emetal boxes between trusty and xenial.. sorry! s > > Thx > YuriW > > On Mon, Nov 14, 2016 at 6:24 AM, Sage Weil wrote: > > On Fri, 11 Nov 2016, Sage Weil wrote: > >> Currently the distros we use for upstream testing are > >> > >> centos 7.x > >> ubuntu 16.04 (xenial) > >> ubuntu 14.04 (trusty) > >> > >> We also do some basic testing for Debian 8 and Fedora (some old version). > >> > >> Jewel was the first release that had native systemd and full xenial > >> support, so it's helpful to have both 14.04 and 16.04 supported to provide > >> an upgrade path. But I think we can safely drop 14.04 now for kraken and > >> luminous. Our options are > >> > >> 1) keep testing on xenial and trusty, and keep building packages for both > > > > Sounds like we'll keep trusty around for a while. Thanks, everyone! > > > > sage > > -- > > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > >