|
Post by AMI_archerwen on Sept 1, 2023 11:14:36 GMT
Hi,
I see the ResourceBlock schema has a property "Reserved".
"Reserved": { "description": "An indication of whether any client has reserved the Resource Block.", "longDescription": "This property shall indicate whether any client has reserved the Resource Block. A client sets this property after the Resource Block is identified as composed. It shall provide a way for multiple clients to negotiate the ownership of the Resource Block.", "readonly": false, "type": [ "boolean", "null" ] }
As my understanding, 1. This property will change to "true" if anyone compose a system with this resource block. 2. We cannot composed a system if this property is "true" even this resource block not composed. Am I correct?
|
|
|
Post by AMI_archerwen on Sept 7, 2023 2:51:36 GMT
Hi, Is any update?
|
|
|
Post by mraineri on Sept 7, 2023 12:31:33 GMT
When we added the Compose action in the CompositionService, we tied in the "PreviewReserve" semantics to the Reserved property; when there's an outstanding CompositionReservation resource that is holding a resource block for a client, the Reserved property will be set to true. When in this state, either the CompositionReservation needs to be deleted to free the reserved resources, or the Compose action needs to be issued again with the "Apply" option to enact the reserved resources.
So, the property changes to true when the resource block is identified as part of a "PreviewReserve" request, and set to false when the CompositionReservation is applied or deleted. When in the reserved state, the resource is held and cannot be part of other composition requests.
|
|