Project

General

Profile

Actions

action #160209

closed

coordination #58184: [saga][epic][use case] full version control awareness within openQA

coordination #154780: [epic] openQA scenario definitions fully in git

Reduce duplication in machine definitions in https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml#L8, e.g. with re-usable machine "defaults" size:S

Added by okurz 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Motivation

There is duplication in machine definitions in https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/scenario-definitions.yaml#L8 and it's good to keep duplication to a minimum. Because this file serves as a showcase for how bigger projects could look like we should actually prevent this duplication. This could be solvable by just moving the common settings to "products" but the settings do not belong to the product, they are machine settings.

Acceptance criteria

Suggestions

  • Use YAML merge keys or consider re-usable machine "defaults" as an openQA feature. At best contrast both solutions for easy comparison
  • Implementation proposal
    machines:
      64bit-2G:
        backend: qemu
        settings:
          <<: &M
            HDDSIZEGB: "20"
            QEMUCPU: host
            WORKER_CLASS: qemu_x86_64
          QEMURAM: "2048"
      64bit-4G:
        backend: qemu
        settings:
          <<: *M
          QEMURAM: "4096"

Related issues 1 (0 open1 closed)

Copied from openQA Project - action #155218: [spike][timeboxed:30h] Use scenario definitions instead of job group templates for os-autoinst-distri-opensuse size:MResolvedtinita

Actions
Actions

Also available in: Atom PDF