Project

General

Profile

Actions

communication #109226

closed

Planned outage in Nuremberg DC

Added by mdruvietis about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2022-04-20
Due date:
% Done:

100%

Estimated time:
1.00 h

Description

Hi Team,

As discussed while a go, I finally finished bureaucracy and can replace our DMZ switches that interconnect our firewalls and bgp routers in our Nuremberg DC. As I'm replacing whole switch stack, some network outage is inevitable and basically all incoming/outgoing traffic to internet will stop. Time window for change is 1 hour, but I expect not more than 10 minute outage during this period.

Affected OpenSUSE subnets:

195.135.221.128/25

2001:67c:2178:8::/64

Time of change:

13th of April, 16:00-17:00 CEST

Please let me know if you have any concerns or want to discuss this.

Actions #1

Updated by cboltz about 2 years ago

Maintenance notice added on status.o.o (even if I'm unsure where it will be displayed).

Please make sure that the status.o.o DNS entry gets switched to status2 before starting the maintenance. Please also set the actual state of the Nuremberg datacenter to "down" when starting the maintenance, and back to green when everything is back. You can do this yourself (status.o.o account on request) or ask someone to do it for you (maybe Lars? I'll probably not be available at this time).

Actions #2

Updated by mdruvietis about 2 years ago

  • Start date changed from 2022-04-13 to 2022-04-20
Actions #3

Updated by mdruvietis about 2 years ago

Hi,

because of delayed hardware I had to postpone this for a week.

# New Time of change:

edited: 21th of April, 16:00-17:00 CEST

Actions #4

Updated by pjessen about 2 years ago

I have updated status.opensuse.org according to the changed schedule.

Actions #5

Updated by pjessen about 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Despite Christian's very useful reminder above, unfortunately I still managed to forget to change the DNS over to status2. Around 1630 I realised when I couldn't update a ticket and almost at the same time, someone asked about software.o.o on IRC. A minute later and everything was working again.

Actions

Also available in: Atom PDF