Create openQA MultiMachine tests for deploying Kubernetes on Tumbleweed using both k3s and rke2
a project by pdostal
Updated almost 2 years ago. No love. 1 follower.

Rancher maintains 2 Kubernetes distribution, both production grade:

  • k3s: Single binary containing containerd backend. Can be run as server or agent on each node of cluster. SQLite is used by default instead of ETCD. MySQL and Postgres also supported. No prerequisity. Intended for edge computing.
  • RKE: Deployed remotely over SSH on top of Docker which is the only required component of the underlying OS. Standard ETCD database in container. Each node and its roles are defined in YAML. Resource hungry, datacenter grade.

Each scenario needs:

1) Support Server: As Internet gateway, DHCP and DNS server. 2) Master node for the control node and it's database 3) 4) Worker nodes joining the cluster.

Resources:

  • [k3s webpage]: https://k3s.io/
  • [k3s github repository]: https://github.com/k3s-io/k3s
  • [rke1 github repository]: https://github.com/rancher/rke
  • [rke1 cluster.yaml]: https://rancher.com/docs/rke/latest/en/example-yamls/#minimal-cluster-yml-example
  • [rke1 deploy guide]: https://rancher.com/docs/rke/latest/en/installation/#prepare-the-nodes-for-the-kubernetes-cluster

This project was inspired by the awesome [SUSE @Home] workshop: https://github.com/SUSE/suse-at-home

TO-DO:

  • Run more tests on top of the Kubernetes cluster.
  • Implement the same for rke2 (not in production yet).

Join this project

Looking for hackers with the skills:

openqa kšs rke2

This project is part of:

Hack Week 20

Activity

  • almost 2 years ago: pdostal added keyword "kšs" to this project.
  • almost 2 years ago: pdostal added keyword "rke2" to this project.
  • almost 2 years ago: pdostal added keyword "openqa" to this project.
  • over 3 years ago: pdostal started this project.
  • over 3 years ago: pdostal originated this project.


    • Comments

    • pdostal
      over 3 years ago by pdostal | Reply

      This pull request has been created.

    Similar Projects

    Enhance UV openQA helper script by mdonis

    Description

    A couple months ago an UV openQA helper script was created to help/automate the searching phase inside openQA for a given MU to test. The script searches inside all our openQA job groups (qam-sle) related with a given MU and generates an output suitable to add (copy & paste) inside the update log.

    This is still a WIP and could use some enhancements.

    Goals

    • Move script from bash to python: this would be useful in case we want to include this into MTUI in the future. The script will be separate from MTUI for now. The idea is to have this as a CLI tool using the click library or something similar.
    • Add option to look for jobs in other sections inside aggregated updates: right now, when looking for regression tests under aggregated updates for a given MU, the script only looks inside the Core MU job group. This is where most of the regression tests we need are located, but some MUs have their regression tests under the YaST/Containers/Security MU job groups. We should keep the Core MU group as a default, but add an option to be able to look into other job groups under aggregated updates.
    • Remove the -a option: this option is used to indicate the update ID and is mandatory right now. This is a bit weird and goes against posix stardards. It was developed this way in order to avoid using positional parameters. This problem should be fixed if we move the script to python.

    Some other ideas to consider:

    • Look into the QAM dashboard API. This has more info on each MU, could use this to link general openQA build results, whether the related RR is approved or not, etc
    • Make it easier to see if there's regression tests for a package in an openQA test build. Check if there's a possibility to search for tests that have the package name in them inside each testsuite.
    • Unit testing?

    More ideas TBD

    Resources

    https://github.com/os-autoinst/scripts/blob/master/openqa-search-maintenance-core-jobs

    https://confluence.suse.com/display/maintenanceqa/Guide+on+how+to+test+Updates

    Post-Hackweek update

    All major features were implemented. Unit tests are still in progress, and project will be moved to the SUSE github org once everything's done. https://github.com/mjdonis/oqa-search

    Learn obs/ibs sync tool by xlai

    Description

    Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.

    Goals

    Check how the tool is implemented, and be capable to add/modify our needed images/repo in future by ourselves.

    Resources

    • https://github.com/os-autoinst/openqa-trigger-from-obs
    • https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/tree/master?ref_type=heads

    OpenQA Golang api client by hilchev

    Description

    I would like to make a simple cli tool to communicate with the OpenQA API

    Goals

    • OpenQA has a ton of information that is hard to get via the UI. A tool like this would make my life easier :)
    • Would potentially make it easier in the future to make UI changes without Perl.
    • Improve my Golang skills

    Resources

    • https://go.dev/doc/
    • https://openqa.opensuse.org/api

    New features in openqa-trigger-from-obs for openQA by jlausuch

    Description

    Implement new features in openqa-trigger-from-obs to make xml more flexible.

    Goals

    One of the features to be implemented: - Possibility to define "VERSION" and "ARCH" variables per flavor instead of global.

    Resources

    https://github.com/os-autoinst/openqa-trigger-from-obs

    Setup a new openQA on more powerful server by JNa

    Description

    • currently local openQA storage is insufficient

    Goals

    -Migrate to more powerful machine

    Resources

    -Service Rainbow