OpenStack Compute (Nova)

transactional task management for Folsom

Registered by Yun Mao on 2011-12-21

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:
milestone icon 2012.2
Started by
Yun Mao on 2012-05-17
Completed by
Thierry Carrez on 2012-08-15

Related branches

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://review.openstack.org/#q,topic:bp/task-management,n,z

Addressed by: https://review.openstack.org/7796
    cleanup power state (partially implements bp task-management)

Gerrit topic: https://review.openstack.org/#q,topic:bug/997867,n,z

Addressed by: https://review.openstack.org/8254
    vm state and task state management

Addressed by: https://review.openstack.org/10266
    cleanup power state (partially implements bp task-management)

Addressed by: https://review.openstack.org/10774
    Clear task state in case of error during execution

Addressed by: https://review.openstack.org/10775
    Allow stop API to be called in Error

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.