Project

General

Profile

Actions
Copy link

coordination #168898

open

coordination #168895: [saga][epic][infra] Support SUSE PRG office move while ensuring business continuity

[epic][infra] Support SUSE PRG office datacenter "PRG1" move while ensuring business continuity

Added by okurz 5 months ago. Updated 4 days ago.

Status:
New
Priority:
Normal
Assignee:
jbaier_cz
Category:
Feature requests
Target version:
QA (public) - future
Start date:
2024-10-25
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Tags:
migration, infra, prg, datacenter, move, suse, office

Subtasks 1 (0 open — 1 closed)

action #168901: Support SUSE PRG office datacenter "PRG1" move to a new location "PRG3" while ensuring business continuity - pre-planning size:MResolvedrobert.richardson2024-10-25

Actions
Actions
Copy link
 #1

Updated by okurz 5 months ago

  • Subtask #168901 added
Actions
Copy link
 #2

Updated by jbaier_cz 4 months ago

  • Assignee changed from okurz to jbaier_cz
Actions
Copy link
 #3

Updated by okurz 4 months ago

  • Subtask #154042 added
Actions
Copy link
 #4

Updated by okurz 4 months ago

  • Subtask deleted (#154042)
Actions
Copy link
 #7

Updated by okurz 2 months ago

  • Subtask #176136 added
Actions
Copy link
 #10

Updated by xlai 4 days ago

Just to ensure information synced among all stakeholders for PRG1 lab move.

As proposed in https://progress.opensuse.org/issues/168970#note-22 and also synced in qe-sync call of 20250326, for the bunch of machines here (located in PRG1 lab), which are shared by virtualization and kernel squad in openqa test, we suggest to move them in two waves:

  • wave 1(total 16):
    • briza,javor,misanthrope,altruist,witch,wizard,lipa,horror,hansolo,jarjarbinks,zoe, inara,jayne,buk,win2k19,esxi7
  • wave 2(total 10):
    • void, dub, kaylee, river,galactica, pegusus, amidala, chewbacca, yoda, darthvader
Actions
Copy link
 #11

Updated by MDoucha 4 days ago

I'll also add a comment from QE Kernel which I've already mentioned in #168970: We agree with moving the machines in two waves as proposed by @xlai above. Our only special requirement is that void must be moved outside of kernel update window. We have regular kernel updates between 8th and 20th day every month and void needs to be online for that. Please also check with Marcus Meissner that there are no irregular kernel-default updates on the way before turning void off.

Actions
Copy link

Also available in: Atom PDF