Change Details

Labs Project Tested: it currently runs on meitnerium Site/Location: eqiad Number of systems: 1 Service: archiva Networking Requirements: meitnerium currently holds a public IP (208.80.154.18 - archiva.wikimedia.org). The idea would be to test archiva first on this new VM, and then flip the archiva.wikimedia.org domain only when ready. Would it be possible to have a internal IP first, and then only at the end move 208.80.154.18 to this new VM? Other requirements identical to meitnerium, except for the OS (since we'd like stretch). This request has been discussed in T192639. I would personally go for archiva1001 as name for the VM, but I don't have particular preferences.

Labs Project Tested: it currently runs on meitnerium Site/Location: eqiad Number of systems: 1 Service: archiva Networking Requirements: meitnerium currently holds a public IP (208.80.154.18 - archiva.wikimedia.org). The perfect scenario would be the following: the new VM comes up with another public IP, different from meitnerium's, so the upgrade procedure for the new Archiva version/host would simply be flipping the A record for archiva.wikimedia.org to the new IP. In case of issues, we could simply revert the DNS change and get back archiva on meitnerium. Eventually meitnerium and its public IP would be decommissioned/returned-to-the-free-pool. Other requirements identical to meitnerium, except for the OS (since we'd like stretch). This request has been discussed in T192639. I would personally go for archiva1001 as name for the VM, but I don't have particular preferences.

Labs Project Tested: it currently runs on meitnerium Site/Location: eqiad Number of systems: 1 Service: archiva Networking Requirements: meitnerium currently holds a public IP (208.80.154.18 - archiva.wikimedia.org). The ideaperfect scenario would be to test archiva first on this new VMhe following: the new VM comes up with another public IP, different from meitnerium's, and thenso the upgrade procedure for the new Archiva version/host would simply be flip thepping the A record for archiva.wikimedia.org domain only when readyto the new IP. Would it be possible to have a internal IP firstIn case of issues, and then only at the end move 208.80.154.18 to this new VM?we could simply revert the DNS change and get back archiva on meitnerium. Eventually meitnerium and its public IP would be decommissioned/returned-to-the-free-pool. Other requirements identical to meitnerium, except for the OS (since we'd like stretch). This request has been discussed in T192639. I would personally go for archiva1001 as name for the VM, but I don't have particular preferences.