coordination #68923

Updated by okurz about 1 year ago

## Motivation
os-autoinst supports "external videoencoder" where we can configure command lines to call other commands. With more efficient video encoders we can save storage space and hence avoid space issues and can store results for a longer time which helps especially for bug investigation discovered by openQA tests.

## Acceptance
### acceptance criteria

* **AC1:** One worker runs with an external video encoder configured
* **AC2:** The configured external video encoder provides significantly smaller video files instead of the default ones
* **AC3:** The worker is not overstressed by the external video encoder, i.e. not more jobs failing or incompleting due to an overstressed worker
* **AC4:** All o3 workers run the same (exceptions allowed if required and documented)
* **AC5:** The same as above for OSD
* **AC6:** No more workarounds in OSD due to inefficient video encoder

## Suggestions

AC1: Install ffmpeg on the worker.
* AC2: Try to find a good encoder setting. Likely VP9 would make sense so `ffmpeg -hide_banner -nostats -r 24 -f image2pipe -vcodec ppm -i - -pix_fmt yuv420p -c:v libvpx-vp9 -crf 35 -b:v 1500k -cpu-used 0` would be a start. Also consider AV1 (see #75256).
* AC3: Check whether the resulting videos work (including seeking).
* AC4: Adopt any special handling of videos in our production instances:

### suggestions
Try it on one worker host first. As not all worker hosts have the same hardware the setting might need to be tweaked per worker host.
* Monitor the CPU usage of ffmpeg e.g. via `htop` and also the overall performance of the worker, e.g. check for incomplete jobs due to performance issues.
* I'd refrain from using non-royalty free formats to avoid any legal problems.
* Adopt any special handling of videos in our production instances: