From: Raslan Darawsheh <rasland@nvidia.com>
To: rasland-staff <rasland-staff@exchange.nvidia.com>,
dpdk-team <dpdk-team@exchange.nvidia.com>,
dpdk-dev <dev@dpdk.org>
Subject: RE: Impact due to the Electricity Shutdown next week
Date: Wed, 2 Nov 2022 11:45:35 +0000 [thread overview]
Message-ID: <BYAPR12MB3078196A5F2F9EBF78588113CF399@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PH7PR12MB5973899BA545F86FBDE08B97D8399@PH7PR12MB5973.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
FYI,
This means that we’ll not have any regression tonight.
And work on features can continue only on local setups.
Kindest regards,
Raslan Darawsheh
From: Eyal Gruber <egruber@nvidia.com>
Sent: Wednesday, November 2, 2022 1:32 PM
To: yarong-org <yarong-org@exchange.nvidia.com>
Subject: RE: Impact due to the Electricity Shutdown next week
Remainder,
The cloud will be down starting today at ~15:00 until tomorrow
Thanks,
Eyal
From: Eyal Gruber
Sent: Wednesday, 26 October 2022 11:58
To: yarong-org <yarong-org@exchange.nvidia.com<mailto:yarong-org@exchange.nvidia.com>>
Subject: Impact due to the Electricity Shutdown next week
Importance: High
Hi,
Next week there will be an electricity Shutdown at Hermon Building (see attached mail)
* When:
Start time: Wednesday, November 2, 3pm, IL time (the shutdown itself starts at 4pm. Our services will go down 1 hour before)
End time: Thursday, November 3, 9am, IL time
* Impacted services:
* Regressions
* CI
* OFED builds
* Linux cloud
Please be aware that additional services which are not provided by our team might also be impacted by the shutdown.
Thanks,
Eyal
[-- Attachment #2: Type: text/html, Size: 18143 bytes --]
parent reply other threads:[~2022-11-02 11:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <PH7PR12MB5973899BA545F86FBDE08B97D8399@PH7PR12MB5973.namprd12.prod.outlook.com>]
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=BYAPR12MB3078196A5F2F9EBF78588113CF399@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dpdk-team@exchange.nvidia.com \
--cc=rasland-staff@exchange.nvidia.com \
/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).