Pluggable Distributed Synchronization
Today Ironic does database-backed locking for distributed synchronization. For example, there is a column in the node table, which a process can put its hostname in to "lock" the node so that other processes won't modify the data. If one doesn't trust database locking (deadlocks if a conductor dies), there are currently no alternatives, nor a way to implement/use alternative backends.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Kyle Stevenson
- Direction:
- Needs approval
- Assignee:
- Kyle Stevenson
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add spec for pluggable distributed synchronization
Addressed by: https:/
Add implementation of pluggable distributed sync
Gerrit topic: https:/
We're moving from using blueprints to track features to RFE bugs. I've filed one for your change (see related bugs section). Please track further work there using Closes-Bug, Partial-Bug or Related-Bug in commit messages and use this newly created RFE bug.
//vdrok 2015-12-16
