Page MenuHomePhabricator

Remove static routes for anycast prefixes
Closed, ResolvedPublic

Description

This came up in T347054: Simplify maintenance of DNS/NTP hosts to reduce toil around reboots, reimages, and other work

I created those statics to be extra safe when initially deploying the anycast service.

but due to the nature of anycast they're even more useless than the LVS statics (T300877: Remove static routes for LVS VIPs from core routers) and bring a false sens of safety now as some are outdated.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Thanks for the task! Do we plan to consolidate https://netbox.wikimedia.org/ipam/prefixes/97/ip-addresses/? That is, if we remove the redundant backup static routes, 10.3.0.1/32 can be recdns, 10.3.0.2/32 will be syslog.anycast.wm and then 10.3.0.3/32 will be ntp.anycast.wmnet. I am asking this in the context of T347054 and the allocation of the IP for ntp.anycast.wmnet primarily.

Yeah, actually you can use 10.3.0.2/32 for NTP, I won't go through renumbering the syslog VIP.

Mentioned in SAL (#wikimedia-operations) [2023-10-04T07:19:53Z] <XioNoX> Remove static routes for anycast prefixes - T347494