Identify type of bgp-router objects explicitly
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
Medium
|
Ignatious Johnson Christopher | |||
Trunk |
Fix Committed
|
Medium
|
Ignatious Johnson Christopher |
Bug Description
Terminology used here assumes that bug 1447273 has been addressed.
Current implementation uses the vendor field (value is "contrail") in
BgpRouterParams to identify control nodes. This is limiting when we
want to allow peering from control node in one cluster to a control
node in another cluster.
Proposal is to fix this by adding a new field called router-type to
BgpRouterParams to explicitly identify the type of bgp-router object.
There will be 3 types defined for now:
- Control Node: Control node in the local contrail cluster
- External Control Node: Control node in another contrail cluster
- Router: A regular BGP router such as MX, vMX, ASR9K
New version of UI code needs to set router-type to appropriate value as
described above when creating/editing a bgp-router. The vendor id should
be automatically set to contrail for router-type Control Node and External
Control Node. It can be configured by user for a Router.
The address family configuration for External Control Node should be same
as that for Control Nodes. IOW, the following families should be enabled
by default: route-target, inet-vpn, inet6-vpn, e-vpn and erm-vpn. There's
no change to the address families for a Router.
On a software upgrade/restart, API server will read all bgp-router objects
from the DB and set the router-type if it's not already set. If the vendor
is contrail, set router-type to Control Node, otherwise set it to Router.
description: | updated |
summary: |
- Identify bgp-router objects for in-cluster control nodes explicitly + Identify type of bgp-router objects explicitly |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
no longer affects: | juniperopenstack/r2.20 |
Schema changes https:/ /github. com/Juniper/ contrail- controller/ commit/ 3ff855b0cb72e89 0bbdb7e6f4d0fe9 0df2fb9bee