Project Description

Inspired by one of the proposals for GSoC and given that I'm usually working on maintenance updates for SUSE Manager - Uyuni I decided to translate it to Italian. :)

Goal for this Hackweek

Given the amount of strings to be translated I'll focus on the product, leaving the user guides for the next future.

Resources

Some more details are available also here:

Looking for hackers with the skills:

uyuni localization

This project is part of:

Hack Week 20

Activity

  • over 4 years ago: j_renner liked this project.
  • over 4 years ago: pagarcia liked this project.
  • almost 5 years ago: dfaggioli liked this project.
  • almost 5 years ago: franjsco liked this project.
  • almost 5 years ago: franjsco joined this project.
  • almost 5 years ago: gboiko liked this project.
  • almost 5 years ago: juliogonzalezgil liked this project.
  • almost 5 years ago: deneb_alpha started this project.
  • almost 5 years ago: deneb_alpha added keyword "uyuni" to this project.
  • almost 5 years ago: deneb_alpha added keyword "localization" to this project.
  • almost 5 years ago: deneb_alpha originated this project.

  • Comments

    • deneb_alpha
      almost 5 years ago by deneb_alpha | Reply

      There are already some translation provided but several are also outdated.

      For hackweek I'm planning to start with the untranslated strings and, when ended, to review the old existing strings.

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      WebUI

      • Java -> 349 strings to be translated

      • deneb_alpha
        over 4 years ago by deneb_alpha | Reply

        • https://github.com/uyuni-project/uyuni/pull/3456

        • deneb_alpha
    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      Looks like we still have some references to SUSE Studio: like here

      • deneb_alpha
        over 4 years ago by deneb_alpha | Reply

        reported: https://github.com/SUSE/spacewalk/issues/14377

    • deneb_alpha
    • deneb_alpha
    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      something went wrong... :(

      Note to self, when tired, have a break ;)

      I translated by mistake a variable

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      translations still ongoing...

      This day two seems to be harder. The translations units I'm handling today are not easy to be translated to Italian in a meaningful way. Some strings are also extremely short or with a lot of code tag. SUMA folks gave me access to a demo instance for having the strings context a little bit easier to get. Moving forward checking carefully for avoiding to break tags and other parts that should not be translated

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      tracking here as replies the commits already on master

      • deneb_alpha
      • deneb_alpha
        over 4 years ago by deneb_alpha | Reply

      • deneb_alpha
        over 4 years ago by deneb_alpha | Reply

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      here we go... :)

      This component https://l10n.opensuse.org/projects/uyuni/java/it/ is done. waiting to see it merged.

      Moving to the next.

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      also the component https://l10n.opensuse.org/projects/uyuni/java-database/it/ is done. :)

      moving to the next!

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      good progress for today and in parallel I have also done some reviews of existing translations trying to use the same working in similar context.

      The route is still long but the trip is exciting! :)

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      I'll take some notes here on things that should be checked and refined for a better and meaningful translation

      • deneb_alpha
        over 4 years ago by deneb_alpha | Reply

        • Working on a common glossary
        • Errata -> better to use patch. it's used in Italian

    • deneb_alpha
      over 4 years ago by deneb_alpha | Reply

      Collecting here via replies the different issues I reported.

    Similar Projects

    Ansible to Salt integration by vizhestkov

    Description

    We already have initial integration of Ansible in Salt with the possibility to run playbooks from the salt-master on the salt-minion used as an Ansible Control node.

    In this project I want to check if it possible to make Ansible working on the transport of Salt. Basically run playbooks with Ansible through existing established Salt (ZeroMQ) transport and not using ssh at all.

    It could be a good solution for the end users to reuse Ansible playbooks or run Ansible modules they got used to with no effort of complex configuration with existing Salt (or Uyuni/SUSE Multi Linux Manager) infrastructure.

    Goals

    • [v] Prepare the testing environment with Salt and Ansible installed
    • [v] Discover Ansible codebase to figure out possible ways of integration
    • [v] Create Salt/Uyuni inventory module
    • [v] Make basic modules to work with no using separate ssh connection, but reusing existing Salt connection
    • [v] Test some most basic playbooks

    Resources

    GitHub page

    Video of the demo


    Uyuni Saltboot rework by oholecek

    Description

    When Uyuni switched over to the containerized proxies we had to abandon salt based saltboot infrastructure we had before. Uyuni already had integration with a Cobbler provisioning server and saltboot infra was re-implemented on top of this Cobbler integration.

    What was not obvious from the start was that Cobbler, having all it's features, woefully slow when dealing with saltboot size environments. We did some improvements in performance, introduced transactions, and generally tried to make this setup usable. However the underlying slowness remained.

    Goals

    This project is not something trying to invent new things, it is just finally implementing saltboot infrastructure directly with the Uyuni server core.

    Instead of generating grub and pxelinux configurations by Cobbler for all thousands of systems and branches, we will provide a GET access point to retrieve grub or pxelinux file during the boot:

    /saltboot/group/grub/$fqdn and similar for systems /saltboot/system/grub/$mac

    Next we adapt our tftpd translator to query these points when asked for default or mac based config.

    Lastly similar thing needs to be done on our apache server when HTTP UEFI boot is used.

    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

    Outcome


    Set Up an Ephemeral Uyuni Instance by mbussolotto

    Description

    To test, check, and verify the latest changes in the master branch, we want to easily set up an ephemeral environment.

    Goals

    • Create an ephemeral environment manually
    • Create an ephemeral environment automatically

      Resources

    • https://github.com/uyuni-project/uyuni

    • https://www.uyuni-project.org/uyuni-docs/en/uyuni/index.html


    Enhance setup wizard for Uyuni by PSuarezHernandez

    Description

    This project wants to enhance the intial setup on Uyuni after its installation, so it's easier for a user to start using with it.

    Uyuni currently uses "uyuni-tools" (mgradm) as the installation entrypoint, to trigger the installation of Uyuni in the given host, but does not really perform an initial setup, for instance:

    • user creation
    • adding products / channels
    • generating bootstrap repos
    • create activation keys
    • ...

    Goals

    • Provide initial setup wizard as part of mgradm uyuni installation

    Resources