Use testcloud domain API v2

[frantisekz]

Refactors domain configuration interface between tmt and testcloud, to allow greater flexibility and superior api stability when making changes and additions in the future.

Apart from that, doesn't expose support for (will come as a separate PR):

• tpm emulation
• uefi
• cpu core count setting (more advanced topologies to follow https://tmt.readthedocs.io/en/stable/spec/hardware.html#cpu TBD)

testcloud counterparts:

• https://pagure.io/testcloud/c/6f0942cb3ba31ff0927ee8b151218e8dc8b34d7d?branch=master
• https://pagure.io/testcloud/pull-request/155
• https://pagure.io/testcloud/c/7ee6dc839a46c72db6d23bcd2e057c2de6fe5ea8?branch=master
• ...

(compatible testcloud built at): https://copr.fedorainfracloud.org/coprs/frantisekz/testcloud-wip/

[lukaszachy]

@kkaarreell FYI - This adds TPM flag for provision -h virtual

[kkaarreell]

Hi @frantisekz , I would like to test this code but may I ask you to rebase first? For proper testing using my test I need the multi-host related code so it would help me a lot if this would be up to date. Thank you.

[frantisekz]

Hi @frantisekz , I would like to test this code but may I ask you to rebase first? For proper testing using my test I need the multi-host related code so it would help me a lot if this would be up to date. Thank you.

Sure, done!

[frantisekz]

Looks good and works nicely! Thanks! Added just one minor suggestion. Plus, I guess, we should also bump the testcloud require to make sure the new api is installed on the user system, right?

Updated, feedback addressed, thanks!

[psss]

Updated, feedback addressed, thanks!

Nice, thanks!

Hint: During the pull request review it's better to add new commits rather then amending existing ones. It makes it easier to see what actually changed, especially when the force-push is combined with a rebase.

[frantisekz]

Hint: During the pull request review it's better to add new commits rather then amending existing ones. It makes it easier to see what actually changed, especially when the force-push is combined with a rebase.

Yeah, sorry for that, I probably took it as too trivial no do it the proper way around, will pay attention to it the next time.

[psss]

Yeah, sorry for that, I probably took it as too trivial no do it the proper way around, will pay attention to it the next time.

Sure, no problemo.

[psss]

Should be good now, we just need to wait until testcloud gets to stable repos.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config: ValidationError({'jobs': {0: {'packages': defaultdict(<class 'dict'>, {'tmt': {'value': {'targets': ["Expected 'list[str]' or 'dict[str,dict]', got {'fedora-all': None, 'epel-9': None, 'fedora-39': {'additional_repos': 'https://download.copr.fedorainfracloud.org/results/frantisekz/testcloud-wip/fedora-39-x86_64/'}} (type <class 'dict'>)."]}}})}}}).

For more info, please check out the documentation or contact the Packit team.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config: ValidationError({'jobs': {0: {'packages': defaultdict(<class 'dict'>, {'tmt': {'value': {'targets': ["Expected 'list[str]' or 'dict[str,dict]', got {'fedora-all': None, 'epel-9': None, 'fedora-39': {'additional_repos': ['https://download.copr.fedorainfracloud.org/results/frantisekz/testcloud-wip/fedora-39-x86_64/']}} (type <class 'dict'>)."]}}})}}}).

For more info, please check out the documentation or contact the Packit team.

[psss]

/packit test

[psss]

/packit build

Newly added options have been moved to a separate pull request.