forestii IP address change planned for Ganeti migration

I will soon migrate this virtual machine to the new ganeti cluster. this will involve an IP address change which might affect the service.

Please let me know if there are any problems you can think of. in particular, do let me know if any internal (inside the server) or external (outside the server) services hardcodes the IP address of the virtual machine.

Trac:
Parent Ticket: legacy/trac#33082 (moved)

added component::applications/tor browser in Legacy / Trac owner::anarcat in Legacy / Trac parent::33082 in Legacy / Trac priority::high in Legacy / Trac resolution::fixed in Legacy / Trac severity::major in Legacy / Trac status::closed in Legacy / Trac tpa-roadmap-march in Legacy / Trac type::project in Legacy / Trac labels

A test instance has been setup. You can test the service by adding the following to your /etc/hosts:

116.202.120.185 forrestii.torproject.org
2a01:4f8:fff0:4f:266:37ff:fe7d:5d12 forrestii.torproject.org

Trac:
Status: new to needs_review

did some tests on the ganeti service, seemed to work fine, host removed from ganeti, DNS lowered, finaly phase begun.

final migration:

--- /mnt/etc/network/interfaces.bak	2020-04-03 16:52:02.280834458 +0000
+++ /mnt/etc/network/interfaces	2020-04-03 16:52:03.276826427 +0000
@@ -1,11 +1,16 @@
+# This file describes the network interfaces available on your system
+# and how to activate them. For more information, see interfaces(5).
+
+# The loopback network interface
 auto lo
 iface lo inet loopback
 
-allow-hotplug eth0
+# The primary network interface
+auto eth0
 iface eth0 inet static
-    address 138.201.212.234/28
-    gateway 138.201.212.225
+    address 116.202.120.185/27
+    gateway 116.202.120.161
 iface eth0 inet6 static
     accept_ra 0
-    address 2a01:4f8:172:39ca:0:dad3:10:1/96
-    gateway 2a01:4f8:172:39ca:0:dad3:0:1
+    address 2a01:4f8:fff0:4f:266:37ff:fe5a:20f5/64
+    gateway 2a01:4f8:fff0:4f::1
--- /mnt/etc/hosts.bak	2020-04-03 16:52:05.772806331 +0000
+++ /mnt/etc/hosts	2020-04-03 16:52:07.600791601 +0000
@@ -3,7 +3,7 @@
 ##
 
 127.0.0.1       localhost
-138.201.212.234        forrestii.torproject.org forrestii
+116.202.120.185 forrestii.torproject.org forrestii
 
 # The following lines are desirable for IPv6 capable hosts
 ::1     localhost ip6-localhost ip6-loopback
@@ -12,3 +12,4 @@
 ff02::1 ip6-allnodes
 ff02::2 ip6-allrouters
 ff02::3 ip6-allhosts
+2a01:4f8:fff0:4f:266:37ff:fe5a:20f5 forrestii.torproject.org forrestii

did the following changes as well, by hand:

• LDAP
• Nagios

no other change was required and the machine seems back online.

migration complete.

Trac:
Status: needs_review to closed
Resolution: N/A to fixed

reopening to self-assign since i did the renumbering.

Trac:
Resolution: fixed to N/A
Status: closed to reopened

Trac:
Owner: tbb-team to anarcat
Status: reopened to assigned

Trac:
Resolution: N/A to fixed
Status: assigned to closed

closed

mentioned in issue legacy/trac#33732 (moved)

mentioned in issue legacy/trac#33082 (moved)

moved from legacy/trac#33729 (moved)

added Project label and removed 1 deleted label

removed 1 deleted label