Floating IP and service chaining do not work together
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
High
|
Kumar Harsh |
Bug Description
If a VN from which a floating-ip pool is created also has one or more
service chains starting/
may not work correctly.
The problem is that the VN will have more than 1 RI and agent code
does not have sufficient information to pick the default RI/VRF for
route lookup when using the FIP. Forwarding will not work correctly
if it happens to pick one of the service RIs.
Proposal is to implement the following:
- Add property to RI in schema to indicate if it's default RI for VN
- Default value of this new property is False
- Schema transformer sets property to True for default RI
- Agent uses property to find default RI/VRF for FIP processing
- Agent ignores a FIP if there's no default RI associated with VN
Reviewed: https:/ /review. opencontrail. org/4737 github. org/Juniper/ contrail- controller/ commit/ 82ec61525ba153b 1fb4dd527fde7db 5e41ac8785
Committed: http://
Submitter: Zuul
Branch: master
commit 82ec61525ba153b 1fb4dd527fde7db 5e41ac8785
Author: Sachin Bansal <email address hidden>
Date: Tue Nov 18 16:51:52 2014 -0800
Add a new property to routing instance to indicate that it is a default routing instance for the network
Change-Id: I7f36587045c0ad 0257a8f3e63cef3 fa28775c82d
Partial-Bug: 1380750