From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0DBA8A0093 for ; Thu, 9 Dec 2021 15:33:46 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D32774014F; Thu, 9 Dec 2021 15:33:44 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 81A9D40041 for ; Thu, 9 Dec 2021 15:33:43 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1639060422; 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: in-reply-to:in-reply-to:references:references; bh=2NXdTRaeRI+qDOZr4s01eKHmWVVaIA9CD3ltNtEn7L0=; b=ifQDdWgesAFF1DcFmWPlT7CfNzmgqcFgRqSuh5lwzaPDgSHOlz6j4UZBZ7ORYYTBEXdYT4 Hpqlakj/ne96NPsWQdkJwm/QGXc5CKzFEhNyYk4bnx4/SDXZ7a+HIeoM3aQWZ3bhUYNbAD tKGrSUnyGLWtzyZHZFaCMaGEAQbjPR8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-338-qgZBo9N_M0q5hVkkiD8zFg-1; Thu, 09 Dec 2021 09:33:39 -0500 X-MC-Unique: qgZBo9N_M0q5hVkkiD8zFg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C24CD1932480; Thu, 9 Dec 2021 14:33:38 +0000 (UTC) Received: from RHTPC1VM0NT (unknown [10.22.35.76]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CDE7719C59; Thu, 9 Dec 2021 14:33:37 +0000 (UTC) From: Aaron Conole To: Lincoln Lavoie Cc: ci@dpdk.org Subject: Re: UNH CI is offline References: Date: Thu, 09 Dec 2021 09:33:36 -0500 In-Reply-To: (Lincoln Lavoie's message of "Wed, 8 Dec 2021 17:09:43 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Lincoln Lavoie writes: > Hello All, > > We have completed some first steps for the major update around Jenkins. > The host's operating system has been upgraded to the latest version to pull > in security patches, etc. Jenkins itself has also been upgraded, but is > not yet to its final desired version. We have to update > incrementally between LTS versions, to allow Jenkins to migrate > configurations, plugins, and job data. That process takes a little bit to > complete each time, while it processes its data and the job history. Makes sense, and I expected it wouldn't be a simple 5 minute process. > The system is online now, and we are going to let it catch up on missed > jobs overnight. We will be keeping a close eye on the output, but things > look stable and correct. We don't expect Jenkins to change the actual > tests, since it just runs tests and collects results. There will be some > additional downtime, while we continue upgrading versions this week and > early next week. If you notice anything that looks incorrect or strange, > please let us know. Thanks. I think right now the contribution rate is rather slow (just because of real-life timing), so I imagine it won't be difficult to catch up. > That does raise a question on storage of historical results (i.e. the > results tar balls) and how long we need to keep those available. The > results (i.e. pass / fail indication) would live on in the dashboard and > database, but the actual results archives (tar balls) are stored in Jenkins > as a job. Would limiting that storage to 4 or 6 months be acceptable to > the community? This will reduce the future issues of upgrades and > migration, in terms of processing time required by Jenkins. A test could > always be rerun, if we needed to recreate an older set of logs/results. > I'll add this as a discussion item for the next community call. +1 - thanks. > Cheers, > Lincoln > > On Mon, Dec 6, 2021 at 1:19 PM Lincoln Lavoie wrote: > >> Hello All, >> >> As discussed at the Thursday CI meeting, UNH infrastructure is now offline >> for upgrades. This means, we will not be reporting results right now, >> patches will get tested once systems are restarted (but that will be a >> backlog process, i.e. CI will have to catch up). >> >> The dashboard and previous results will remain available. >> >> During the downtime, we can not rerun tests. >> >> We will follow up as we complete the upgrades. >> >> Cheers, >> Lincoln >> -- >> *Lincoln Lavoie* >> Principal Engineer, Broadband Technologies >> 21 Madbury Rd., Ste. 100, Durham, NH 03824 >> lylavoie@iol.unh.edu >> https://www.iol.unh.edu >> +1-603-674-2755 (m) >> >>