Why a Dashboard?

In the YaST team we use quite a lot of external or internal services like GitHub, Travis, Jenkins, Open Build Service, Bugzilla, Trello,... It is too difficult and time consuming to track all those tools and get an overview what is OK, what failed and what actions should we take to resolve the problems.

Ideally there should be a tool which collects the status from all services and provides a summary page with all relevant information at one place.

Additionally it should not only report the found problems but also propose a solution so non-expert developers have a hint what needs to be fixed and how (if possible).

Generic Dashboard

The goal is to have the dashboard generic so the other teams could easily change the used services and their parameters (like which users to watch in bugzilla) and reuse the tool without much effort. This could also enable the cooperation with the other teams and increase the amount of possible developers for the project.

The Prototype

There already exists a prototype application, deployed here (this public instance does not contain any credentials, it can only see the publicly available services and their publicly available data, i.e. no internal bug reports).

Features

Ruby on Rails application with Postgres DB and nginx web server (in the production mode)
Includes a Docker configuration for easy development/deployment
The UI is based on the Gentellela template
Includes a simple Jenkins log analyzer which proposes solutions for known error patterns (live page)
See more details in the README

TODO

Collect the requirements for this service
Collect the list of services which we should watch
For each service collect which attributes or values which are important to track
The UI Design
- How to present the data at the summary page?
- How to make it easily readable?
- How to easily recognize the required actions?
Add more status analyzers to propose actions for the other services
Make the application easily configurable
Think how to pass and store the sensitive data (passwords, access tokens) securely

=================================================================================

No Hackers yet

Join this project Leave this project

Looking for hackers with the skills:

rubyonrails webapps css javascript ruby docker

This project is part of:

Hack Week 16

Activity

over 7 years ago: jordimassaguerpla liked this project.

over 7 years ago: mvidner liked this project.

over 7 years ago: deneb_alpha liked this project.

over 7 years ago: ancorgs liked this project.

over 7 years ago: hennevogel liked this project.

over 7 years ago: david_kang liked this project.

over 7 years ago: teclator liked this project.

over 7 years ago: lslezak added keyword "ruby" to this project.

over 7 years ago: lslezak added keyword "docker" to this project.

over 7 years ago: lslezak added keyword "rubyonrails" to this project.

over 7 years ago: lslezak added keyword "webapps" to this project.

over 7 years ago: lslezak added keyword "css" to this project.

over 7 years ago: lslezak added keyword "javascript" to this project.

over 7 years ago: lslezak originated this project.

Comments

Be the first to comment!

Similar Projects

rubyonrails

Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse

Description

"LDAP mode is not official supported by OBS!". See: config/options.yml.example#L100-L102

However, there is an RSpec file which tests LDAP mode in OBS. These tests use the ruby-ldap rubygem, mocking the results returned by a LDAP server.

The ruby-ldap rubygem seems no longer maintaned, and also prevents from updating to a more recent Ruby version. A good alternative is to replace it with the net-ldap rubygem.

Before replacing the ruby-ldap rubygem, we should modify the tests so the don't mock the responses of a LDAP server. Instead, we should modify the tests and run them against a real LDAP server.

Goals

Goals of this project:

Modify the RSpec tests and run them against a real LDAP server
Replace the net-ldap rubygem with the ruby-ldap rubygem

Achieving the above mentioned goals will:

Permit upgrading OBS from Ruby 3.1 to Ruby 3.2
Make a step towards officially supporting LDAP in OBS.

Resources

Replace ruby-ldap rubygem with net-ldap

webapps

WebUI for your data by avicenzi

A single place to view every bit of data you have.

Problem

You have too much data and you are a data hoarder.

Family photos and videos.
Lots of eBooks, TV Shows, Movies, and else.
Boxes full of papers (taxes, invoices, IDs, certificates, exams, and else).
Bank account statements (multiple currencies, countries, and people).

Maybe you have some data on S3, some on your NAS, and some on your local PC.

How do you get it all together?
How do you link a bank transaction to a product invoice?
How to tag any object type and create a collection out of it (mix videos, photos, PDFs, transactions)?
How to store this? file/folder structure does not work, everything is linked together

Project Description

The idea is a place where you can throw all your data, photos, videos, documents, binaries, and else.

Create photo albums, document collections, add tags across multiple file-formats, link content, and else.

The UI should be easy to use, where the data is not important for now (could be all S3 or local drive).

Similar proposals

The closest I found so far is https://perkeep.org/, but this is not what I'm looking for.

Goal for this Hackweek

Create a web UI, in Svelte ideally, perhaps React.

It should be able to show photos and videos at least.

Resources

None so far, this is just an idea.

Cobbler Angular Web Interface by SchoolGuy

Project Description

The old Cobbler webinterface was built into the server, leading to a huge dependency stack only required for a few people.

Goal for this Hackweek

The project should aim to finalize the first prototype of the new Angular based web interface.

A secondary goal of this hackweek is to learn a lot of Angular.

Update for Hackweek 24

The GH project received some traction since I have some vacation. As such it is my aim to get a first alpha released to close the milestone 0.0.1 (or whatever version I can release with semantic release).

Resources

javascript

Try to render Agama in a TUI browser by ancorgs

Description

Agama is a new Linux installer that will be very likely used for SLES 16. It offers a modern and convenient web interface that can be executed both locally and remotely.

But of course some users will miss the old TUI (ncurses) interface of the YaST installer.

So I want to experiment whether would it be possible to render a simplified version of the web interface for TUI browsers. That's only doable and maintainable if we keep the current technology stack we use for rendering the full-blown page, simply replacing complicated UI elements with others that are easy to render. That means the browser would need to support Javascript.

Chawan seems to be almost there regarding support for Javascript, XHR and related technologies. But according to this conversation, the next missing piece would be to support recursive import of module script tags.

Unfortunately, Chawan is written in Nim and I'm pretty sure a week is not enough time for me to learn Nim, implement the feature at Chawan and then fix whatever is the next obstacle on the Agama side.

But if someone could take care of the Nim part, I would do the same with the Agama one. So this is basically a call for help to get this project even started.

Editor mode at Agama web interface by ancorgs

Description

Agama is a new Linux installer that will be very likely used for SLES 16.

It takes a configuration (in JSON format) as input. And offers several interfaces to build that configuration in an easy and interactive way.

I was considering the possibility to add to the web interface a "text editor" mode similar to the XML editor available at virt-manager. That could be used to see how the changes in the UI translate into changes on the configuration.

Goals

Refresh my knowledge about UI development for Agama, since there was a major overhaul recently (adopting TanStack Query) and I need to learn the new way to do things.
Please hackers who always want to know how things work internally. :-)

obs-service-vendor_node_modules by cdimonaco

Description

When building a javascript package for obs, one option is to use https://github.com/openSUSE/obs-service-node_modules as source service to get the project npm dependencies available for package bulding.

obs-service-vendornodemodules aims to be a source service that vendors npm dependencies, installing them with npm install (optionally only production ones) and then creating a tar package of the installed dependencies.

The tar will be used as source in the package building definitions.

Goals

Create an obs service package that vendors the npm dependencies as tar archive.
Maybe add some macros to unpack the vendor package in the specfiles

Resources

Agama installer on-line demo by lslezak

Description

The Agama installer provides a quite complex user interface. We have some screenshots on the web page but as it is basically a web application it would be nice to have some on-line demo where users could click and check it live.

The problem is that the Agama server directly accesses the hardware (storage probing) and loads installation repositories. We cannot easily mock this in the on-line demo so the easiest way is to have just a read-only demo. You could explore the configuration options but you could not change anything, all changes would be ignored.

The read-only demo would be a bit limited but I still think it would be useful for potential users get the feeling of the new Agama installer and get familiar with it before using in a real installation.

As a proof of concept I already created this on-line demo.

The implementation basically builds Agama in two modes - recording mode where it saves all REST API responses and replay mode where it for the REST API requests returns the previously recorded responses. Recording in the browser is inconvenient and error prone, there should be some scripting instead (see below).

Goals

Create an Agama on-line demo which can be easily tested by users
The Agama installer is still in alpha phase and in active development, the online demo needs to be easily rebuilt with the latest Agama version
Ideally there should be some automation so the demo page is rebuilt automatically without any developer interactions (once a day or week?)

TODO

Use OpenAPI to get all Agama REST API endpoints, write a script which queries all the endpoints automatically and saves the collected data to a file (see this related PR).
Write a script for starting an Agama VM (use libvirt/qemu?), the script should ensure we always use the same virtual HW so if we need to dump the latest REST API state we get the same (or very similar data). This should ensure the demo page does not change much regarding the storage proposal etc...
Fix changing the product, currently it gets stuck after clicking the "Select" button.
Move the mocking data (the recorded REST API responses) outside the Agama sources, it's too big and will be probably often updated. To avoid messing the history keep it in a separate GitHub repository
Allow changing the UI language
Display some note (watermark) in the page so it is clear it is a read-only demo (probably with some version or build date to know how old it is)
Automation for building new demo page from the latest sources. There should be some check which ensures the recorded data still matches the OpenAPI specification.

Changing the UI language

This will be quite tricky because selecting the proper translation file is done on the server side. We would probably need to completely re-implement the logic in the browser side and adapt the server for that.

Also some REST API responses contain translated texts (storage proposal, pattern names in software). We would need to query the respective endpoints in all supported languages and return the correct response in runtime according to the currently selected language.

Resources

Agama Expert Partitioner by joseivanlopez

Description

Agama is a new Linux installer that will be very likely used for SLES 16.

It offers an UI for configuring the target system (language, patterns, network, etc). One of the more complex sections is the storage configuration, which is going to be revamped. This project consists on exploring the possibility of having something similar to the YaST Expert Partitioner for Agama.

Goals

Explore different approaches for the storage UI in Agama.

ruby

Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse

Description

"LDAP mode is not official supported by OBS!". See: config/options.yml.example#L100-L102

However, there is an RSpec file which tests LDAP mode in OBS. These tests use the ruby-ldap rubygem, mocking the results returned by a LDAP server.

The ruby-ldap rubygem seems no longer maintaned, and also prevents from updating to a more recent Ruby version. A good alternative is to replace it with the net-ldap rubygem.

Before replacing the ruby-ldap rubygem, we should modify the tests so the don't mock the responses of a LDAP server. Instead, we should modify the tests and run them against a real LDAP server.

Goals

Goals of this project:

Modify the RSpec tests and run them against a real LDAP server
Replace the net-ldap rubygem with the ruby-ldap rubygem

Achieving the above mentioned goals will:

Permit upgrading OBS from Ruby 3.1 to Ruby 3.2
Make a step towards officially supporting LDAP in OBS.

Resources

Replace ruby-ldap rubygem with net-ldap

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

docker

Migrate from Docker to Podman by tjyrinki_suse

Description

I'd like to continue my former work on containerization of several domains on a single server by changing from Docker containers to Podman containers. That will need an OS upgrade as well as Podman is not available in that old server version.

Goals

Update OS.
Migrate from Docker to Podman.
Keep everything functional, including the existing "meanwhile done" additional Docker container that is actually being used already.
Keep everything at least as secure as currently. One of the reasons of having the containers is to isolate risks related to services open to public Internet.
Try to enable the Podman use in production.
At minimum, learn about all of these topics.
Optionally, improve Ansible side of things as well...

Resources

A search engine is one's friend. Migrating from Docker to Podman, and from docker-compose to podman-compose.