the following attributes was added:
- node_filter: YAQL expression to select nodes for applying the graph
- node_attributes_on_success: attributes which will be applied to node
if execution of graph completes successfully.
- node_attributes_on_fail: attributes which will be applied to node
if execution of graph fails.
- node_attributes_on_stop: attributes which will be applied to node
if execution of graph interrupts.
Blueprint: graph-concept-extension
Change-Id: I949b3971f62c17b1d243c8ed97e2802afa4e0cce
Since self.env.create always return db object now,
we can use this returned value instead of
self.env.clusters list.
It's a refactoring, so no bug or blueprint.
Change-Id: If7c84cb7124bcf08ef5ff110542012564190fae1
In db scheme the 'condtition' field was string, but
but for using yaql in condtition, we have to declare condittion as dict object,
for example: '"condtition": {"yaql_exp": "changed($.nodes)"'
This patch updates database schema, to allow store dict object in condition field.
Closes-Bug: 1564308
Change-Id: I4978fbc5eb4d2492411a016dadc0ed6028a36899
Following handles has been added:
GET /releases/<release_id>/deployment_graphs/
GET/POST/PUT/PATCH/DELETE /releases/<release_id>/deployment_graphs/<graph_type>/
GET /clusters/<cluster_id>/deployment_graphs/
GET/POST/PUT/PATCH/DELETE /clusters/<cluster_id>/deployment_graphs/<graph_type>/
GET /plugins/<cluster_id>/deployment_graphs/
GET/POST/PUT/PATCH/DELETE /clusters/<plugin_id>/deployment_graphs/<graph_type>/
Change-Id: I1fd5fb53700c761a65249dd0a646dbdbf8d5272a
Implements: blueprint custom-graph-execution
Now it is possible to update deployment graph name
and tasks keeping the graph database ID intact.
DeploymentGraph.update and DeploymentGraph.create_for_model
methods are inroduced that allow to update or create graph.
Change-Id: I8170569d9283d226f53b5fb2879a5ff9ee7bb984
Implements: blueprint custom-graph-execution
verbose_ prefix does not reflected any meaningfull information
Change-Id: I7138abae9c7ccdc8c7996e0fed5a7bc868848ba1
Implements: blueprint custom-graph-execution
This models store deployment tasks sets that is grouped under
DeploymentGraph record with unique id.
DeploymentGraph is linked via m2m to the:
- releases
- plugins
- clusters
This transitive tables containing 'type' field, that should be used as
graphs merge key in business logic.
DocImpact
Implements: blueprint custom-graph-execution
Change-Id: If53cb58e8ae4cf8fe4caa470bf207ff1683b1cda
Andreas Jaeger