Project

General

Profile

action #90344

kubevirt backend for openQA and/or os-autoinst

Added by okurz 4 months ago. Updated 29 days ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-03-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

We use a lot of virtual machines to run jobs. Some of that we might be able to move to containers, but we need full VMs for some of the use cases.

Suggestion

  • Look into KubeVirt
  • Add a new backend in os-autoinst i.e. implement a new class backend/kubevirt.pm

History

#1 Updated by cdywan 4 months ago

  • Description updated (diff)

#2 Updated by cdywan 4 months ago

  • Blocked by action #81060: Create a helm chart to deploy web UI in kubernetes added

#3 Updated by okurz 4 months ago

Not sure if it's just backend/kubevirt.pm that will help or if we need a change on the level of openQA. kubevirt can provide management of ressources for multiple VMs. If we would just need to control the available ressources by the number of openQA worker instances where each corresponds to one VM there would be no significant gain.

Ideas I can think of:

  • Still first create a "backend/kubevirt.pm" for a 1:1 VM mapping. This could help to get some experience first
  • Likely an initial "kubevirt" backend could be very similar to the "svirt" backend
  • Maybe the current approach of multiple assignments as for the directly chained jobs can be used to assign multiple jobs in a row to kubevirt and then we can try to assign all these to kubevirt as ressources are available
  • Use the concept of "assignment" to workers to check if the requested ressources for VMs are available and unassign again if not, without failing the test jobs. Maybe this is even something we could use for the qemu backend?

#4 Updated by cdywan 29 days ago

  • Blocked by deleted (action #81060: Create a helm chart to deploy web UI in kubernetes)

#5 Updated by cdywan 29 days ago

  • Blocks action #81060: Create a helm chart to deploy web UI in kubernetes added

#6 Updated by okurz 29 days ago

Wait. Why should a kubevirt backend block a helm chart for the openQA webui?

#7 Updated by cdywan 29 days ago

okurz wrote:

Wait. Why should a kubevirt backend block a helm chart for the openQA webui?

I flipped the relation to match the Blocked state. But honestly I'm not sure why either should be blocked. Maybe we can discuss this in the standup tomorrow?

#8 Updated by okurz 29 days ago

  • Blocks deleted (action #81060: Create a helm chart to deploy web UI in kubernetes)

#9 Updated by okurz 29 days ago

sure we can. But I agree with you that the two tickets are not blocking each other, either way :) I have removed that blocking relationship.

Also available in: Atom PDF