[GBP-182] A discrete RSP should be requested per scheduler per overlay destination Created: 05/Aug/15 Updated: 15/Oct/15 Resolved: 15/Oct/15 |
|
| Status: | Resolved |
| Project: | groupbasedpolicy |
| Component/s: | Integration:SFC |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Keith Burns | Assignee: | Keith Burns |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4092 |
| Priority: | High |
| Description |
|
Currently, the RSP requested uses the chain name. This should be derived from the SFP. This should be a combination of scheduler and egress classifier destination, to ensure the appropriate resources are scheduled. This may require an enhancement to the SFP/SF-SFF scheduling allocation algorithm. |
| Comments |
| Comment by Keith Burns [ 15/Oct/15 ] |
|
This is actually not required, nor is it efficient. Multiple classifiers may use the same RSP if it is more efficient. (say Shortest Path First). My adding the Src/Dest TunnelIP to the RSP, we devolve to n-squared (x2 for symmetric). |