Tempest requirements not in sync with openstack

[Hugh Saunders]

It is difficult the install tempest as part of an openstack installation as tempest does not follow the openstack process for requirements.

Tempest needs some level of insulation from other openstack components so that it can have its own set of deps.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/192445
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=ab41a3708a4fc172fdd306193778d9af11e4ba89
Submitter: Jenkins
Branch: juno

commit ab41a3708a4fc172fdd306193778d9af11e4ba89
Author: kevin <email address hidden>
Date: Tue Jun 16 17:09:21 2015 -0500

    Backported tempest roles from Master

    Change to backport the tempest roles from master into juno. This
    change is being done because the deps within Juno no longer allow
    tempest to be installed along side OpenStack without a lot of
    tom foolery which is not worth the maintenance costs. The upstream
    process for installing tempest work and will work with future
    versions of the Juno development branch.

    Change-Id: I18a690c614253d6b7e2e52e40bf1f14dd6dad87c
    Closes-Bug: #1466010

[Darren Birkett (darren-birkett)]

This review: https://review.openstack.org/#/c/193850/

adds a change in master to add a flag to yaprt to ignore tempest. That commit refers to this bug, however this bug is tracking the backport of the original work to move tempest into a venv.

So, does the yaprt change also need to happen in kilo and juno?

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: kilo
Review: https://review.openstack.org/195225

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/195232
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=2f11799bd85b4bc80f83dd38946a889c53509b9a
Submitter: Jenkins
Branch: kilo

commit 2f11799bd85b4bc80f83dd38946a889c53509b9a
Author: kevin <email address hidden>
Date: Sat Jun 20 22:54:23 2015 -0500

    Added flag to instruct yaprt to ignore tempest

    This change makes it possible for OSAD to instruct yaprt to NEVER
    do anything with tempest and the requirements that are being
    brought with the requirements that can cause issues with un-versioned
    requirements. This flag simply instructs yaprt to index the repo
    as a item in the report but in this case absolutely no requirements
    will be indexed or built for tempest.

    This was done because tempest does not version anything and its
    forward movement makes it impossible to maintain a consistent stack
    and for our purposes, we install tempest in a venv using an isolated
    install so none of these tempest requirements are necessary for us
    to have to deal with.

    Change-Id: I619300352efe50828fc34ee1ded96e13a43522cd
    Closes-Bug: #1466010
    (cherry picked from commit cba5f5cf3d928da8cf25b7f2d4d2ecfc2957846f)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: juno
Review: https://review.openstack.org/197342

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/195225
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=49655597722e04aaeff755240fa4c14b7b7c8e3c
Submitter: Jenkins
Branch: kilo

commit 49655597722e04aaeff755240fa4c14b7b7c8e3c
Author: kevin <email address hidden>
Date: Mon Jun 22 15:17:28 2015 -0500

    Updated tempest isolation options

    This change updates the way that the packages are installed in an
    isolated deployment. This ensures that our build packages are used
    within the deployment while also allowing temptest to go online and
    consume upstream packages from pypi. Additionally this updates
    tempest-lib which is needed to make keystone w/ fernet tokens go as
    there is an upstream issues with date timestamps with all versions
    of tempest-lib that will prohibit the use of fernet tokens.

    Change-Id: Ia479610b9ab69d64d1de756099d840b2ab331378
    Related-Bug: #1466010
    (cherry picked commit from 2086f6edb1a4c50dc0000804a510aa4da1af4f5f)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/197342
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=e81c5a208be338cfd4b7c431022bd4df1a17ed3a
Submitter: Jenkins
Branch: juno

commit e81c5a208be338cfd4b7c431022bd4df1a17ed3a
Author: kevin <email address hidden>
Date: Tue Jun 30 16:40:31 2015 -0500

    Updated tempest isolation options

    This change updates the way that the packages are installed in an
    isolated deployment. This ensures that our build packages are used
    within the deployment while also allowing temptest to go online and
    consume upstream packages from pypi.

    Change-Id: Ia479610b9ab69d64d1de756099d840b2ab331378
    Closes-Bug: #1466010
    (cherry picked commit from 2086f6edb1a4c50dc0000804a510aa4da1af4f5f)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.