ST: allow the same vmi to be referenced in multiple service-instances
Bug #1661134 reported by
amit surana
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.2 |
Fix Committed
|
High
|
Yuvaraja Mariappan | |||
R4.0 |
Fix Committed
|
High
|
Yuvaraja Mariappan | |||
Trunk |
Fix Committed
|
High
|
Yuvaraja Mariappan |
Bug Description
A common service-chain use case is to have hundreds of left-VNs (private VNs) connected to the same right-vn (public VN). In such cases, it would be ideal to have each of the service-instances to be able to refer to the same right-VN vmi. While this works fine for in-network-nat SIs, it is not supported if the SIs are of type in-network.
Currently, when this topology is configured, only the last/latest SI<->vmi reference is kept (the prior one(s) is/are broken).
Changed in juniperopenstack: | |
assignee: | Sachin Bansal (sbansal) → Ranjeet R (rranjeet-n) |
description: | updated |
description: | updated |
information type: | Public → Private |
tags: | added: att-aic-contrail |
information type: | Private → Public |
To post a comment you must log in.
Reviewed: https:/ /review. opencontrail. org/28637 github. org/Juniper/ contrail- controller/ commit/ 6c05344b3bd9a6b 6307520ad1f8d72 ef7c2641e2
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: master
commit 6c05344b3bd9a6b 6307520ad1f8d72 ef7c2641e2
Author: Ranjeet R <email address hidden>
Date: Thu Feb 9 13:26:41 2017 -0800
Fixes: ST: allow the same vmi to be referenced in multiple service-instances
The VirtualMachineI nterfaceST class has a singular variable
to store port_tuple. Making it an array to keep updating
if there are multiple port tuples.
Also, having multiple port tuples will work only in the case
of in-network service mode.
Also, adding a UT to check for port tuples.
Change-Id: I8f459860b06aad 63a49feaa9b4e59 b0dcfa2d86b
Closes-Bug: 1661134