os_nova role has no functional testing

[Jesse Pretorius]

The role has no functional testing. This is a release-critical requirement for the Mitaka release.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/289986
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=3206988c0028e33c3369dd6043f24212adbc7921
Submitter: Jenkins
Branch: master

commit 3206988c0028e33c3369dd6043f24212adbc7921
Author: Matt Thompson <email address hidden>
Date: Tue Mar 8 15:43:44 2016 +0000

    Enable functional convergence testing

    This commit updates tests/test.yml to deploy rabbitmq, galera,
    keystone, and nova for a functional convergence test. Note that we
    point at a non-existent memcached server, but this can be adjusted to
    build memcached if deemed necessary. Additionally, we deploy the
    nova-compute service but as it is within a container it's
    non-functional. Closer inspection also reveals that while the service
    is running, it's actually throwing an error due to lack of python
    libvirt module.

    Change-Id: Iba146290f64dbed23ae1d67c3548a884288b292b
    Partial-Bug: #1553963

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/292497
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=bc1c46fbfdb0934edfadc2d020540db12f8b118e
Submitter: Jenkins
Branch: master

commit bc1c46fbfdb0934edfadc2d020540db12f8b118e
Author: Matt Thompson <email address hidden>
Date: Mon Mar 14 16:36:55 2016 +0000

    Use upper-constraints file in developer mode

    Last week, keystone was failing to install in developer mode due to us
    not specifying upper constraints. This was due to an upcapped version
    of pysaml2 being installed which is causing problems. This commit first
    clones the requirements repo and then uses the upper constraints file
    when installing packages.

    Note that we only update pip_install_options when in developer mode if
    the constraints aren't already set. This is because in developer mode
    you could have a container with multiple services running on it and the
    pip_install_options fact would get updated when already set, resulting
    in pip failing to install packages.

    Change-Id: If2e7036d02a94bee67df12a610b0110434410777
    Partial-Bug: #1553963