All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Michael Halstead <mhalstead@linuxfoundation.org>,
	Yocto Project Discussion <yocto@yoctoproject.org>,
	yocto-infrastructure@yoctoproject.org
Subject: Re: [yocto-infrastructure] Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z)
Date: Sat, 11 May 2019 13:59:57 -0700	[thread overview]
Message-ID: <0ac93492-e1a3-a0df-35bb-d639ed718bb3@gmail.com> (raw)
In-Reply-To: <CADfgfoZ4HF74sG1NXVOFcUQNBYWPBo8NW=K5G_7sfAiSBiDO=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]



On 5/10/19 4:21 PM, Michael Halstead wrote:
> What: 30-minute network outage to Portland-hosted services
> When: Fri, May 17, between 10PM-3AM PDT (Sat, 05:00-10:00 UTC)
> Why : Network equipment replacement by our service provider
>
> Services Impacted:  autobuilder.yoctoproject.org
> <http://autobuilder.yoctoproject.org>, downloads.yoctoproject.org
> <http://downloads.yoctoproject.org>, sstate.yoctoproject.org
> <http://sstate.yoctoproject.org>
>
> Our Portland hosting provider needs to replace some of their main 
> network equipment, which will require rerunning some cables. They are 
> asking us to prepare for up to a 30-minute network outage between the 
> hours listed above in order to complete this work.

Thanks for the heads up.

Is there a time on Sat that if things are not back to normal that we
should contact you? I hope and don't expect you to be working @ 3am.

regards,
Armin
>
> -- 
> Michael Halstead
> Linux Foundation / SysAdmin
>
>


[-- Attachment #2: Type: text/html, Size: 3086 bytes --]

  reply	other threads:[~2019-05-11 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 23:21 Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z) Michael Halstead
2019-05-11 20:59 ` akuster808 [this message]
2019-05-14 15:09   ` [yocto-infrastructure] " Michael Halstead

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=0ac93492-e1a3-a0df-35bb-d639ed718bb3@gmail.com \
    --to=akuster808@gmail.com \
    --cc=mhalstead@linuxfoundation.org \
    --cc=yocto-infrastructure@yoctoproject.org \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.