chain instances should not span L3Ps
Bug #1436104 reported by
Ivar Lazzaro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Confirmed
|
Medium
|
Ivar Lazzaro | ||
Bug Description
When instantiating a chain, there's no restriction as far as the participating PTGs' L3Ps are concerned.
As a consequence, chain instances are created between PTGs that can't talk to each other by policy (different L3Ps).
Chain instances across L3Ps should be disallowed.
| Changed in group-based-policy: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| milestone: | none → next |
| assignee: | nobody → Ivar Lazzaro (mmaleckk) |
Revision history for this message
| Ivar Lazzaro (mmaleckk) wrote | #1 |
To post a comment you must log in.
With provider centric service chains [0], every SC only exist in the provider L3P independently from who consumes it. This issue is therefore fixed by [0]
[0] https:/