Generate ignition/combustion files from Uyuni/SUSE Manager
a project by dvosburg
Updated almost 2 years ago. 4 hacker ♥️. 1 follower.

Project Description

Ignition and combustion are the json configuration files used in SLE Micro/Leap Micro/Microos/ALP. These originated in Fedora CoreOS - so it is not distribution-specific.

Uyuni should be able to provision these systems without requiring users to learn the json formatting and layout. Salt has json output, and formulas with forms are used in other cases in Uyuni.

Provisioning has long been a key value in Uyuni/SUMA, and this extends the viability in directions that will matter now and in the future.

Integration into a deployment process would be the next logical step - but just getting the right files is a great start.

Goal for this Hackweek

Creating a formula with forms that can be selected in Uyuni that outputs the ignition/combustion json files.

Resources

https://documentation.suse.com/sle-micro/5.5/html/SLE-Micro-all/cha-images-ignition.html

https://coreos.github.io/ignition/

https://documentation.suse.com/sle-micro/5.5/html/SLE-Micro-all/cha-images-combustion.html

https://documentation.suse.com/suma/4.3/en/suse-manager/specialized-guides/salt/salt-formulas-custom.html

https://opensuse.github.io/fuel-ignition/

Join this project

Looking for hackers with the skills:

salt ignition json slemicro combustion uyuni susemanager

This project is part of:

Hack Week 23

Activity

  • almost 2 years ago: ygutierrez liked this project.
  • almost 2 years ago: dgedon liked this project.
  • almost 2 years ago: amunoz liked this project.
  • almost 2 years ago: admehmood liked this project.
  • almost 2 years ago: dvosburg started this project.
  • almost 2 years ago: dvosburg added keyword "susemanager" to this project.
  • almost 2 years ago: dvosburg added keyword "salt" to this project.
  • almost 2 years ago: dvosburg added keyword "ignition" to this project.
  • almost 2 years ago: dvosburg added keyword "json" to this project.
  • almost 2 years ago: dvosburg added keyword "slemicro" to this project.
  • almost 2 years ago: dvosburg added keyword "combustion" to this project.
  • almost 2 years ago: dvosburg added keyword "uyuni" to this project.
  • almost 2 years ago: dvosburg originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    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

    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