Mistral Tempest tests have a hardcoded dependency on mistral being installed / present

[Kaustuv Royburman]

The Mistral Tempest tests have a hard-coded dependency on Mistral being present when Tempest tests are executed.
When trying to sparse-checkout the mistral_tempest_tests folder to run the Mistral tests as a Tempest plugin; it fails due to Mistral not being installed as some utilities and resources which are written in the Mistral Tempest tests are being hard referenced from Mistral being installed in the same environment.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/500344
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=9f8719024b46955c1a0909b33a31aa0bc496621e
Submitter: Zuul
Branch: master

commit 9f8719024b46955c1a0909b33a31aa0bc496621e
Author: Kaustuv Royburman <email address hidden>
Date: Sat Sep 2 23:15:50 2017 -0500

    Decoupling of Mistral tempest test from Mistral code base

    The Mistral Tempest tests have a hard-coded dependency on Mistral being present
    when Tempest tests are executed.
    When trying to sparse-checkout the mistral_tempest_tests folder to run
    the Mistral tests as a Tempest plugin; it fails due to Mistral not
    being installed as some utilities and resources which are written in
    the Mistral Tempest tests are being hard referenced from Mistral
    being installed in the same environment.

    This patch decouples the Mistral Tempest Tests so that they can be executed in
    a stand-alone mode along with the necessary resources that are required to
    execute the Tempest tests.

    Change-Id: Ifd6a3a65a14c4ad4736dccc3e72cd564b6f53a0a
    Closes-Bug: #1714732

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/mistral 6.0.0.0b2 development milestone.