|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| − | '''Revised on:''' {{REVISIONMONTH1}}/{{REVISIONDAY}}/{{REVISIONYEAR}} by {{REVISIONUSER}}
| |
| | | | |
| − | == Overview ==
| |
| − |
| |
| − | A persistence API as well as base persistence types are provided with taskflow for the purpose of ensuring that jobs, flows, and there associated tasks can be backed up in a database or in memory (or elsewhere). The user, when configuring the persistence API, has the option to specify which backend is desired and subsequently store and retrieve the data associated with the jobs, flows, and tasks in use.
| |
| − |
| |
| − | '''For in-depth details see:''' [http://docs.openstack.org/developer/taskflow/persistence.html Details]
| |
| − |
| |
| − | === Why? ===
| |
| − |
| |
| − | [[File:Machovka_harddisk.png|frame|right]]
| |
| − |
| |
| − | * Allows for reconstruction and resumption of flows and there associated tasks.
| |
| − | * Allows for redundant checks that expected data is provided.
| |
| − | * Allows for the user to view the history of a jobs, flows and there associated tasks.
| |
| − | * Facilitates debugging of taskflow usage and integration (and runtime/post-runtime analysis).
| |
| − |
| |
| − | == Checkpointing ==
| |
| − |
| |
| − | A WIP topic/discussion is the concept of check-pointing.
| |
| − |
| |
| − | '''See:''' [[TaskFlow/Checkpointing|Checkpointing]]
| |
