An instance task state does sound like a good idea to avoid this as we can't move the instance.uuid lock over to n-api to cover both the reserve and attach as it would delay the actual API response for too long IMHO.
-----
I prefer to fix the current problem in this way, which can fundamentally solve this problem.
An instance task state does sound like a good idea to avoid this as we can't move the instance.uuid lock over to n-api to cover both the reserve and attach as it would delay the actual API response for too long IMHO.
-----
I prefer to fix the current problem in this way, which can fundamentally solve this problem.
yes, we need a spec to hammer out the details.