Difference between revisions of "StructuredStateManagement"
(→High availability) |
(→High availability) |
||
| Line 27: | Line 27: | ||
| − | === | + | === Details === |
| − | In order to | + | In order to implement of this new orchestration layer the following key concepts must be built into the design from the start. |
# A set of '''atomic''' tasks that can be organized into a workflow. | # A set of '''atomic''' tasks that can be organized into a workflow. | ||
| − | # Task resumption | + | # Task resumption. |
| + | # Task rollback. | ||
# Task tracking. | # Task tracking. | ||
# Resource locking. | # Resource locking. | ||
# Workflow sharding. | # Workflow sharding. | ||
# Simplicity (allowing for extension and verifiability). | # Simplicity (allowing for extension and verifiability). | ||
| + | # Tolerant to upgrades. | ||
| + | |||
| + | ==== Atomic tasks ==== | ||
| + | |||
| + | ===== Why it matters ===== | ||
| + | |||
| + | ===== How it will be addressed ===== | ||
| + | |||
| + | ==== Task resumption ==== | ||
| + | |||
| + | ===== Why it matters ===== | ||
| + | |||
| + | ===== How it will be addressed ===== | ||
| + | |||
| + | ==== Task rollback ==== | ||
| + | |||
| + | ===== Why it matters ===== | ||
| + | |||
| + | ===== How it will be addressed ===== | ||
| + | |||
| + | ==== Task tracking ==== | ||
| + | |||
| + | ===== Why it matters ===== | ||
| + | |||
| + | ===== How it will be addressed ===== | ||
Revision as of 21:21, 22 April 2013
Contents
Summary
Move away from ad-hoc states and state transitions to a more concrete organized structured state management in nova.
Requirements
https://etherpad.openstack.org/task-system
Discussions
https://etherpad.openstack.org/the-future-of-orch
Plan of record
- Create prototype.
- Get feedback from summit session.
- Get more feedback from email list & heat folks about common library.
- Adjust prototype as needed from feedback.
- Split prototype into small chunks.
- Adjust tests for each small chunks.
- Start to submit prototype chunks into review.openstack.org (disabling whole component until ready to turn on).
Design
Details
In order to implement of this new orchestration layer the following key concepts must be built into the design from the start.
- A set of atomic tasks that can be organized into a workflow.
- Task resumption.
- Task rollback.
- Task tracking.
- Resource locking.
- Workflow sharding.
- Simplicity (allowing for extension and verifiability).
- Tolerant to upgrades.
