Actions
action #170260
closedHelp others (or ourselves) to configure wireguard tunnels on other hosts needing wireguard to PRG2 in the NUE2 server room size:M
Status:
Rejected
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Acceptance criteria¶
- AC1: All QE hosts needing wireguard to connect to PRG2 in the NUE2 server room have WireGuard setup so they can reach the CC area as necessary
Suggestions¶
- Understand what was done as part of #169564
- Review the list of potentially applicable machines from the original planning ticket: https://racktables.nue.suse.com/index.php?andor=and&cft%5B%5D=11&cft%5B%5D=509&cfe=%7BQE+LSG%7D+and+not+%28%7BOld-Decommissioned%7D+or+%7BDecommissioned%7D+or+%7BTo+be+decommissioned%7D%29+and+not+%7BUnused%7D+and+not+%7BopenSUSE%7D+and+not+%7Bbare-metal+testing%7D&page=depot&tab=default&submit.x=17&submit.y=24
- Find groups of machines where the same applies, e.g. atomkraft+wasserstoff
- For each machine understand+ask+decide if the machine needs wireguard access to PRG2
- In the best case just point machine owners to the right instructions so act as "point of contact" rather than letting everyone run into traps and also we don't want to do all the work for others
- Consider tagging machines for which wireguard-to-CC was applied, e.g. racktables tag "wireguard-to-CC"
- Ensure machine owners are happy :)
- As necessary if specific group of machines pose special problems then clone into specific new tickets about those
- Handle masked systemd service var-lib-openqa-share.mount on unreal6
Updated by okurz 5 months ago
- Copied from action #169564: Configure wireguard tunnels on OSD production hosts needed for openQA located in the NUE2 server room size:S added
Updated by okurz 5 months ago
- Subject changed from Configure wireguard tunnels on other hosts needing wireguard to PRG2 in the NUE2 server room to Configure wireguard tunnels on other hosts needing wireguard to PRG2 in the NUE2 server room size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz about 2 months ago
- Status changed from Workable to Rejected
- Assignee set to okurz
- Target version changed from Tools - Next to Ready
- Start date deleted (
2024-11-26) - Parent task changed from #166598 to #153712
It seems with multiple alternative approaches this isn't necessary anymore
Actions