[TRNSPRTPCE-203] Temp service creation and provisioning Created: 21/Feb/20  Updated: 13/Sep/21

Status: Open
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug 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   

According to the OpenROADM service model whitepaper, the temp-service-create RPC "is for requesting the Open ROADM Controller or RNC to compute a service path and reserve the wavelengths assigned to the service. The temporary services will be converted to the normal services upon creation of a service request from the SDN controller using the matching Common ID.

My interpretation of the above is that a temp service should only be reserved and not actually provisioned. However, TransportPCE currently provisions all devices on the computed path for a temp service.

Also, when TransportPCE receives a service-create request with a Common ID matching an existing temp service, the temp service is not converted to a normal service but rather a new service is created (with a different wavelength, etc.)


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