We use multiple VRRP group IDs usually loosely (as it's a value from 0 to 255) matching the VLAN ID.
This is useful when there are different VRRP groups in the same vlan, which we don't do. Furthermore ulsfo uses a value of 1 for both v4 and v6 in all vlans.
I suggest we use 1 everywhere, and remove the Netbox custom field, to keep the config lean.
As changing it is impactful (split-brain), we should do it when the site is depooled. However there is no urgency.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Remove "old" VRRP support | operations/software/homer/deploy | master | +0 -3 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T260363 Standardize VRRP group IDs | |||
| Resolved | ayounsi | T311218 Netbox: use FHRP Groups feature | |||
| Resolved | ayounsi | T296452 Upgrade Netbox to 3.2 | |||
| Stalled | None | T234997 Make Netbox Active/Active | |||
| Resolved | ayounsi | T311385 Netbox and Redis | |||
| Stalled | None | T330084 gdnsd failures when converting services from active/passive to active/active |
Change 838171 had a related patch set uploaded (by Ayounsi; author: Ayounsi):
[operations/software/homer/deploy@master] Remove "old" VRRP support
Change 838171 merged by Ayounsi:
[operations/software/homer/deploy@master] Remove "old" VRRP support
Mentioned in SAL (#wikimedia-operations) [2023-02-20T09:06:38Z] <XioNoX> delete old group ID custom field from Netbox - https://netbox.wikimedia.org/extras/custom-fields/6/ - T260363
We're slowly moving away from VRRP. The benefits of renumbering them all is not worth the time, especially as we removed the custom field in favor or T311218: Netbox: use FHRP Groups feature.