From: Michael Santana <msantana@redhat.com>
To: dev@dpdk.org
Subject: OVSCI Automation Upgrade planned for Friday 9/9/22 net-virt-staff
Date: Thu, 8 Sep 2022 23:50:42 -0400 [thread overview]
Message-ID: <CABVNPRoPQ+reu+FhhOCj9yefeUoLH8JYFk8nF=Fn1wk9wHuLKw@mail.gmail.com> (raw)
Hi all,
We are planning on doing a system upgrade on our OVSCI automation
system this Friday 9/9/22.
This will affect our upstream robots (i.e. ovs, ovn, dpdk). This
affects patchwork sync and github actions sync, etc.
After the upgrade is completed the robots will be started again and
expected to work normally. Any obvious issues that appear will be
resolved on demand
The upgrade will start estimated at 9AM EST and last for the entire day
The highlights are:
* First and foremost Backup. If we run into any major roadblocks we
can always rollback
* Upgrade from rhel7.9 to rhel8.4
* After the upgrade Jenkins jobs will be enabled manually one by one
for testing and making sure they work properly
* We have done some testing with the upgrade ahead of time so we know
what to expect. However, there is still a chance of unexpected things
to happen. This is why we are enabling jobs one by one. This will
allow us to fix any issues on demand
reply other threads:[~2022-09-09 3:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABVNPRoPQ+reu+FhhOCj9yefeUoLH8JYFk8nF=Fn1wk9wHuLKw@mail.gmail.com' \
--to=msantana@redhat.com \
--cc=dev@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).