transactional task management for Folsom
Tasks in Nova such as launching instances are complicated and error prone. Currently there is no systematic, reusable way to keep track of the distributed task executions. There is also no mechanism to know which tasks are currently using what resources. Task management is implicitly assumed to be VM state management. This blueprint proposes to build a highly available service to offer first-class APIs to task and resource lock management.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- High
- Drafter:
- Yun Mao
- Direction:
- Approved
- Assignee:
- Yun Mao
- Definition:
- Approved
- Series goal:
- Accepted for folsom
- Implementation:
-
Implemented
- Milestone target:
-
2012.2
- Started by
- Yun Mao
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
I'm a little concerned about the current approach due to the goal of removing db access from the compute nodes. In fact we may not need a distributed lock if we do so. I will try to make it to the next orchestration meeting to discuss --Vish
Gerrit topic: https:/
Addressed by: https:/
cleanup power state (partially implements bp task-management)
Gerrit topic: https:/
Addressed by: https:/
vm state and task state management
Addressed by: https:/
cleanup power state (partially implements bp task-management)
Addressed by: https:/
Clear task state in case of error during execution
Addressed by: https:/
Allow stop API to be called in Error
