Enable locking of Resources in DB
Registered by
Zane Bitter
- Ensure state transitions are atomic and store the engine ID of the engine holding the lock
- Use the "UPDATE ... WHERE ..." form as discussed in http://
- This is the same concept that is behind the existing StackLock
- However probably better to make this part of the Resource table rather than use a separate table
Blueprint information
- Status:
- Complete
- Approver:
- Zane Bitter
- Priority:
- Medium
- Drafter:
- Zane Bitter
- Direction:
- Approved
- Assignee:
- Ishant Tyagi
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- 2015.1.0
- Started by
- Ishant Tyagi
- Completed by
- Angus Salkeld
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
DB changes for resource locking
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.