Project

General

Profile

Actions

action #168901

open

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

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

Support SUSE PRG office datacenter "PRG1" move to a new location "PRG3" while ensuring business continuity - pre-planning size:M

Added by okurz about 2 months ago. Updated 3 days ago.

Status:
Workable
Priority:
Normal
Assignee:
Category:
Feature requests
Start date:
2024-10-25
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Vit Pelcak informed me that he is invited "to discuss requirements for server room for the new Prague office." We will support the planning process.

Vit wrote:

So far I got these requirements:
Move all the machines
Working PXE, IPMI...Move in time not colliding with the product testing/release (@Jan StehlĂ­k suggested Feb/Mar)
Move in phases so that we don't have all the machines offline at the same time

My addition: Do we actually need machines in a new office server room or just move them to PRG2e? Nobody from the QE tools team commonly visits the server rooms in neither PRG1 nor PRG2 so it wouldn't make a difference. There should be IPv6

Note: void.qam.suse.cz (aka openqa.qam.suse.cz) with its workers is currently in PRG1.

Acceptance Criteria

  • AC1: Assets of QE Tools inside PRG1 are known
  • AC2: Racktable entries for the identified assets are up-to-date
  • AC3: We know if we want/need machines in the new PRG site "PRG3"
  • AC4: For every identified asset, the future of the asset is decided (i.e. to be discarded, moved, replaced with new one)

Suggestions

  • Be aware about #170458
  • Review current state in racktables and update where there is already obvious outdated information or incomplete information, e.g. contact persons that have left the company or missing MAC addresses for machines
  • For unclear racktables entries talk to contact persons / machine owners / loaners
  • Identify groups of machines and for every identified asset decide about the future of the asset, i.e. to be discarded, moved, replaced with new one
Actions #1

Updated by okurz about 2 months ago

From Vit:

JFYI here is the document to gather our requirements for Prg server room
https://confluence.suse.com/display/~ewalker/Prague+%28in+office%29+Server+Room+requirements+for+Prague+teams

Actions #2

Updated by okurz about 1 month ago

  • Status changed from Feedback to New
  • Assignee deleted (okurz)
  • Target version changed from future to Ready
Actions #3

Updated by jbaier_cz 29 days ago

  • Assignee set to jbaier_cz

As discussed I will take care of this one.

Actions #4

Updated by jbaier_cz 24 days ago

  • Description updated (diff)

At least from what I know, this won't be an issue until next year. We should be ready nevertheless.

Actions #5

Updated by jbaier_cz 24 days ago

And just to make sure it will not fall into oblivion, void.qam.suse.cz (aka openqa.qam.suse.cz) with its workers is currently in PRG1.

Actions #6

Updated by okurz 23 days ago

  • Subject changed from Support SUSE PRG office datacenter "PRG1" move while ensuring business continuity - pre-planning to Support SUSE PRG office datacenter "PRG1" move to a new location "PRG3" while ensuring business continuity - pre-planning size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #8

Updated by jbaier_cz 21 days ago

  • Status changed from Workable to Blocked

Block this one on #170458 as that will help with AC1/AC2.

Actions #9

Updated by okurz 20 days ago

  • Description updated (diff)

Actually this shouldn't wait for #154042 which would be about a DHCP VM with unclear ownership. But this ticket here should focus on the physical machines within PRG1. With an evacuation of PRG1 possible even qanet.qa.suse.cz would be obsolete. Instead I added a relation to the sibling task #170458. @jbaier_cz the situation is unchanged, wait for the blocker you mentioned.

Actions #10

Updated by jbaier_cz 3 days ago

  • Status changed from Blocked to Workable
Actions

Also available in: Atom PDF