Release notes
Change-Id: I3dff86398ea6a2a28a65e40c5ecce475584e5539
This commit is contained in:
parent
44ac05e398
commit
b07e6afc61
@ -0,0 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- Parallel evaluation of Vitrage templates.
|
||||
The user can now specify a number of workers to evaluate the templates.
|
||||
Each such worker, holds a clone of the graph and will evaluate a portion
|
||||
of the template scenarios. The number of workers defaults to the number
|
||||
of available cores.
|
@ -0,0 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- Persisting of the current active actions.
|
||||
Scenarios that execute the same actions are considered overlapping,
|
||||
Vitrage keeps track of these actions, previously in-memory and now it is
|
||||
stored in the DB. This allows for parallel evaluators.
|
5
releasenotes/notes/sql_integration-c33342d100492ceb.yaml
Normal file
5
releasenotes/notes/sql_integration-c33342d100492ceb.yaml
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- Integration with Sql Alchemy.
|
||||
Allows for data and state to be kept after restarts.
|
||||
And will also allow a shared data store for multiple processes.
|
Loading…
x
Reference in New Issue
Block a user