@aborrero: What exactly is this stalled on, as this has no subtasks?

We need to decide where does this work fit within all the network reshuffling going on.

Task is waiting for further input and can currently not be acted on.

I'm definitely still interested in this patch stack:

• https://gerrit.wikimedia.org/r/c/operations/puppet/+/922104 (refactor virtual routes away from keepalived)
• https://gerrit.wikimedia.org/r/c/operations/puppet/+/922105 (use interface::tagged)
• https://gerrit.wikimedia.org/r/c/operations/puppet/+/922106 (move VIPs to BGP instead of keepalived)

We definitely should do this work, but I think better to not start making any changes until the current cloudlb/cloud-private work in eqiad is all complete and stable.

FWIW the cloudgw is connected to the cloud realm, just on a different vlan/subnet to the other hosts.

cmooney@cloudgw1001:~$ sudo ip vrf exec vrf-cloudgw ping -c 4 172.20.255.1
PING 172.20.255.1 (172.20.255.1) 56(84) bytes of data.
64 bytes from 172.20.255.1: icmp_seq=1 ttl=63 time=0.169 ms
64 bytes from 172.20.255.1: icmp_seq=2 ttl=63 time=0.230 ms
64 bytes from 172.20.255.1: icmp_seq=3 ttl=63 time=0.226 ms
64 bytes from 172.20.255.1: icmp_seq=4 ttl=63 time=0.186 ms

--- 172.20.255.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3063ms
rtt min/avg/max/mdev = 0.169/0.202/0.230/0.026 ms

This is currently on vlan1120 ( cloud-instance-transport1-b-eqiad) in eqiad for example.

As long as the two cloudgw's are doing VRRP over this vlan it's probably best to keep it this way rather than add cloud-private.

An improvement would be to replace the current vlan with cloud-private, and replace the VRRP VIP / HA with BGP-based announcement of the ranges we currently statically route to the VIP from the cloudsw's.

Change 922104 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):

[operations/puppet@production] cloudgw: refactor to set up routes independently from keepalived

https://gerrit.wikimedia.org/r/922104

Change 922105 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):

[operations/puppet@production] cloudgw: refactor vlan interfaces to use interface::tagged

https://gerrit.wikimedia.org/r/922105

Change 922106 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):

[operations/puppet@production] cloudgw: codfw: add cloud-private subnet support

https://gerrit.wikimedia.org/r/922106

In T338334#9207934, @cmooney wrote:

An improvement would be to replace the current vlan with cloud-private, and replace the VRRP VIP / HA with BGP-based announcement of the ranges we currently statically route to the VIP from the cloudsw's.

I'm very much interested in this. Do you think we can do this before my departure in 2 weeks?

I created in netbox:

• https://netbox.wikimedia.org/ipam/ip-addresses/14976/ 172.20.5.18/24 cloudgw2002-dev.private.codfw.wikimedia.cloud
• https://netbox.wikimedia.org/ipam/ip-addresses/14978/ 172.20.5.19/24 cloudgw2003-dev.private.codfw.wikimedia.cloud

Change 922104 merged by Arturo Borrero Gonzalez:

[operations/puppet@production] cloudgw: refactor to set up routes independently from keepalived

https://gerrit.wikimedia.org/r/922104

Change 922105 merged by Arturo Borrero Gonzalez:

[operations/puppet@production] cloudgw: refactor interfaces setting to use the base module

https://gerrit.wikimedia.org/r/922105

Change 964941 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):

[operations/puppet@production] cloudgw: add cloud-private

https://gerrit.wikimedia.org/r/964941