taskotron / libtaskotron

#229 Sub-Feature: Image Management
Closed: Fixed Opened by tflink.

Closed: Fixed
Reopen Issue

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/issue/94

This ticket also depends on https://pagure.io/taskotron/issue/132
This ticket also depends on https://pagure.io/taskotron/issue/131
This ticket also depends on https://pagure.io/taskotron/issue/120
This ticket also depends on https://pagure.io/taskotron/issue/119

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: #263
- Issue marked as depending on: #264
- Issue marked as depending on: #290
- Issue marked as depending on: #291
Metadata
None
None
None
None
Low
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.