Provisioning should support Beaker pool enforcement/exclusion

[happz]

In Beaker jobs, this is possible to request/exclude a specific Beaker pool (not to be confused with Artemis pools):

system-pool: !virtkvm-gating
system-pool: virtkvm-gating

First, it's a feature sought by current Beaker users, and it probably shouldn't be hard to extend the Beaker plugin/mrack to support this.

Second, I'm not sure how to support this with Artemis, and to what extent this should be decoupled from how: beaker. As Artemis can and does wrap Beaker service too, it can certainly accept constraints of this kind and propagate them to Beaker behind the curtain. Feels like something generic enough for hardware, but it's not actual HW requirements, more like an organizational aspect... Anyway, adding HW labels, open for discussion.

[thrix]

Relevant RH issues:
https://issues.redhat.com/browse/KQE-59

[psss]

@skycastlelily, would you be possibly interested in this? We consider this for 1.38 or 1.39.

[skycastlelily]

Sure,will look into and work on it tomorrow:)

…

On Tue, Oct 8, 2024 at 10:52 PM Petr Šplíchal ***@***.***> wrote: @skycastlelily <https://github.com/skycastlelily>, would you be possibly interested in this? We consider this for 1.38 or 1.39. — Reply to this email directly, view it on GitHub <#2346 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKFR23FLR3EVZTX3WKXWVBTZ2PWSXAVCNFSM6AAAAABPSNUTRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQGA3TMNJQG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[psss]

That's great, proposing for 1.38 then. Thanks!

[skycastlelily]

Here are the merge requests :)
#3271
https://gitlab.com/testing-farm/artemis/-/merge_requests/1283

[thrix]

Seems nothing else to do here on tmt side, closing.