Jump to: navigation, search

StructuredStateManagement

Revision as of 21:21, 22 April 2013 by Harlowja (talk | contribs) (High availability)

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

  1. Create prototype.
  2. Get feedback from summit session.
  3. Get more feedback from email list & heat folks about common library.
  4. Adjust prototype as needed from feedback.
  5. Split prototype into small chunks.
  6. Adjust tests for each small chunks.
  7. Start to submit prototype chunks into review.openstack.org (disabling whole component until ready to turn on).

Design

New-arch.png



Details

In order to implement of this new orchestration layer the following key concepts must be built into the design from the start.

  1. A set of atomic tasks that can be organized into a workflow.
  2. Task resumption.
  3. Task rollback.
  4. Task tracking.
  5. Resource locking.
  6. Workflow sharding.
  7. Simplicity (allowing for extension and verifiability).
  8. 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