[TRNSPRTPCE-202] Duplication of interface creation when setting up bidirectional path Created: 21/Feb/20 Updated: 13/Sep/21 |
|
| Status: | Open |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Jonas Mårtensson | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Functional compliance to OR |
| Description |
|
When implementing a (bidirectional) service, the setupServicePath function of the DeviceRendererServiceImpl class is called two times (once per direction). Since the two directions (almost?) always go through the same nodes/ports and use the same wavelength, this results in identical interfaces always being created two times, both for Xponders and ROADMs, which seems unnecessary and inefficient. Would it be possible to set up both directions in one function and avoid the duplication? |