While it would certainly be possible to have each bare metal host handle its own image downloading for tasks and execution, that isn't the most efficient method in terms of disk usage or maintenance (making sure old images are removed, etc).
There is some overlap with the sysadmin-ish tasks needed to support disposable clients but some of the features needed are: downloading images to use for task executor downloading images to use for target VMs find already-downloaded images specify which image to use for task executor in a way that doesn't require package changes or much manual tweaking
This ticket is a duplicate of https://pagure.io/taskotron/libtaskotron/issue/229
This ticket also depends on https://pagure.io/taskotron/libtaskotron/issue/291 This ticket also depends on https://pagure.io/taskotron/libtaskotron/issue/290 This ticket also depends on https://pagure.io/taskotron/libtaskotron/issue/264 This ticket also depends on https://pagure.io/taskotron/libtaskotron/issue/263
Seems like a job for read-only nfs. Let the nfs server handle the job of periodically downloading images.
The bits covered here which aren't complete have been moved to other tickets, closing.
Metadata Update from @tflink: - Issue marked as depending on: #119 - Issue marked as depending on: #120 - Issue marked as depending on: #131 - Issue marked as depending on: #132 - Issue tagged with: infrastructure
Log in to comment on this ticket.