The role of --http-boot in "openstack overcloud image upload" should be clearer

[Jeremy Freudberg]

In a multiarch cloud when using "openstack overcloud image upload" the argument --http-boot is of vital importance. This argument must be customized such that a distinct folder is created for the images of each arch (and possibly platform). The unit tests reflect this but not any docstring or actual doc (at least upstream).

So, let's make it clearer. Reporting this so that the work can be tracked.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/680122

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/680122
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=5afa9c862a88d6ef9bbbec24cf4d502163c895fb
Submitter: Zuul
Branch: master

commit 5afa9c862a88d6ef9bbbec24cf4d502163c895fb
Author: Jeremy Freudberg <email address hidden>
Date: Wed Sep 4 14:30:47 2019 -0400

    Clarify the purpose of --http-boot

    In a multiarch cloud when using "openstack overcloud image upload" the
    argument --http-boot is of vital importance. This argument must be
    customized such that a distinct folder is created for the images of
    each arch (and possibly platform). Now, reflect this in docstring /
    help text (tripleo-docs already has some content, luckily).

    Change-Id: I707ed1de6aa0347185769baa2ee0539bcb6d2df4
    Closes-Bug: #1840711

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-tripleoclient 12.2.0 release.