Comply with upper-constraints when building images

[Peter Stachowski]

Currently building an image uses requirements but not upper-constraints. This can cause an issue when libraries change and the image becomes out of sync with the server code (for example when oslo.context changes).

Trove integration should use upper-constraints as well.

[jian.song (jiansong)]

function cmd_build_image() {
    IMAGE_DATASTORE_TYPE=${1:-'mysql'}
    ESCAPED_PATH_TROVE=${2:-'\/opt\/stack\/trove'}
    HOST_SCP_USERNAME=${3:-'ubuntu'}
    GUEST_USERNAME=${4:-'ubuntu'}

    exclaim "Ensuring we have all packages needed to build image."
    sudo $HTTP_PROXY $PKG_MGR $PKG_GET_ARGS update
    sudo $HTTP_PROXY $PKG_MGR $PKG_GET_ARGS install qemu
    sudo -H $HTTP_PROXY pip install --upgrade pip dib-utils

    install_devstack_code

    cmd_clone_projects do_not_force_update $REDSTACK_SCRIPTS/image-projects-list

    exclaim "Use tripleo-diskimagebuilder to actually build the Trove Guest Agent Image."
    build_guest_image $IMAGE_DATASTORE_TYPE
}

Is here to change? ...

[Amrith Kumar (amrith)]

This has already been fixed.

[Amrith Kumar (amrith)]

And, no, that's not where the fix must go.

[jian.song (jiansong)]

ok,thanks