Hi, Renat, I want to make it clear. Then, what you want to see is dependencies between workflow executions? or task executions in one workflow? We know that we could use a separate task or a workflow as a 'task'.
On Wed, Sep 2, 2015 at 3:33 PM, Renat Akhmerov <rakhme...@mirantis.com> wrote: > > On 01 Sep 2015, at 22:21, Lingxian Kong <anlin.k...@gmail.com> wrote: > > To achieve that, we should record the execution/task-execution > relationship during an execution is running, because we have no such info > currently. > > > Well, in DB model we, in fact, have a field pointing to parent task > execution id (and hence we can figure out workflow execution id easily), > it’s required because child workflow needs to communicate its result to its > parent workflow somehow. But it’s not displayed anywhere. So we can use > this field. > > > Renat Akhmerov > @ Mirantis Inc. > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- *Regards!* *-----------------------------------* *Lingxian Kong*
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
