When one port of a service VM is used in multiple service instances, the VRF
assign rules generated for this interface cannot identify which of those VRF
to use for the traffic. This is because VRF assign rules currently don't have
src or dst VN information. With this change, we will not create VRF assign
rules for 'book-end' interfaces, i.e., the left interface of the first instance
and right interface in the last instance in the chain. This allows us to
support this case when such a shared interface is the first or last in the
service chain.
Reviewed: https:/ /review. opencontrail. org/34156 github. com/Juniper/ contrail- controller/ commit/ 9d0ac3db175148f 7f3b36ca5a3b8d3 71edf8553c
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: master
commit 9d0ac3db175148f 7f3b36ca5a3b8d3 71edf8553c
Author: Sachin Bansal <email address hidden>
Date: Sun Jul 30 13:24:41 2017 -0700
Do not generate vrf assign rules for book-end RIs
When one port of a service VM is used in multiple service instances, the VRF
assign rules generated for this interface cannot identify which of those VRF
to use for the traffic. This is because VRF assign rules currently don't have
src or dst VN information. With this change, we will not create VRF assign
rules for 'book-end' interfaces, i.e., the left interface of the first instance
and right interface in the last instance in the chain. This allows us to
support this case when such a shared interface is the first or last in the
service chain.
Change-Id: Ibe9882fa96d427 9b67c9aea469445 c358505d957
Closes-Bug: 1661134