[SFC-114] Operational state of RSP/SFP doesn't reflect scheduling algorithm Created: 14/Oct/15 Updated: 14/Oct/15 |
|
| Status: | Confirmed |
| Project: | sfc |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Keith Burns | Assignee: | Keith Burns |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4470 |
| Description |
|
RSP: , { "hop-number": 1, "service-index": 254, "service-function-forwarder-locator": "sfc-tun2", "service-function-name": "firewall-72", "service-function-forwarder": "SFF1" } ], SFP: , { "name": "SFCGBP-Path-RSP" } ] SFC: , { "name": "dpi-abstract1", "type": "service-function-type:dpi" } ] If a default scheduling algorithm is being used, it should be enumerated in operational state. |