The problem I typically find very hard to figure out in the whole SUSE company who is the go-to guy for a certain skill/knowledge/experience. I'd like to have some place where one, who does not know people around him, can just browse and search for people by some tag or label. Sometimes you have a problem in a specific area but you don't know who to ask to, or even if you do, you don't know there were many other people with the same knowledge/experience you could have ask before.
The idea Getting inspired by GitHub/GitLab issues and labels, we could have a website with all SUSE employees and a list of assigned tags as a property to look up for people with a certain knowledge/experience.
The solution - a web page with all the SUSE employees - a list of tags and the possibility to create new tags - a single page per each employee - a list of assigned tags for a single profile - a toolbox in the single profile page where to add an existing tag, or create a new one and assign it to the profile. Let the people freely assign tags to people profiles (if I know you know something, I will add the tag to you and you can be visible and reachable by that tech area) - a global search-by-tag box to add the possibility to look for people by the list of existing tags, or by a partial match with the inserted text.
Use case example Let's say we have { tags : [java, javascript, cloud, python, perl, suse manager, network, obs, jenkins, licenses, ruby, ....] } and I look for "java", then the search result should include all people with both the java and the javascript tag.
It frequently happen that we have the same problem in different products, but we solve it in different ways because we don't know the each other problem exists or it has been already solved. This feature could be very useful, especially for asking for help or ideas.
No Hackers yet
This project is part of:
Hack Week 17
Activity
Comments
Similar Projects
RMT.rs: High-Performance Registration Path for RMT using Rust by gbasso
Description
The SUSE Repository Mirroring Tool (RMT) is a critical component for managing software updates and subscriptions, especially for our Public Cloud Team (PCT). In a cloud environment, hundreds or even thousands of new SUSE instances (VPS/EC2) can be provisioned simultaneously. Each new instance attempts to register against an RMT server, creating a "thundering herd" scenario.
We have observed that the current RMT server, written in Ruby, faces performance issues under this high-concurrency registration load. This can lead to request overhead, slow registration times, and outright registration failures, delaying the readiness of new cloud instances.
This Hackweek project aims to explore a solution by re-implementing the performance-critical registration path in Rust. The goal is to leverage Rust's high performance, memory safety, and first-class concurrency handling to create an alternative registration endpoint that is fast, reliable, and can gracefully manage massive, simultaneous request spikes.
The new Rust module will be integrated into the existing RMT Ruby application, allowing us to directly compare the performance of both implementations.
Goals
The primary objective is to build and benchmark a high-performance Rust-based alternative for the RMT server registration endpoint.
Key goals for the week:
- Analyze & Identify: Dive into the
SUSE/rmtRuby codebase to identify and map out the exact critical path for server registration (e.g., controllers, services, database interactions). - Develop in Rust: Implement a functionally equivalent version of this registration logic in Rust.
- Integrate: Explore and implement a method for Ruby/Rust integration to "hot-wire" the new Rust module into the RMT application. This may involve using FFI, or libraries like
rb-sysormagnus. - Benchmark: Create a benchmarking script (e.g., using
k6,ab, or a custom tool) that simulates the high-concurrency registration load from thousands of clients. - Compare & Present: Conduct a comparative performance analysis (requests per second, latency, success/error rates, CPU/memory usage) between the original Ruby path and the new Rust path. The deliverable will be this data and a summary of the findings.
Resources
- RMT Source Code (Ruby):
https://github.com/SUSE/rmt
- RMT Documentation:
https://documentation.suse.com/sles/15-SP7/html/SLES-all/book-rmt.html
- Tooling & Stacks:
- RMT/Ruby development environment (for running the base RMT)
- Rust development environment (
rustup,cargo)
- Potential Integration Libraries:
- rb-sys:
https://github.com/oxidize-rb/rb-sys - Magnus:
https://github.com/matsadler/magnus
- rb-sys:
- Benchmarking Tools:
k6(https://k6.io/)ab(ApacheBench)