[TRNSPRTPCE-643] Manage 100GE service terminated on a 2.2.1 XPDR with a list of xponder Created: 09/Mar/22 Updated: 28/Mar/22 Resolved: 28/Mar/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus, Sulfur |
| Type: | Story | Priority: | High |
| Reporter: | Christophe BETOULE | Assignee: | Christophe BETOULE |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 4 weeks | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Goal : Creation/deletion of a 100GE service terminated on a 2.2.1 XPDR with a list of xponder. Right now when trying to create a 100GE service that terminates on another xponder subtree (XPDR2 as an example), the PCE does not take the correct port of the xponder in question. It always takes the first available port even if the port-name and port-device-name is explicity set in the service request of 100GE. Even then, it does not pick the right PP of the SRG connected to the chosen xponder. Acceptance criteria : Code does not bring regression and is submited for review. The associated functional test is provided to complement 2.2.1 End-to-End test suite. |