Tracking bug for BGPaaSv2 implementation
Bug #1552952 reported by
Nischal Sheth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
Wishlist
|
Nischal Sheth |
Bug Description
BGPaaS was implemented via bug 1518047.
The initial implementation has a limitation that routes can only be
advertised from the bgpaas-client to the bgpaas-server. Assumption
is that the client has a static default route with the subnet default
gateway as the nexthop.
This bug tracks an enhancement to remove above limitation and allow
bidirectional exchange of routes between the client and server. The
server will advertise routes to the client with the bgp nexthop set
to the default gateway of the subnet to which the client belongs.
Config changes are tracked via bug 1563075.
UI changes are tracked via bug 1558168.
Changed in juniperopenstack: | |
assignee: | nobody → Nischal Sheth (nsheth) |
description: | updated |
tags: | added: bgpaas |
tags: | removed: config |
description: | updated |
To post a comment you must log in.
Summary of Design
- Add gateway address fields for v4 and v6 to BgpRouterParams
- ST populates these fields in the client bgp-router's properties
- CN parses and processes these fields
- CN makes the gateway address part of RibExportPolicy
- CN updates nexthops for exported routes based on RibExportPolicy