Opened 5 months ago

Closed 4 months ago

Last modified 4 months ago

#33447 closed task (fixed)

migrate omeiense to the ganeti cluster, triggering an IP change

Reported by: anarcat Owned by: anarcat
Priority: High Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Major Keywords: tpa-roadmap-march
Cc: Actual Points:
Parent ID: #33085 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.

thanks!

Child Tickets

Change History (5)

comment:1 Changed 5 months ago by irl

it might be worthwhile removing this host from the varnish rotation until it's in place and dns has propagated and whatever. nothing should be talking to this host by IP address, except for all the places that have IPsec config.

comment:2 Changed 4 months ago by anarcat

Keywords: tpa-roadmap-march added; tpa-roadmap-february removed
Owner: changed from tpa to anarcat
Status: newaccepted

hoping to do this this week.

comment:3 Changed 4 months ago by anarcat

host migrated, ip address changed:

--- /mnt/etc/network/interfaces.bak	2016-06-10 15:14:57.382544239 +0000
+++ /mnt/etc/network/interfaces	2020-03-12 19:25:30.423758502 +0000
@@ -6,11 +6,11 @@
 iface lo inet loopback
 
 # The primary network interface
-allow-hotplug eth0
+auto eth0
 iface eth0 inet static
-    address 78.47.38.227/28
-    gateway 78.47.38.225
+    address 116.202.120.183/27
+    gateway 116.202.120.161
 iface eth0 inet6 static
     accept_ra 0
-    address 2a01:4f8:211:6e8:0:823:3:1/96
-    gateway 2a01:4f8:211:6e8:0:823:0:1
+    address 2a01:4f8:fff0:4f:266:37ff:fe77:1ad8/64
+    gateway 2a01:4f8:fff0:4f::1

LDAP and Nagios changed, remaining:

  1. DRBD
  2. Puppet, DNS, reverse DNS
  3. retirement

comment:4 Changed 4 months ago by anarcat

Resolution: fixed
Status: acceptedclosed

the host was retired from unifolium. the only remaining match for the ip address is in the nagios check, and i think that will go away by itself after a while.

comment:5 Changed 4 months ago by anarcat

that was incorrect: a manual change was required in the nagios config, and has now been done.

Note: See TracTickets for help on using tickets.