Project Description

Currently, Uyuni(SUSE Manager) offers a product migration feature, but it doesn't support migration from SLE to SLES4SAP. Users are required to run a separate script to perform this migration, which may not be ideal, especially if Uyuni is already installed. Additionally, the script's requirements vary with each service pack.

To address this, we aim to enhance SUSE Manager by incorporating a product migration feature that facilitates the transition from SLES to SLES4SAP. This feature will be seamlessly integrated into SUSE Manager using salt states, making the migration process more user-friendly and efficient.

Goal for this Hackweek

User can easily migrate their SLES to SLES4SAP using Uyuni.

Resources

Looking for hackers with the skills:

uyuni susemanager sles4sap migration

This project is part of:

Hack Week 23

Activity

  • almost 2 years ago: pschinagl started this project.
  • almost 2 years ago: dvosburg left this project.
  • almost 2 years ago: dvosburg started this project.
  • almost 2 years ago: RDiasMateus liked this project.
  • almost 2 years ago: t.huynh liked this project.
  • almost 2 years ago: ygutierrez liked this project.
  • almost 2 years ago: juliogonzalezgil liked this project.
  • almost 2 years ago: admehmood added keyword "migration" to this project.
  • almost 2 years ago: admehmood added keyword "sles4sap" to this project.
  • almost 2 years ago: admehmood added keyword "susemanager" to this project.
  • almost 2 years ago: admehmood added keyword "uyuni" to this project.
  • almost 2 years ago: admehmood originated this project.

  • Comments

    • dvosburg
      almost 2 years ago by dvosburg | Reply

      I would like to help testing this

    • pschinagl
      almost 2 years ago by pschinagl | Reply

      I initiated the original script and did it for Azure as a POC with AHB the last weeks - so happy to share my knowledge. The scripts requirement do not change - its only between 12 and 15 where you need to do additional things....

    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