Implement SyncPoint DB table
- Based on https:/
- Stores a record of the dependencies that have been satisfied, and the cached get_resource and get_attr data they supplied
- There's probably a better name, the implementation has changed a lot since I first wrote the code above (update the simulator to match to avoid confusion)
- Updates must be atomic, using "UPDATE ... WHERE ..." form as discussed in http://
- Probably use composite primary keys (resource_id & traversal id), so there is a predictable unique key (for fast lookup) but we can still query for e.g. all rows from a single traversal.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Zane Bitter
- Direction:
- Needs approval
- Assignee:
- Rakesh H S
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- 2015.1.0
- Started by
- Angus Salkeld
- Completed by
- Angus Salkeld
Related branches
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
convergence sync_point db
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.