Edge Image Builder and mkosi for Uyuni
a project by oholecek
Updated 11 months ago. 4 hacker ♥️. 1 follower.

Description

One part of Uyuni system management tool is ability to build custom images. Currently Uyuni supports only Kiwi image builder.

Kiwi however is not the only image building system out there and with the goal to also become familiar with other systems, this projects aim to add support for Edge Image builder and systemd's mkosi systems.

Goals

Uyuni is able to

  • provision EIB and mkosi build hosts
  • build EIB and mkosi images and store them

Resources

  • Uyuni - https://github.com/uyuni-project/uyuni
  • Edge Image builder - https://github.com/suse-edge/edge-image-builder
  • mkosi - https://github.com/systemd/mkosi

Join this project

Looking for hackers with the skills:

uyuni edge eib mkosi imagebuilding

This project is part of:

Hack Week 24

Activity

  • 11 months ago: juliogonzalezgil liked this project.
  • 11 months ago: mweiss2 liked this project.
  • 11 months ago: llansky3 liked this project.
  • 11 months ago: vizhestkov liked this project.
  • 11 months ago: oholecek added keyword "imagebuilding" to this project.
  • 11 months ago: oholecek added keyword "uyuni" to this project.
  • 11 months ago: oholecek added keyword "edge" to this project.
  • 11 months ago: oholecek added keyword "eib" to this project.
  • 11 months ago: oholecek added keyword "mkosi" to this project.
  • 11 months ago: oholecek started this project.
  • 11 months ago: oholecek originated this project.


    • Comments

    • oholecek
      11 months ago by oholecek | Reply

      Progress during the Hackweek

      • adapted service salt states for both EIB and mkosi and also updated original Kiwi (handling build host preparation)
      • adapted build image salt state for mkosi and original Kiwi (for actual image building)
      • adapted Java profile creation and editing to support EIB and mkosi

      TODO next:

      • adapt Java side to select correct build host variant
      • post build image inspection for EIB and mkosi and image collection

    Similar Projects

    Flaky Tests AI Finder for Uyuni and MLM Test Suites by oscar-barrios

    Description

    Our current Grafana dashboards provide a great overview of test suite health, including a panel for "Top failed tests." However, identifying which of these failures are due to legitimate bugs versus intermittent "flaky tests" is a manual, time-consuming process. These flaky tests erode trust in our test suites and slow down development.

    This project aims to build a simple but powerful Python script that automates flaky test detection. The script will directly query our Prometheus instance for the historical data of each failed test, using the jenkins_build_test_case_failure_age metric. It will then format this data and send it to the Gemini API with a carefully crafted prompt, asking it to identify which tests show a flaky pattern.

    The final output will be a clean JSON list of the most probable flaky tests, which can then be used to populate a new "Top Flaky Tests" panel in our existing Grafana test suite dashboard.

    Goals

    By the end of Hack Week, we aim to have a single, working Python script that:

    1. Connects to Prometheus and executes a query to fetch detailed test failure history.
    2. Processes the raw data into a format suitable for the Gemini API.
    3. Successfully calls the Gemini API with the data and a clear prompt.
    4. Parses the AI's response to extract a simple list of flaky tests.
    5. Saves the list to a JSON file that can be displayed in Grafana.
    6. New panel in our Dashboard listing the Flaky tests

    Resources

    Move Uyuni Test Framework from Selenium to Playwright + AI by oscar-barrios

    Description

    This project aims to migrate the existing Uyuni Test Framework from Selenium to Playwright. The move will improve the stability, speed, and maintainability of our end-to-end tests by leveraging Playwright's modern features. We'll be rewriting the current Selenium code in Ruby to Playwright code in TypeScript, which includes updating the test framework runner, step definitions, and configurations. This is also necessary because we're moving from Cucumber Ruby to CucumberJS.

    If you're still curious about the AI in the title, it was just a way to grab your attention. Thanks for your understanding.

    Goals

    • Migrate Core tests including Onboarding of clients
    • Improve test reliabillity: Measure and confirm a significant reduction of flakynes.
    • Implement a robust framework: Establish a well-structured and reusable Playwright test framework using the CucumberJS

    Resources