Once T405609 is complete we can look at this task.
Effectively there are two objectives:
- Reimage the host, moving it from the legacy row-wide vlan to the per-rack one available on the new switch
- Adjust the BGP config to peer with the switch directly, instead of with the CR routers
The real benefit of this is that the switches have a specific route for all the VIPs it announces, and thus traffic coming from our other hosts to services behind the load-balancer will take an optimal path through the network, avoiding the bottleneck of our core routers if it originates within row C or D.
Basic steps should be:
- Create puppet patch so the LVS peers with the .1 address on the new vlan (the switch itself)
- It should also create a new vlan sub-interface for the private1-d-eqiad vlan
- Kick off a reimage of the host with the --move-vlan option set
- Once the cookbook has edited the Netbox config, manually check all required vlans are still on the primary port
- If not add them back in, --move-vlan probably is not designed to deal with those
- Also add private1-c-eqiad to the list of tagged vlans on the switch port
- Merge the puppet patch while the OS is installing
- Run Homer against cr1-eqiad, cr2-eqiad and lsw1-d7-eqiad
- This removes the old CR BGP conf, and adds the required BGP config and additional vlan trunk to the switch
- When it comes back verify things look ok