Project

General

Profile

Actions

action #134051

closed

QA - coordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability

QA - coordination #129280: [epic] Move from SUSE NUE1 (Maxtorhof) to new NBG Datacenters

QA - coordination #37910: [tools][epic] Migration of or away from qanet.qa.suse.de

Eng-Infra maintained DNS server for .qa.suse.de taking over from qanet size:M

Added by nicksinger 11 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
2023-08-09
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Motivation

We need to clear out Maxtorhof where qanet currently sits and is running bind to serve the qa.suse.de domain. We agreed that we want to keep the domain as "common name" for all qe provided services pointing to domains in different locations (e.g. s.qa.suse.de should be a CNAME for s.qe.nue2.suse.org).

In the best case eng-infra can provide us with a zone on their already existing infrastructure. Next best thing would be a VM provided by them. If all this is not possible we might need to spin up qanet2 and serve the domain from there.

Acceptance criteria

Suggestions


Related issues 4 (0 open4 closed)

Related to openQA Infrastructure - action #133985: [alert] Backup VM not reachable via FQDN size:MResolvedokurz2023-08-08

Actions
Related to QA - action #132623: Decommissioning of selected selected LSQ QE machines from NUE1-SRV2Resolvedokurz2023-07-12

Actions
Related to openQA Infrastructure - action #134243: fozzie not responsive via ipmiRejectedokurz2023-08-15

Actions
Related to openQA Infrastructure - action #134453: backup.qam.suse.de is Failed according to netbox and not creating backups size:MResolvedmkittler

Actions
Actions #1

Updated by nicksinger 11 months ago

created https://sd.suse.com/servicedesk/customer/portal/1/SD-129541 to request such service from eng-infra.

Actions #2

Updated by okurz 11 months ago

  • Related to action #133985: [alert] Backup VM not reachable via FQDN size:M added
Actions #3

Updated by okurz 11 months ago

  • Related to action #132623: Decommissioning of selected selected LSQ QE machines from NUE1-SRV2 added
Actions #5

Updated by okurz 11 months ago

  • Tags set to infra
  • Subject changed from Migrate qa.suse.de domain into eng-infra provided infrastructure to Eng-Infra maintained DNS server for .qa.suse.de taking over from qanet size:M
  • Description updated (diff)
  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version set to Ready
  • Parent task set to #130955

merged in content from #134045 , tracking https://sd.suse.com/servicedesk/customer/portal/1/SD-129541

Actions #6

Updated by livdywan 10 months ago

Actions #7

Updated by livdywan 10 months ago

  • Related to action #134453: backup.qam.suse.de is Failed according to netbox and not creating backups size:M added
Actions #8

Updated by okurz 10 months ago

No response in SD ticket, reminded in ticket

Actions #9

Updated by okurz 10 months ago

  • Parent task changed from #130955 to #37910
Actions #10

Updated by okurz 9 months ago

With mcaj+gsouza in https://meet.jit.si/suse_qa_tools now. mcaj+gsouza will ensure that they have a task to track in their backlog about this. mcaj proposed to manage the qa.suse.de domain in the same DNS server that manages oqa.prg2.suse.org and might also serve in the future QE machines in PRG2e. mcaj will create a merge request in https://gitlab.suse.de/OPS-Service/salt/ preparing according changes based on https://gitlab.suse.de/qa-sle/qanet-configs/-/blob/master/var/lib/named/master/forward/qa.suse.de and we can then extend it to our needs. ETA mid of next week.

Actions #12

Updated by okurz 9 months ago

  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)
  • Priority changed from Normal to High

After discussion with mflores if we just wait for this then we should expect late 2023-11, likely later. So better we try to understand from https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4098 and https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4099 how to serve .qa.suse.de from dns1/2.nue2.suse.org and/ro dns1/2.prg2.suse.org

Actions #13

Updated by dheidler 9 months ago

  • Assignee set to dheidler
Actions #14

Updated by dheidler 9 months ago

  • Status changed from Workable to Feedback
Actions #15

Updated by dheidler 8 months ago

  • Status changed from Feedback to Blocked
Actions #16

Updated by livdywan 8 months ago

dheidler wrote in #note-15:

Blocked on MR.
Slack thread: https://suse.slack.com/archives/C029APBKLGK/p1697016522648029

Assigned but no response. Maybe fallen under the radar, or we need to ask someone else to review? I commented in the thread.

Actions #18

Updated by okurz 8 months ago

https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4146 was replaced by https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4247 which was merged. So this should be effective now. @dheidler are you waiting for something else, maybe you know more?

Actions #19

Updated by dheidler 8 months ago

  • Status changed from Blocked to In Progress

Updating the dhcp server on qanet.
Will announce
10.160.2.88 (millikan.suse.de)
10.144.53.53 (dns1.prg2.suse.org)

10.136.53.53 -
dns1.suse.de

10.144.53.53 -
dns1.prg2.suse.org

10.136.53.54 -
dns2.suse.de

as DNS servers.

Actions #20

Updated by okurz 8 months ago

I wrote an announcement in https://suse.slack.com/archives/C02CANHLANP/p1698223169457739

@here we will now switch over the DNS for the domain qa.suse.de from the NUE based machine qanet.qa.suse.de to PRG2. Expect the DNS resolution to switch over unless you manually use qanet.qa.suse.de . Details in https://progress.opensuse.org/issues/134051

Actions #21

Updated by openqa_review 8 months ago

  • Due date set to 2023-11-09

Setting due date based on mean cycle time of SUSE QE Tools

Actions #22

Updated by dheidler 8 months ago

  • Status changed from In Progress to Resolved

I didn't find a host in qa.suse.de network where I was able to login and check that dns was set correctly.
So assuming that it is fine.
Manually updated resolv.conf on qanet.

Actions #23

Updated by okurz 8 months ago

  • Status changed from Resolved to Workable

Nice!

Some open points:

Actions #24

Updated by dheidler 8 months ago

  • Status changed from Workable to Resolved

Updated https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs#Management_of_SRV2_network_config and https://confluence.suse.com/display/qasle/Retrospected+Instance

Repo is not yet deprecated as DHCP config still applies (also this is out of scope anyway).

Actions #25

Updated by okurz 8 months ago

  • Due date deleted (2023-11-09)

Ok, tracking in #81192

Actions

Also available in: Atom PDF