DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: Re: UNH CI is offline
Date: Wed, 8 Dec 2021 17:09:43 -0500	[thread overview]
Message-ID: <CAOE1vsNNd5bhc0frgfuwpPRu5LeaKujZoLDFproXk8CHJzvrNA@mail.gmail.com> (raw)
In-Reply-To: <CAOE1vsPTMzHwxMXOm6=X4NXVJb1ofm+mBFR+wEYgcWMhNP-qBg@mail.gmail.com>

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.

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.

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.

Cheers,
Lincoln

On Mon, Dec 6, 2021 at 1:19 PM Lincoln Lavoie <lylavoie@iol.unh.edu> 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)
> <https://www.iol.unh.edu>
>


-- 
*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)
<https://www.iol.unh.edu>

  reply	other threads:[~2021-12-08 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 18:19 Lincoln Lavoie
2021-12-08 22:09 ` Lincoln Lavoie [this message]
2021-12-09 14:33   ` Aaron Conole
2021-12-09 16:01     ` Thomas Monjalon
2021-12-13 19:59       ` Lincoln Lavoie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOE1vsNNd5bhc0frgfuwpPRu5LeaKujZoLDFproXk8CHJzvrNA@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).