Project Description

In this project I would like to extend the capabilities of the SLE Release Management Container. This container is used by some colleagues in the SLE Release Management team to have access to osc and other Release Management critical commands inside a container environment. This includes the beta-emails project to send our beta announcements.

Right now the container only installs the basic dependencies for the beta-emails project. But beta-emails requires further dependencies to be installed via npm and gem. These are currently executed manually, at the first run of the container. I would like to get these dependencies installed within the container build.

This will likely require a git submodule to add the up-to-date version of beta-emails in the container build environment without calling git (as it is a non-public GitLab repo, which requires user authentication).

Goal for this Hackweek

I would like to get the dependencies for beta-emails installed within the container build and remove all build dependencies for those dependencies (npm and the whole compile stack).

Resources

https://gitlab.suse.de/suntorytimed/sle-releasemanager https://gitlab.suse.de/vmoutoussamy/beta-emails

Join this project Leave this project

Looking for hackers with the skills:

beta containers docker podman npm ruby gem ci/cd

This project is part of:

Hack Week 21

Activity

over 2 years ago: jlausuch liked this project.

over 2 years ago: dgedon added keyword "gem" to this project.

over 2 years ago: dgedon added keyword "ci/cd" to this project.

over 2 years ago: dgedon added keyword "npm" to this project.

over 2 years ago: dgedon added keyword "ruby" to this project.

over 2 years ago: dgedon added keyword "beta" to this project.

over 2 years ago: dgedon added keyword "containers" to this project.

over 2 years ago: dgedon added keyword "docker" to this project.

over 2 years ago: dgedon added keyword "podman" to this project.

over 2 years ago: ybonatakis liked this project.

almost 3 years ago: dgedon liked this project.

almost 3 years ago: dgedon joined this project.

almost 3 years ago: gameboy974 joined this project.

almost 3 years ago: suntorytimed started this project.

almost 3 years ago: suntorytimed originated this project.

Comments

Be the first to comment!

Similar Projects

containers

ClusterOps - Easily install and manage your personal kubernetes cluster by andreabenini

Description

ClusterOps is a Kubernetes installer and operator designed to streamline the initial configuration and ongoing maintenance of kubernetes clusters. The focus of this project is primarily on personal or local installations. However, the goal is to expand its use to encompass all installations of Kubernetes for local development purposes.
It simplifies cluster management by automating tasks and providing just one user-friendly YAML-based configuration config.yml.

Overview

Simplified Configuration: Define your desired cluster state in a simple YAML file, and ClusterOps will handle the rest.
Automated Setup: Automates initial cluster configuration, including network settings, storage provisioning, special requirements (for example GPUs) and essential components installation.
Ongoing Maintenance: Performs routine maintenance tasks such as upgrades, security updates, and resource monitoring.
Extensibility: Easily extend functionality with custom plugins and configurations.
Self-Healing: Detects and recovers from common cluster issues, ensuring stability, idempotence and reliability. Same operation can be performed multiple times without changing the result.
Discreet: It works only on what it knows, if you are manually configuring parts of your kubernetes and this configuration does not interfere with it you can happily continue to work on several parts and use this tool only for what is needed.

Features

distribution and engine independence. Install your favorite kubernetes engine with your package manager, execute one script and you'll have a complete working environment at your disposal.
Basic config approach. One single config.yml file with configuration requirements (add/remove features): human readable, plain and simple. All fancy configs managed automatically (ingress, balancers, services, proxy, ...).
Local Builtin ContainerHub. The default installation provides a fully configured ContainerHub available locally along with the kubernetes installation. This configuration allows the user to build, upload and deploy custom container images as they were provided from external sources. Internet public sources are still available but local development can be kept in this localhost server. Builtin ClusterOps operator will be fetched from this ContainerHub registry too.
Kubernetes official dashboard installed as a plugin, others planned too (k9s for example).
Kubevirt plugin installed and properly configured. Unleash the power of classic virtualization (KVM+QEMU) on top of Kubernetes and manage your entire system from there, libvirtd and virsh libs are required.
One operator to rule them all. The installation script configures your machine automatically during installation and adds one kubernetes operator to manage your local cluster. From there the operator takes care of the cluster on your behalf.
Clean installation and removal. Just test it, when you are done just use the same program to uninstall everything without leaving configs (or pods) behind.

Planned features (Wishlist / TODOs)

Containerized Data Importer (CDI). Persistent storage management add-on for Kubernetes to provide a declarative way of building and importing Virtual Machine Disks on PVCs for

Enable the containerized Uyuni server to run on different host OS by j_renner

Description

The Uyuni server is provided as a container, but we still require it to run on Leap Micro? This is not how people expect to use containerized applications, so it would be great if we tested other host OSs and enabled them by providing builds of necessary tools for (e.g. mgradm). Interesting candidates should be:

openSUSE Leap
Cent OS 7
Ubuntu
???

Goals

Make it really easy for anyone to run the Uyuni containerized server on whatever OS they want (with support for containers of course).

Technical talks at universities by agamez

Description

This project aims to empower the next generation of tech professionals by offering hands-on workshops on containerization and Kubernetes, with a strong focus on open-source technologies. By providing practical experience with these cutting-edge tools and fostering a deep understanding of open-source principles, we aim to bridge the gap between academia and industry.

For now, the scope is limited to Spanish universities, since we already have the contacts and have started some conversations.

Goals

Technical Skill Development: equip students with the fundamental knowledge and skills to build, deploy, and manage containerized applications using open-source tools like Kubernetes.
Open-Source Mindset: foster a passion for open-source software, encouraging students to contribute to open-source projects and collaborate with the global developer community.
Career Readiness: prepare students for industry-relevant roles by exposing them to real-world use cases, best practices, and open-source in companies.

Resources

Instructors: experienced open-source professionals with deep knowledge of containerization and Kubernetes.
SUSE Expertise: leverage SUSE's expertise in open-source technologies to provide insights into industry trends and best practices.

ADS-B receiver with MicroOS by epaolantonio

I would like to put one of my spare Raspberry Pis to good use, and what better way to see what flies above my head at any time?

There are various ready-to-use distros already set-up to provide feeder data to platforms like Flightradar24, ADS-B Exchange, FlightAware etc... The goal here would be to do it using MicroOS as a base and containerized decoding of ADS-B data (via tools like dump1090) and web frontend (tar1090).

Goals

Create a working receiver using MicroOS as a base, and containers based on Tumbleweed
Make it easy to install
Optimize for maximum laziness (i.e. it should take care of itself with minimum intervention)

Resources

1x Small Board Computer capable of running MicroOS
1x RTL2832U DVB-T dongle
1x MicroSD card
https://github.com/antirez/dump1090
https://github.com/flightaware/dump1090 (dump1090 fork by FlightAware)
https://github.com/wiedehopf/tar1090

Project status (2024-11-22)

So I'd say that I'm pretty satisfied with how it turned out. I've packaged readsb (as a replacement for dump1090), tar1090, tar1090-db and mlat-client (not used yet).

Current status:

Able to set-up a working receiver using combustion+ignition (web app based on Fuel Ignition)
Able to feed to various feeds using the Beast protocol (Airplanes.live, ADSB.fi, ADSB.lol, ADSBExchange.com, Flyitalyadsb.com, Planespotters.net)
Able to feed to Flightradar24 (initial-setup available but NOT tested! I've only tested using a key I already had)
Local web interface (tar1090) to easily visualize the results
Cockpit pre-configured to ease maintenance

What's missing:

MLAT (Multilateration) support. I've packaged mlat-client already, but I have to wire it up
FlightAware support

Give it a go at https://g7.github.io/adsbreceiver/ !

Project links

Port the classic browser game HackTheNet to PHP 8 by dgedon

Description

The classic browser game HackTheNet from 2004 still runs on PHP 4/5 and MySQL 5 and needs a port to PHP 8 and e.g. MariaDB.

Goals

Port the game to PHP 8 and MariaDB 11
Create a container where the game server can simply be started/stopped

Resources

https://github.com/nodeg/hackthenet

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.

podman

Migrate from Docker to Podman by tjyrinki_suse

Description

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.

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é.