action #134051
closedQA (public) - coordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability
QA (public) - coordination #129280: [epic] Move from SUSE NUE1 (Maxtorhof) to new NBG Datacenters
QA (public) - 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
0%
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¶
- AC1: We can maintain CNAME entries within the .qa.suse.de domain in https://gitlab.suse.de/OPS-Service/salt/
Suggestions¶
- Follow-up with the discussion https://suse.slack.com/archives/C04MDKHQE20/p1691150107815519
- Ask Eng-Infra in Slack #dct-migration . If that yields no results then create SD ticket or push them in a corner and threaten them or whatever to provide this
- Extend our wiki with according instructions
- Take over all current entries from https://gitlab.suse.de/qa-sle/qanet-configs/ so that we are sure we can decommission qanet
- Push the Eng-Infra maintained DNS servers from DHCP+PXE on qanet
Updated by nicksinger over 1 year ago
created https://sd.suse.com/servicedesk/customer/portal/1/SD-129541 to request such service from eng-infra.
Updated by okurz over 1 year ago
- Related to action #133985: [alert] Backup VM not reachable via FQDN size:M added
Updated by okurz over 1 year ago
- Related to action #132623: Decommissioning of selected selected LSQ QE machines from NUE1-SRV2 added
Updated by okurz over 1 year 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
Updated by livdywan over 1 year ago
- Related to action #134243: fozzie not responsive via ipmi added
Updated by livdywan over 1 year ago
- Related to action #134453: backup.qam.suse.de is Failed according to netbox and not creating backups size:M added
Updated by okurz over 1 year 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.
Updated by okurz over 1 year ago
Updated by okurz about 1 year 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
Updated by dheidler about 1 year ago
- Status changed from Workable to Feedback
Updated by dheidler about 1 year ago
- Status changed from Feedback to Blocked
Blocked on MR.
Slack thread: https://suse.slack.com/archives/C029APBKLGK/p1697016522648029
Updated by livdywan about 1 year 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.
Updated by okurz about 1 year 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?
Updated by dheidler about 1 year 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.
Updated by okurz about 1 year 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
Updated by openqa_review about 1 year ago
- Due date set to 2023-11-09
Setting due date based on mean cycle time of SUSE QE Tools
Updated by dheidler about 1 year 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.
Updated by okurz about 1 year ago
- Status changed from Resolved to Workable
Nice!
Some open points:
- https://sd.suse.com/servicedesk/customer/portal/1/SD-129541 is still open, I assume we can suggest in there to close it with reference to https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4247, right?
- We still have https://gitlab.suse.de/qa-sle/qanet-configs/ and possibly some references to that. Please take a look into confluence and wiki for references and update and mark the gitlab repo as outdated
Updated by dheidler about 1 year 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).