[TRNSPRTPCE-413] Handling E2E service request for B100G Created: 08/Mar/21  Updated: 10/Nov/21  Resolved: 13/Sep/21

Status: Verified
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: Silicon

Type: Story Priority: High
Reporter: Balagangadhar Bathula Assignee: Balagangadhar Bathula
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: 1 week, 3 days Remaining Estimate: 1 week, 3 days
Σ Time Spent: 2 days Time Spent: Not Specified
Σ Original Estimate: 1 week, 3 days Original Estimate: 1 week, 3 days

Sub-Tasks:
Key
Summary
Type
Status
Assignee
TRNSPRTPCE-449 Changes to port mapping YANG to suppo... Sub-task Verified Balagangadhar Bathula  
Epic Link: Higher Rates

 Description   

The service request for B100G needs to be decoupled as two parts:
Assuming the port-quals are set for both client and network ports:
For Muxponder use case:
1) First create an "Infrastructure" service that would handle the line side interfaces. This creates, OTSi, OTSi-group, along with OTUC4 and ODUC4 interfaces.
2) This creates a ODU switching-pool and notifications are used to update the port-mapping.
3) Verify if the port mapping is correctly updated
4) Create a "Service" connection-type that will create 100GE OTN. This will create ODU4 client and ODU4 network and the ODU cross-connect
5) Verify the network topology data is updated with the spectrum, available bandwidth and trib-slots.



 Comments   
Comment by Balagangadhar Bathula [ 08/Mar/21 ]

orenais, svachhani, gthouenonPlease provide you thoughts on this workflow and please feel free to edit/comment the description. I tried to capture the discussion that we had in the TPCE call.

Comment by Olivier Renais [ 08/Mar/21 ]

Hello Bala. Yes, this makes sense to me! Thanks

Generated at Wed Feb 07 20:43:01 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.