We're using Swift to serve images when using the direct deploy. This RFE proposes an alternative way of serving them via the existing ironic-conductor HTTP server. This will avoid dependency on Swift. As a bonus point, we may be able to convert images to RAW format on the conductor, then stream them to IPA, avoiding in-memory conversion.
In discussion with the development team, we realized raw streaming would be problematic, however we think that could be solved by turning on server side compression, which should be transparently handled by the client and reduce the network overhead. It would increase webserver CPU overhead, but that is likely fine to save the network utilization for larger images with lots of whitespace.
Let us call it done. There may be improvements, one issue is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1630964, but the core of this feature is done.
This feature has been verified with two options
1) Raw image
2) ImageDownloadSource: http
Both cases we used the logs to validate streaming success
look in journal file log " Image streamed onto device /dev/vda2 in 14.087767124176025 seconds"
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.