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 3 years ago: j_renner liked this project.
  • over 3 years ago: pagarcia liked this project.
  • over 3 years ago: dfaggioli liked this project.
  • over 3 years ago: franjsco liked this project.
  • over 3 years ago: franjsco joined this project.
  • over 3 years ago: gboiko liked this project.
  • over 3 years ago: juliogonzalezgil liked this project.
  • over 3 years ago: deneb_alpha started this project.
  • over 3 years ago: deneb_alpha added keyword "uyuni" to this project.
  • over 3 years ago: deneb_alpha added keyword "localization" to this project.
  • over 3 years ago: deneb_alpha originated this project.

  • Comments

    • deneb_alpha
      over 3 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 3 years ago by deneb_alpha | Reply

      WebUI

      • Java -> 349 strings to be translated

      • deneb_alpha
        over 3 years ago by deneb_alpha | Reply

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

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

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

      • deneb_alpha
        over 3 years ago by deneb_alpha | Reply

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

    • deneb_alpha
    • deneb_alpha
    • deneb_alpha
      over 3 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 3 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 3 years ago by deneb_alpha | Reply

      tracking here as replies the commits already on master

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

      • deneb_alpha
        over 3 years ago by deneb_alpha | Reply

    • deneb_alpha
      over 3 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 3 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 3 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 3 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 3 years ago by deneb_alpha | Reply

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

    • deneb_alpha
      over 3 years ago by deneb_alpha | Reply

      Collecting here via replies the different issues I reported.

    Similar Projects

    Edge Image Builder and mkosi for Uyuni by oholecek

    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


    Uyuni developer-centric documentation by deneb_alpha

    Description

    While we currently have extensive documentation on user-oriented tasks such as adding minions, patching, fine-tuning, etc, there is a notable gap when it comes to centralizing and documenting core functionalities for developers.

    The number of functionalities and side tools we have in Uyuni can be overwhelming. It would be nice to have a centralized place with descriptive list of main/core functionalities.

    Goals

    Create, aggregate and review on the Uyuni wiki a set of resources, focused on developers, that include also some known common problems/troubleshooting.

    The documentation will be helpful not only for everyone who is trying to learn the functionalities with all their inner processes like newcomer developers or community enthusiasts, but also for anyone who need a refresh.

    Resources

    The resources are currently aggregated here: https://github.com/uyuni-project/uyuni/wiki


    Create SUSE Manager users from ldap/ad groups by mbrookhuis

    Description

    This tool is used to create users in SUSE Manager Server based on LDAP/AD groups. For each LDAP/AD group a role within SUSE Manager Server is defined. Also, the tool will check if existing users still have the role they should have, and, if not, it will be corrected. The same for if a user is disabled, it will be enabled again. If a users is not present in the LDAP/AD groups anymore, it will be disabled or deleted, depending on the configuration.

    The code is written for Python 3.6 (the default with SLES15.x), but will also work with newer versions. And works against SUSE Manger 4.3 and 5.x

    Goals

    Create a python and/or golang utility that will manage users in SUSE Manager based on LDAP/AD group-membership. In a configuration file is defined which roles the members of a group will get.

    Table of contents

    Installation

    To install this project, perform the following steps:

    • Be sure that python 3.6 is installed and also the module python3-PyYAML. Also the ldap3 module is needed:

    bash zypper in python3 python3-PyYAML pip install yaml

    • On the server or PC, where it should run, create a directory. On linux, e.g. /opt/sm-ldap-users

    • Copy all the file to this directory.

    • Edit the configsm.yaml. All parameters should be entered. Tip: for the ldap information, the best would be to use the same as for SSSD.

    • Be sure that the file sm-ldap-users.py is executable. It would be good to change the owner to root:root and only root can read and execute:

    bash chmod 600 * chmod 700 sm-ldap-users.py chown root:root *

    Usage

    This is very simple. Once the configsm.yaml contains the correct information, executing the following will do the magic:

    bash /sm-ldap-users.py

    repository link

    https://github.com/mbrookhuis/sm-ldap-users


    Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

    Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

    Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines. It also manages configuration, can run audits, build image containers, monitor and much more!

    Currently there are a few distributions that are completely untested on Uyuni or SUSE Manager (AFAIK) or just not tested since a long time, and could be interesting knowing how hard would be working with them and, if possible, fix whatever is broken.

    For newcomers, the easiest distributions are those based on DEB or RPM packages. Distributions with other package formats are doable, but will require adapting the Python and Java code to be able to sync and analyze such packages (and if salt does not support those packages, it will need changes as well). So if you want a distribution with other packages, make sure you are comfortable handling such changes.

    No developer experience? No worries! We had non-developers contributors in the past, and we are ready to help as long as you are willing to learn. If you don't want to code at all, you can also help us preparing the documentation after someone else has the initial code ready, or you could also help with testing :-)

    The idea is testing Salt and Salt-ssh clients, but NOT traditional clients, which are deprecated.

    To consider that a distribution has basic support, we should cover at least (points 3-6 are to be tested for both salt minions and salt ssh minions):

    1. Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    2. Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
    3. Package management (install, remove, update...)
    4. Patching
    5. Applying any basic salt state (including a formula)
    6. Salt remote commands
    7. Bonus point: Java part for product identification, and monitoring enablement
    8. Bonus point: sumaform enablement (https://github.com/uyuni-project/sumaform)
    9. Bonus point: Documentation (https://github.com/uyuni-project/uyuni-docs)
    10. Bonus point: testsuite enablement (https://github.com/uyuni-project/uyuni/tree/master/testsuite)

    If something is breaking: we can try to fix it, but the main idea is research how supported it is right now. Beyond that it's up to each project member how much to hack :-)

    • If you don't have knowledge about some of the steps: ask the team
    • If you still don't know what to do: switch to another distribution and keep testing.

    This card is for EVERYONE, not just developers. Seriously! We had people from other teams helping that were not developers, and added support for Debian and new SUSE Linux Enterprise and openSUSE Leap versions :-)

    Pending

    FUSS

    FUSS is a complete GNU/Linux solution (server, client and desktop/standalone) based on Debian for managing an educational network.

    https://fuss.bz.it/

    Seems to be a Debian 12 derivative, so adding it could be quite easy.

    • [W] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    • [W] Onboarding (salt minion from UI, salt minion from bootstrap script, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator) --> Working for all 3 options (salt minion UI, salt minion bootstrap script and salt-ssh minion from the UI).
    • [W] Package management (install, remove, update...) --> Installing a new package works, needs to test the rest.
    • [I] Patching (if patch information is available, could require writing some code to parse it, but IIRC we have support for Ubuntu already). No patches detected. Do we support patches for Debian at all?
    • [W] Applying any basic salt state (including a formula)
    • [W] Salt remote commands
    • [ ] Bonus point: Java part for product identification, and monitoring enablement


    Automated Test Report reviewer by oscar-barrios

    Description

    In SUMA/Uyuni team we spend a lot of time reviewing test reports, analyzing each of the test cases failing, checking if the test is a flaky test, checking logs, etc.

    Goals

    Speed up the review by automating some parts through AI, in a way that we can consume some summary of that report that could be meaningful for the reviewer.

    Resources

    No idea about the resources yet, but we will make use of:

    • HTML/JSON Report (text + screenshots)
    • The Test Suite Status GithHub board (via API)
    • The environment tested (via SSH)
    • The test framework code (via files)


    Lawndon - Recycled electric mower converted into a 3D printable and autonomous hill climbing mower. by jordonleach

    Description

    Lawndon is currently a remote controlled mower built from a recycled electric push mower and modified with 3D printable parts. The main idea is to have a high torque, low power mower to be efficient and powerful enough to climb hills. Previous iterations have progressed the original idea into a 4x4 mower with printable tank tracks.

    > Continuation of lawndon project.

    Goals

    My goal this year is to begin implementing autonomous capabilities that are economical and easily reproducible without the requirement of using GNSS. I plan on utilizing UWB technology to run the triangulation necessary for automatic navigation of the mower.

    Update

    I successfully built a few mechanisms to triangulate the position of a UWB tag using 3 anchors, along with a node.js backend and Vue.js frontend to display in real-time the position of the tag related to the anchors.

    View post here: https://github.com/jordojordo/lawndon/wiki/Videos#nov-22nd-2024

    Resources

    Visit the Lawndon repository for information.