Difference between revisions of "StructuredStateManagement"
(→Summary) |
(→Summary) |
||
| Line 20: | Line 20: | ||
# Adjust tests for each 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). | # Start to submit prototype chunks into review.openstack.org (disabling whole component until ready to turn on). | ||
| + | |||
| + | == Design == | ||
| + | |||
| + | <gallery> | ||
| + | File:Example.jpg|Caption1 | ||
| + | File:http://i.imgur.com/O6AC6kJ.png|Caption2 | ||
| + | </gallery> | ||
| + | |||
| + | === Resumption === | ||
=== High availability === | === High availability === | ||
Revision as of 20:53, 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
- Example.jpg
Caption1
- Http://i.imgur.com/O6AC6kJ.png
Caption2
