Learn more about these different git repos.
Other Git URLs
At present, the kojivmd daemon relies on having images locally on the builder.
kojivmd
https://docs.pagure.org/koji/winbuild/#administration
This presents a few problems:
Instead, I'm proposing that kojivmd use images (only) from Koji. The images can be cached locally to save bandwidth, but we don't need every win builder to have every image at all times.
Further details to come.
In the current api, the name of the image to use is the first argument to the winBuild() hub call. This becomes the first argument to the winbuild task. The kojivmd daemon will clone the vm of this name using virt-manager.
winBuild()
winbuild
I suggest that in the new system, this name maps to the package name for the image to use. The image to use would be the latest build for that package in the build tag. The kojivmd process would fetch this image (or used a cached copy) and then proceed as normal.
Metadata Update from @mikem: - Custom field Size adjusted to None
Initially, we would provide a backwards compatibility option. If the given vm name does not match any package in the build tag, and this compat option is enabled, then kojivmd would fall back to the old behavior (using an untracked image from the local drive). Once the new way is established, we will deprecate that compat option.
Login to comment on this ticket.