Merge webui into OBS API
an invention by coolo
Updated over 6 years ago. 4 hacker ♥️.

The webui is currently the poor cousin of the OBS parts even though it's wildly used. It's a pain in the ass to code for it as there is not a API for most things you need to do - and if there is it's cumbersome to use.

E.g. the webui needs to query /configuration.xml to find out the page title. This XML contains all configurable items about the OBS including scheduler splits, architectures, ...

The general idea of this project is to make the webui an engine of the API so we can map build.opensuse.org to api.opensuse.org/webui and be done with it. The webui engine then can make use of the API models in their beauty, also removing code duplication.

Looking for hackers with the skills:

ruby

This project is part of:

Hack Week 10

Activity

  • almost 12 years ago: srinidhi liked this project.
  • about 12 years ago: hennevogel liked this project.
  • about 12 years ago: ralfflaxa liked this project.
  • about 12 years ago: dmdiss liked this project.
  • about 12 years ago: coolo added keyword "ruby" to this project.
  • about 12 years ago: coolo started this project.
  • about 12 years ago: coolo originated this project.


    • Comments

    • coolo
      about 12 years ago by coolo | Reply

      https://github.com/coolo/open-build-service/compare/new_webui?expand=1 shows the current state - no single test passes :)

    • coolo
      about 12 years ago by coolo | Reply

      the idea is to finish integrating the webui below /webui2, then remove the need of the webui controllers and after that remount to /webui

    • coolo
      about 12 years ago by coolo | Reply

      The webui is dead - long live the webui engine :)

      OK, not for so long actually, the end goal is having one rails app to rule them all.

    • coolo
      about 12 years ago by coolo | Reply

      Details: http://lists.opensuse.org/opensuse-buildservice/2013-10/msg00086.html

    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:

    1. Analyze & Identify: Dive into the SUSE/rmt Ruby codebase to identify and map out the exact critical path for server registration (e.g., controllers, services, database interactions).
    2. Develop in Rust: Implement a functionally equivalent version of this registration logic in Rust.
    3. 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-sys or magnus.
    4. 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.
    5. 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
    • Benchmarking Tools:
      • k6 (https://k6.io/)
      • ab (ApacheBench)

    Recipes catalog and calculator in Rails 8 by gfilippetti

    My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.

    TO DO

    • Index page
    • Product page
    • Admin area -- Supplies calculator based on orders -- Orders notification
    • Authentication
    • Payment
    • Deployment

    Day 1

    As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.

    Day 2

    Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.

    Hackweek 24

    For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.

    Day 1