Difference between revisions of "Heat/ConvergenceDesign"
< Heat
(→Stack Create Flow) |
(→Stack Create Flow) |
||
Line 43: | Line 43: | ||
|- | |- | ||
| Example || Example || Example | | Example || Example || Example | ||
− | |}{| class="wikitable" | + | |} |
+ | {| class="wikitable" | ||
|- | |- | ||
! Header text !! Header text !! Header text | ! Header text !! Header text !! Header text |
Revision as of 10:10, 18 September 2014
Contents
Convergence Design
This page proposes the design for the convergence blueprints.
Note: Currently this page does not address design for 3rd blueprint "Convergence continuous observer"
Flow Diagrams
Flowchart
Sequence
Data Model Change
Data model for persisting the graph
Add a new table 'resource_graph'
Column name | Type | Constraint |
---|---|---|
resource_id | varchar(36) | NOT NULL ForeignKey resource.id |
needed_by | varchar(36) | NULL ForeignKey resource.id |
stack_id | varchar(36) | NOT NULL ForeignKey stack.id |
retry_count | Integer | Default (0) |
observed_ready | Boolean | Default False |
Stack Create Flow
- Heat engine parses the template and upon successful validation it persists the template, stack ,all the resources and the graph. [Currently only stack and template are stored as part of stack.store() ]
Header text | Header text | Header text |
---|---|---|
Example | Example | Example |
Example | Example | Example |
Example | Example | Example |
Header text | Header text | Header text |
---|---|---|
Example | Example | Example |
Example | Example | Example |
Example | Example | Example |