Hello!

Let me know if this answers all your questions, don't hesitate to ask if not.

Wikinetwork codfw side:
AS65002
cr1-codfw IP: 208.80.153.186
cr2-codfw IP: 208.80.153.187

Will import (accept) prefixes:
- 185.15.57.0/24
- 172.16.128.0/21
(can be adjusted as you wish)

Will export a default route

WMCS codfw side:
AS64711
cloudnetX IP:
cloudnetY IP:

BFD if availlable: 3*300ms

The transition from static to BGP is impact-less and can be done anytime (with a small notice to prepare the config).
Steps are:
1/ configure BGP and verify it's behaving as expected
At this point the static routes will still have the priority
2/ Remove the static routes and VRRP/VIP config
Need BGP (and optionally BFD) ports open and listening to the routers IPs.

Cheers

On Tue, Feb 18, 2020 at 12:38 PM Arturo Borrero Gonzalez <aborrero@wikimedia.org> wrote:

Hi Arzhel,

I'm working on writing down required changes to our setup to introduce BGP
routing in CloudVPS transport network (between the Neutron virtual router and
the Core Router).

It would be great if you can write details of what you need from us, and a
recommended procedure/timeline for doing the changes.
Example of stuff I'm expecting:

* Neutron would need to use BGP protocol version X (I ignore this bit)
* We can only recv x.x.x.x ranges, and not other ranges
* we'd need to do the switch from static to BGP only on a concrete day
* You need to use AS # NNN
* Make sure protocol X is allowed in any firewalling for the session to be
correctly established (or monitoring or whatever)

My idea is to merge your ideas/requirements with what Neutron docs say. The docs
will end up here:

https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/EnhancementProposals/Network_refresh#BGP_in_the_transport_network

For now, let's assume everything will happen in codfw (in our codfw1dev deployment).

--
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation