Orchestration of long-running transactions
Registered by
Glen Campbell
Nova needs to be able to monitor and manage long-running transactions. For example, when creating 1,000 servers, it may be necessary to create a build plan, retry failed builds, refresh the plan, and possibly even roll back the entire transaction if it cannot be completed rapidly enough. To do this, an orchestration service is proposed that can monitor workflows around Nova events and transactions.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- High
- Drafter:
- Sandy Walsh
- Direction:
- Approved
- Assignee:
- Nova Orchestration Team
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Vish Ishaya
Related branches
Related bugs
Sprints
Whiteboard
Revisit
(?)