So to get things going for now we wrote a standalone fedmsg consumer to schedule openQA jobs:

https://phab.qadevel.cloud.fedoraproject.org/diffusion/OPENQA/browse/develop/scheduler/fedora_openqa_schedule/consumer.py

but ideally we should run it from Taskotron (along with several other things, to reduce mushrooming of standalone consumers). This requires D748 (a Taskotron trigger that fires on Pungi 4 compose completion), and either a Taskotron trigger for two-week Atomic composes or releng to switch two-week Atomic composes to Pungi 4.

We also need, somehow, to ensure the actual task runs in an environment where a correct /etc/openqa/client.conf, with an API key and secret, is in place (and now I think about it, we somehow need to duplicate the task to kick off jobs on both staging and production openQA).