We are getting ready to test BGP support. For initial tests we allocated a VIP address on eqiad (10.2.2.89), I'd like to announce that VIP from lvs1013 to validate liberica BGP support.
@ayounsi, @cmooney it should be enough to add lvs1013 to the list of eqiad lvs_neighbors in homer or do we need something on top of that?
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Modify LVS_Import policy to support both Liberica and PyBal | operations/homer/public | master | +8 -2 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Vgutierrez | T332027 Replace current L4LB with with Katran-based alternative | |||
| Resolved | Vgutierrez | T375464 Test liberica BGP support |
it should be enough to add lvs1013 to the list of eqiad lvs_neighbors in homer or do we need something on top of that?
In eqiad they're still configured manually, otherwise we now just have to flip the BGP flag in Netbox : https://netbox.wikimedia.org/dcim/devices/?q=lvs&cf_bgp=True
Let me know when is a good time to configure the session.
Probably a good time to change that? I think we just need to enable the BGP flag in homer for all the current hosts (plus lvs1013 if we want), and then homer should replace the existing group with the one it built?
Change #1079244 had a related patch set uploaded (by Cathal Mooney; author: Cathal Mooney):
[operations/homer/public@master] Modify LVS_Import policy to support both Liberica and PyBal
Change #1079244 merged by jenkins-bot:
[operations/homer/public@master] Modify LVS_Import policy to support both Liberica and PyBal