[SFC-130] API change, we need to be able to store the SF tap port in the DPL for OPNFV SFC Created: 07/Jan/16 Updated: 19/Oct/17 Resolved: 11/Feb/16 |
|
| Status: | Resolved |
| Project: | sfc |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Brady Johnson | Assignee: | Unassigned |
| 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: | 4893 |
| Description |
|
In the context of OPNFV SFC, we need to be able to configure the tap port the SF is connected to in the SF DPL configuration. The VNF Mgr (Tacker) will know this info and can easily configure it. Currently Tacker is putting the tap port name in the SF DPL name, but there should be a dedicated field for it. I propose we augment the SF Yang model and add it. Brady |
| Comments |
| Comment by Brady Johnson [ 11/Feb/16 ] |
|
This has been fixed here: |