Project

General

Profile

action #77842

openQA Project - coordination #64746: [saga][epic] Scale up: Efficient handling of large storage to be able to run current tests efficiently but keep big archives of old results

coordination #68923: [epic] Use external videoencoder in production auto_review:"External encoder not accepting data"

Use external videoencoder in production on all o3 machines

Added by okurz 9 months ago. Updated 20 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
2020-11-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See #68923

Acceptance criteria

  • AC1: All o3 workers run the same external video encoder configured (exceptions allowed if required and documented) as in #77839
  • AC2: All o3 workers are not overstressed by the external video encoder, i.e. not more jobs failing or incompleting due to an overstressed worker

Suggestions

  • Research what has been done in #77839
  • Ensure ffmpeg is installed on all worker machines
  • Configure external video encoder as documented in https://progress.opensuse.org/issues/68923#note-17
  • Monitor the CPU usage of ffmpeg e.g. via htop and also the overall performance of each worker, e.g. check for incomplete jobs due to performance issues
  • Wait for feedback for some days

Related issues

Copied from openQA Infrastructure - action #77839: Use external videoencoder in production on one o3 workerResolved2020-11-13

Copied to openQA Infrastructure - action #77845: Use external videoencoder in production on all osd machinesNew2020-11-13

History

#1 Updated by okurz 9 months ago

  • Copied from action #77839: Use external videoencoder in production on one o3 worker added

#2 Updated by okurz 9 months ago

  • Copied to action #77845: Use external videoencoder in production on all osd machines added

#3 Updated by okurz 9 months ago

  • Tracker changed from coordination to action

#4 Updated by okurz 23 days ago

  • Status changed from Workable to New

moving all tickets without size confirmation by the team back to "New". The team should move the tickets back after estimating and agreeing on a consistent size

#5 Updated by okurz 20 days ago

  • Target version changed from Ready to future

Also available in: Atom PDF