Miloš Prchlík

Adds a new key, `block-device`, that guest topology may use to inform tests about which disk matches requested by HW requirements. Related to https://github.com/teemtee/tmt/issues/2402 Pull Request Checklist * [x] implement...

``` TMT_SHOW_TRACEBACK=1 tmt -vv run plans --default \ provision --how virtual --image fedora-39 \ --hardware 'disk[1].size=20GB' \ --hardware 'disk[0].size=15GB' \ login -s provision \ finish ``` Fixes https://github.com/teemtee/tmt/issues/2765 Pull Request...

Expose actual guest HW description in guest topology

3

Related to https://github.com/teemtee/tmt/issues/2402. The patch bootstraps `hardware` field in the guest topology content, and populates it it very basic content. Extending it with more info, e.g. `disk` or `system`, will...

Pull Request Checklist * [x] implement the feature

Beaker plugin should allow submitting jobs with a specific owner

1

As suggested by current Beaker users, they'd like `bkr job-submit --job-owner=foo ...` to be supported.

Support multiple disks in testcloud VMs

1

As proposed on today's workshop.

Allow disk/network HW requirements to speak about the whole set of devices

1

The current assumption is the index matters: ```yaml disk: - size: "> 20 GB" ``` The first disk shall have this size. But what if it's "any disk", "all disks"...

rstrnt-sync-* apparently not compatible with tmt

3

When called for the first time, `rstrnt-sync-set` spawns a background process that listens on TCP & Unix sockets for incoming sync changes. However, when a test finishes, tmt & SSH...

Tests performing `PROVISION_HOW=container` use a wide array of containers, both official ones and custom ones as well. The goal of this ticket is to level the playfield and make the...

## Rules **General ones** * design the docstrings and help texts as if they are destined to be rendered by Sphinx, i.e. make use of ReST goodies: literals for literals...