No output in executions listing

[Jiri Tomasek]

Recently Executions listing has been refactored for better performance (split into multiple tables etc.) but the side effect is that GET v2/executions API calls don't include the 'output' of each execution and to actually get it another GET v2/executions/<exID> API call for each execution is required.

TripleO UI uses executions listing and track the results of a set of workflow executions. Only place to keep the information about each of those executions is the execution output. This means, that GUI has to make an API call to get list of executions and then for each execution it needs to make another API request to fetch the output for each execution. This is not exactly performant and the result is actually much worse then the effect of going through multiple DB tables for executions listing request.

Proposed solution is to add 'include_output' boolean parameter to GET v2/executions which would make the response include the outputs with the executions. This solution enables clients to fetch executions outputs in single API call as well as maintains current, more performant, executions listing call without 'output' by default.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/364446

[Dougal Matthews (d0ugal)]

Just to state it clear, this bug is actually reporting a regression caused by the refactoring.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/364446
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=dbdf4fcad2d412265348b48e2de413fbe816768b
Submitter: Jenkins
Branch: master

commit dbdf4fcad2d412265348b48e2de413fbe816768b
Author: Dougal Matthews <email address hidden>
Date: Thu Sep 1 17:25:33 2016 +0100

    Optionally include the output when retrieving all executions

    During the table refactor, the output was removed from the result
    of listing all the executions. This change restores that
    behaviour but doesn't include the output by default to avoid
    performance problems. To include it, the query param
    include_output should be used. For example:

        /v2/executions?include_output=true

    Closes-Bug: #1617351
    Change-Id: I2acec34920e397789fc61f184ed69071497ea7d9

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/mistral 3.0.0.0rc1 release candidate.