Implement Route Table with ip address next hop
Bug #1541087 reported by
Sachin Bansal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.21.x |
Won't Fix
|
High
|
Suresh Balineni | |||
Trunk |
Fix Committed
|
High
|
Suresh Balineni |
Bug Description
Currently, we have an implementation of route tables where each route can have a service instance as a next hop. We need to be able to specify an ip address as next hop. For this, I propose to change the next-hop-type field in RouteType to an enum with two possible values: 'service-instance' and 'ip-address'. If the field is not set, we will treat it same as 'service-instance'. If it is set to 'ip-address', the next hop must be a valid ip address. We will then create a static-route in the primary routing instance of that network with the same prefix and next hop and no route targets.
information type: | Proprietary → Public |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/16813
Submitter: Sachin Bansal (<email address hidden>)