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:
This project is part of:
Hack Week 20
Activity
Comments
-
over 4 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.
-
over 4 years ago by deneb_alpha | Reply
WebUI
- Java -> 349 strings to be translated
-
over 4 years ago by deneb_alpha | Reply
Looks like we still have some references to SUSE Studio: like here
-
-
-
-
over 4 years ago by deneb_alpha | Reply
something went wrong... :(
Note to self, when tired, have a break ;)
-
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
-
-
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.
-
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!
-
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! :)
-
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
-
over 4 years ago by deneb_alpha | Reply
- Working on a common glossary
- Errata -> better to use patch. it's used in Italian
-
-
over 4 years ago by deneb_alpha | Reply
Collecting here via replies the different issues I reported.
-
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.
Nah, let's be honest 
AI helped a lot to vibe code a good part of the Ruby methods of the Test framework, moving them to Typescript, along with the migration from Capybara to Playwright. I've been using "Cline" as plugin for WebStorm IDE, using Gemini API behind it.
Goals
- Migrate Core tests including Onboarding of clients
- Improve test reliabillity: Measure and confirm a significant reduction of flakiness.
- Implement a robust framework: Establish a well-structured and reusable Playwright test framework using the CucumberJS
Resources
- Existing Uyuni Test Framework (Cucumber Ruby + Capybara + Selenium)
- My Template for CucumberJS + Playwright in TypeScript
- Started Hackweek Project
Uyuni read-only replica by cbosdonnat
Description
For now, there is no possible HA setup for Uyuni. The idea is to explore setting up a read-only shadow instance of an Uyuni and make it as useful as possible.
Possible things to look at:
- live sync of the database, probably using the WAL. Some of the tables may have to be skipped or some features disabled on the RO instance (taskomatic, PXT sessions…)
- Can we use a load balancer that routes read-only queries to either instance and the other to the RW one? For example, packages or PXE data can be served by both, the API GET requests too. The rest would be RW.
Goals
- Prepare a document explaining how to do it.
- PR with the needed code changes to support it
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
Set Uyuni to manage edge clusters at scale by RDiasMateus
Description
Prepare a Poc on how to use MLM to manage edge clusters. Those cluster are normally equal across each location, and we have a large number of them.
The goal is to produce a set of sets/best practices/scripts to help users manage this kind of setup.
Goals
step 1: Manual set-up
Goal: Have a running application in k3s and be able to update it using System Update Controler (SUC)
- Deploy Micro 6.2 machine
Deploy k3s - single node
- https://docs.k3s.io/quick-start
Build/find a simple web application (static page)
- Build/find a helmchart to deploy the application
Deploy the application on the k3s cluster
Install App updates through helm update
Install OS updates using MLM
step 2: Automate day 1
Goal: Trigger the application deployment and update from MLM
- Salt states For application (with static data)
- Deploy the application helmchart, if not present
- install app updates through helmchart parameters
- Link it to GIT
- Define how to link the state to the machines (based in some pillar data? Using configuration channels by importing the state? Naming convention?)
- Use git update to trigger helmchart app update
- Recurrent state applying configuration channel?
step 3: Multi-node cluster
Goal: Use SUC to update a multi-node cluster.
- Create a multi-node cluster
- Deploy application
- call the helm update/install only on control plane?
- Install App updates through helm update
- Prepare a SUC for OS update (k3s also? How?)
- https://github.com/rancher/system-upgrade-controller
- https://documentation.suse.com/cloudnative/k3s/latest/en/upgrades/automated.html
- Update/deploy the SUC?
- Update/deploy the SUC CRD with the update procedure
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