kick-start will use cached image even if elements are newer

[Yvonne S.]

Once you run './redstack kick-start <datastore>' the image is cached. If you then pull a more recent copy of the trove-integration repo and run kick-start again, it will use the cached image. It will do this even if the elements have changed.

A fix is proposed that would print out a message if the cached image directory is older than the elements directory (with an option to then force a rebuild of the image).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/151348
Committed: https://git.openstack.org/cgit/openstack/trove-integration/commit/?id=2e3b7761d838b49e85997f62c998a11e602584e2
Submitter: Jenkins
Branch: master

commit 2e3b7761d838b49e85997f62c998a11e602584e2
Author: Peter Stachowski <email address hidden>
Date: Thu Jan 29 14:00:29 2015 -0500

    kick-start doesn't warn on stale image file

    Once you run './redstack kick-start <datastore>' the image is cached.
    If you then pull a more recent copy of the trove-integration repo and
    run kick-start again, it will use the cached image. It will do this
    even if the corresponding elements have changed.

    This fix checks all the files in the elements directory and prints
    out a message if the cached image directory is older than any of
    the files that it is built with. An option to force a rebuild of
    the image was also added.

    Change-Id: I0922c92525ab3ea8678d6dd067ce8bff7d961c31
    Co-Authored-By: Petr Malik <email address hidden>
    Closes-Bug: #1415690