Opened 4 months ago

Closed 3 months ago

Last modified 3 months ago

#33730 closed project (fixed)

vineale IP address change planned for Ganeti migration

Reported by: anarcat Owned by: anarcat
Priority: High Milestone:
Component: Internal Services/Service - git Version:
Severity: Major Keywords: tpa-roadmap-march
Cc: Actual Points:
Parent ID: #33082 Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (6)

comment:1 Changed 4 months ago by anarcat

Status: newneeds_review

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

116.202.120.189 vineale.torproject.org
2a01:4f8:fff0:4f:266:37ff:fe30:d3c9 vineale.torproject.org

comment:2 Changed 4 months ago by irl

Status: needs_reviewmerge_ready

Please do the thing, we will fix it after. This isn't going to have drastic denial-of-service effects on our developers if it all breaks, this is a sacrificial read-only mirror. Worst case people will look stuff up on GitHub while we fix gitweb.

comment:3 Changed 4 months ago by anarcat

Please do the thing, we will fix it after. This isn't going to have drastic denial-of-service effects on our developers if it all breaks, this is a sacrificial read-only mirror. Worst case people will look stuff up on GitHub while we fix gitweb.

Great, thanks for the update! :)

comment:4 Changed 3 months ago by anarcat

Owner: changed from tor-gitadm to anarcat
Status: merge_readyaccepted

renumbering started:

--- /mnt/etc/network/interfaces.bak	2016-08-22 13:51:35.341701767 +0000
+++ /mnt/etc/network/interfaces	2020-03-30 20:01:28.942339294 +0000
@@ -6,12 +6,11 @@
 iface lo inet loopback
 
 # The primary network interface
-allow-hotplug eth0
+auto eth0
 iface eth0 inet static
-    address 138.201.212.228/28
-    gateway 138.201.212.225
+    address 116.202.120.189/27
+    gateway 116.202.120.161
 iface eth0 inet6 static
     accept_ra 0
-    address 2a01:4f8:172:39ca:0:dad3:4:1/96
-    gateway 2a01:4f8:172:39ca:0:dad3:0:1
-
+    address 2a01:4f8:fff0:4f:266:37ff:fe0a:36e2/64
+    gateway 2a01:4f8:fff0:4f::1

comment:5 Changed 3 months ago by anarcat

Resolution: fixed
Status: acceptedclosed

host has been migrated. changes have been done on the host, LDAP, nagios and puppet, and no other required change was detected. i do not believe a notification to tor-project is necessary.

comment:6 Changed 3 months ago by anarcat

DNS fuckup: because there was no change required in the DNS records, DNS was never updated. it's unclear why.

by force-pushing to the dns/domains repository, i was able to trigger a rebuild of the zone and now the DNS is up to date. i documented this problem in #33766.

Note: See TracTickets for help on using tickets.