From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76604 invoked by alias); 6 Feb 2020 02:16:03 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 76351 invoked by uid 89); 6 Feb 2020 02:15:57 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=H*M:3475 X-HELO: us-smtp-1.mimecast.com Received: from us-smtp-delivery-1.mimecast.com (HELO us-smtp-1.mimecast.com) (207.211.31.120) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 06 Feb 2020 02:15:55 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1580955354; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rI0DzAZTcXeMqOUbsXWB/3Mf2W2+oslI7LAeLe2d9fA=; b=ZxyhyrFjJvDzfoGDg79MS8P82redAMAmStYSWWhJTTzf8lo/na+Otf71LvrJ6vsQSioRT2 O7gNiYHx/LVpo9q32lrLyq9RIbk+6U/GKyMK2PXVEkm1LRdx1OrEuL4GJ1CIyLC58NAH9D DqqjmQG5GyBHq85d+2R9QS86IOBi/o0= Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-211-qjMXyd84P2eRfpuV7UZKzg-1; Wed, 05 Feb 2020 21:15:50 -0500 Received: by mail-qk1-f197.google.com with SMTP id s9so2597715qkg.21 for ; Wed, 05 Feb 2020 18:15:50 -0800 (PST) Return-Path: Received: from [192.168.1.4] (135-23-175-75.cpe.pppoe.ca. [135.23.175.75]) by smtp.gmail.com with ESMTPSA id p135sm760794qke.2.2020.02.05.18.15.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Feb 2020 18:15:49 -0800 (PST) Subject: Re: Choice of distribution for new sourceware.org server? To: "Frank Ch. Eigler" Cc: overseers@sourceware.org, Florian Weimer References: <74e963de-f7c8-33d0-d133-ada427c000a4@redhat.com> <20200206013050.GA16275@cgf.cx> <20200206013405.GC97355@elastic.org> <20200206020237.GD97355@elastic.org> From: Carlos O'Donell Message-ID: Date: Thu, 06 Feb 2020 02:16:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <20200206020237.GD97355@elastic.org> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-q1/txt/msg00063.txt On 2/5/20 9:02 PM, Frank Ch. Eigler wrote: > Hi - > > >>> Having to upgrade apprx. every 8 months is a PITA though, with so much >>> activity and non-distro software on the machine. >> >> Sorry, I don't follow, could you expand on this a bit? > >> How much non-distro software is there on sourceware? > > Well, quite a bit. If non-distro softare impacts our maintenance costs, should we be evaluating the list of non-distro software for value vs. cost? >> When you say "activity" do you mean that users would be impacted >> once every 8 months for a small window of downtime? > > Probably, if nothing goes wrong. And if there's an incompatible > rebase of python or php or whatever, then we (?) have to fix the > thing. There is a downside to upgrade churn, in terms of our > manpower. Best practice is to have a production and development server to avoid these kinds of problems and shake out such changes. Do we have 2 servers now? > Note that with rhel8/centos8, we'll have a competent container > platform. Heck, the new machine is big enough to carry a few VMs too, > so if some future service were to require newer rawhide-y prereqs, we > can accomomdate that even with a stable base. I agree it would be great to run containers or VMs on sourcware for specific services. In which case RHEL8 with ELS as an option is even more valuable? In summary: - Why not stick with RHEL8 to get ELS and avoid CentOS 8 early phase out. - Stick with RHEL8 as long as we can to avoid costly maintenance upgrades. - Use VMs and containers to isolate new systems to provide services that need newer userspace or kernels. Does RHEL8 seem like the better choice here with ELS? -- Cheers, Carlos.