Now /graphs/execute/ handler is used to execute graph
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Documentation Team |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
commit 98e45a0317a1482
Author: Ilya Kutukov <email address hidden>
Date: Wed Jul 27 14:30:27 2016 +0300
Now /graphs/execute/ handler is used to execute graph
$ fuel2 graph execute --env 1 [--nodes 1 2 3] [--graph_types gtype1 gtype2] [--task-names task1 task2] [--force] [--dry-run]
now calling brand new:
/api/
handler that using the Transactions Manager.
Also now it is possible to call:
$ fuel2 graph execute --force
to enforce execution of tasks without skipping.
$ fuel2 graph execute --task-names task1 task2
to run only specific tasks ignoring dependancies.
DocImpact
Change-Id: Iafc59c60a1ebce
Implements: blueprint graph-concept-
Changed in fuel: | |
milestone: | none → 10.0 |
assignee: | nobody → Fuel Documentation Team (fuel-docs) |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: area-docs |