New POK Lab VPN Instructions
Friends, If you require access to the new lab in Poughkeepsie during the RDU move, please follow these instructions: https://wiki.sepia.ceph.com/doku.php?id=wireguard. You can ping the public key to myself or anyone on my team in Slack. We’re all educated on how to manually process these requests. Teuthology runs will be able to be scheduled on soko04.front.sepia.ceph.com. DO NOT UNDER ANY CIRCUMSTANCES RSYNC ANY DATA OVER YOUR WIREGUARD TUNNEL. There is some strange networking tomfoolery afoot that we haven’t had time to nail down yet. If one Wireguard client starts any sort of transfer over the VPN tunnel, all of the other VPN clients suffer packet loss. We may end up switching back to the old VPN method depending on what we’re able to figure out. As for DNS, we are serving both POK and RDU records via 158.69.67.47 publicly. The DNS server will be 10.20.192.11 once we no longer need the RDU records. I am still syncing the teuthology home directories over to the lab but I fear the transfer is suffering the same packet loss issue the VPN clients do. I didn’t hear from anyone on if they really needed anything synced so last call… If you need a dev box, let me know what OS you’d prefer. We are still working on the ARM64 builders. This is not the setup I wanted to have prior to the shutdown but we’ve done the best we could with the hand dealt. We appreciate everyone’s patience and understanding. -- David Galloway Ceph Engineering Labs – Infrastructure Architect david.galloway@ibm.com IBM
participants (1)
-
David Galloway