Shall we use resalloc to dynamically provision workers? about openscanhub HOT 3 OPEN

I am opening this issue after discussing dynamic provisioning of workers with @lzaoral and @praiskup.

Thank you for the issue! Just a few additions:

It is used inside Copr infrastrucutre to manage builders (workers).

Yes, exactly - the "Builder" and "Worker" are a bit confusing terms when we talk about OpenScanHub and Copr. Copr isn't using the Kobo framework; in the Copr architecture we have basically just one "Worker" (named Backend), and that "Worker" controls all the (even hundreds of) parallel tasks alone and delegates the heavy work (Mock processes) to Builders over SSH.

Example: vm_alloc.py

If this needs to be generalized into a library for better reuse, let us know.

from openscanhub.

I discussed this issue with @kdudka and we agreed to introduce an optional dependency on resalloc in hub component.

from openscanhub.

This issue is still working in progress. @praiskup is prototyping a daemon that should fit OpenScanHub's workflow to dynamically spin up workers (praiskup/resalloc#125).

from openscanhub.