Hi TL;DR: - Provo machines can reach NUE machines via provo-gate.infra.opensuse.org - new provo-ns.infra.opensuse.org machine for DNS - all machines have external IPv6 now - updated/upgraded all machines to Leap 15.1 Long version: We have currently the following machines running in Provo: 192.168.67.1 provo-proxy (IP is on mufasa) 192.168.67.2 mufasa 192.168.67.3 provo-proxy2 (IP is on mufasa) 192.168.67.4 provo-ns (planned for external DNS) 192.168.67.5 narwal4 (static.o.o in Provo) 192.168.67.6 nala (mirrordb for download.o.o in Provo) 192.168.67.7 provo-mirror #192.168.67.8 old keyserver2 (shut down) #192.168.67.9 water2 (wiki - shut down) #192.168.67.10 riesling2 (wiki - shut down) 192.168.67.11 login3 (login service in Provo) 192.168.67.20 provo-gate (new machine, acting as gateway to NUE) 130.57.72.11 status2 (external status.o.o fallback) I setup provo-gate as gateway now (running VPN tunnel to Nuremberg via scar), which allows all Provo machines to reach machines in Nuremberg. Sadly, I did not find the time to establish the route back as well. This needs some adaptions on scar's firewall - and I need to read more about this (or better: find someone who volunteers to help) before this can go live. While I was on it, I setup an additional machine named "provo-ns", which is currently empty (Leap 15.1 admin image only) and is waiting to get an external DNS server for the opensuse.org domain. The two status.opensuse.org machines sync the database and Cachet installation files now once each day, which should allow us a smooth failover and/or fallback in case of trouble. This is documented in the Heroes-Wiki. These points are open: * roll-out DNS on provo-ns * establish the route back from Nuremberg to Provo machines ** add all nodes to Salt ** add all nodes into Monitoring ** add all nodes into Backup With kind regards, Lars -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org