take my existing buildit.sh script (https://github.com/dmbyte/SES-scripts/blob/master/clusterbuilder/) and enhance it to be more of the installer experience needed. It would ideally be coupled with an autoyast file that does:

It would be nice to have a OS that can be tinkered with easily by having only a compiler as the only binary on the system.

openSUSE now has a lot of black magic around building distributions for :Factory and :Leap This includes all of the 000* packages and opensuse-release-tools doing very useful stuff like pkglistgen automatically managing the package lists for .kiwi files so release managers don't need to manually update which packages are going on which media

I plan to implement XEP-0308 for Profanity. Something that is asked for since 2016.

Play with kiwi and liveCd capabilities to create a Small liveCD to get a rescue and multimedia system in less than 700MB. Will be a liveCD in Full french.

tcetc

Summary

There are a number of items related to doing Virtualization CI and testing which I have a hard time getting to during my day job. I'll take Hackweek as an opportunity to get at least a little out of my normal space and improve our methods. This mainly focuses on QEMU/KVM and some of the efforts and infrastructure I've already got in various states of development, or at least investigation. Part of this effort is to try to leverage what is available in this space upstream, and to focus on watching the state of CI as it exists upstream, not just in our shipping products.

I want to set up a few small raised beds to plant some vegetables. Volunteers more than welcome-just ping me on RC.

1) Explore postmarketOS, LineageOS on real device. 2) Explore Qualcomm mainlaining effort.

So I have 469.icu :), it's currently doing nothing... (and for sale) but in the meantime, I'd like to write an url shortener from scratch and deploy it on my own server

Solid Ground[1] is a powerful software tool, essential for the daily tasks of an L3 agent. Built upon Django framework[2], it greatly simplifies the storing and management of the needed information for orchestrating the various, tedious and sometimes quite complicated actions (steps) of the L3 process[3]. And although Solid Ground is significantly benefited by the utilization of Django's ORM (and other components such as Rest, views, etc.) and has very strong command line interfaces (l3t and Django admin's shell), it lacks a modern, user friendly, clean and with nice user experience (i.e. engaging) WUI! The purpose of the current project is to leverage Bootstrap - the world’s most popular framework for building responsive, mobile-first sites[4] - in order to enhance Solid Ground's WUI without disrupting its operational capability! In other words to apply a cleaner, more engaging look and feel that will not break Solid Ground's functions.

The next release of Ceph (Octopus) will be delivered via containers.
A new tool named cephadm is being developed to bootstrap and manage Ceph containers.

The recent Banana Pi BPI-F2S board features a new Arm SoC SP7021 by Sunplus, which is not yet supported in mainline Linux. Prior to Hackweek I had prepared UART and interrupt controller drivers and Device Tree for Sunplus SP7021's Arm Cortex-A7 cores: GitHub branch f2s-next

Give a more complete overview of the infrastructure and the processes the documentation team uses to write, maintain, and publish the documentation for the SUSE products. Add missing information/chapters to the guide.

With 'pint' the Public Cloud Team already provides a command line based tool to get information about the images we're hosting in the public clouds. It's provided via the Public Cloud Module in SLE as well as in the Cloud:Tools repo. As more and more people are asking about information on the images we've published but not all of them feel comfortable using tools on the command line we like to provide a web UI which shows that data. One should be able to search for specific images, sort by regions or state etc.

Create a basic web app where you can search for Progress tickets and create Jira tickets to a certain project. Outcome:

This project aims to run VMs in a CaaSP 4 cluster using kubevirt and a libvirt+qemu container (aka compute container) based on SLES15 SP1/2. Compute containers based on openSUSE Leap15.1 and SLES15 SP1 already available in registry.opensuse.org and registry.suse.com respectively. VMs can be deployed to the cluster but there are several functional problems that need investigating, e.g. accessing the VM's serial and VNC consoles, proper network access, etc.

For a long time, I have wanted to port a card game called "26" to the digital world. I've been playing 26 since I was very young, especially in the winter months, when it was too cold to go play outside. 26 is played by 2 players. Each player has a stack of 20 cards (all face-down, except for the top card), and 6 cards in their hand. The goal of the game is to get rid of all your cards by building flushes on the board. The first player to get rid of all their cards wins.

Let's imagine you are a sales engineer. You want to either:

The current disk layout recreation code in ReaR is about 10 years old now and more and more

Hydrogen is a software drum machine and pattern editor. While it can export and play through MIDI, which is enough to play through my SR-16, it is not clear how one could record patterns and songs from Hydrogen.

With the approach of kernel 5.6 SGI Octanes are supported with builtin IO components. What's missing for a graphics workstation is a driver for the graphics card. There is already a not upstreamed framebuffer driver for Impact graphic cards. Since there will be no new framebuffer driver accepted upstream, the goal of this project is to convert the existing frame buffer driver to a DRM driver and make it ready to be sent upstream.

Learn how to develop and create some plugins/apps for rocketchat. One that comes to mind is to enhance gerrit links which all are enriched with the same text, no matter what you link. A plugin could extend those links into printing some proper info like the patch name so its easier to click on those.

I would like to set up a small backup server on my spare hardware What I have:

Be familiar with the process of writing a test case in openQA by taking a ticket from a QA team.

In a 2-node HA cluster without quorum server, since neither of the cluster nodes (partitions) has more than 50% votes in case of split-brain, we should configure corosync.conf to enable two_ndoe: 1, so that both nodes (partitions) will be granted "quorum". But there'll be potential fencing matches which could introduce double-fencing by chances. The current solution is using random/static fencing delays by configuring pcmk_delay_max/base parameters for stonith resources to prevent double-fencing.

CephFS is awesome, but without a VPN it's not safe to be routed over the internet, and it lacks client support on many platforms. The Linux Kernel Library allows for the linux kernel to be built as a cross-platform user-space library and integrated into a regular Android, Windows, macOS, etc. application. This project combines CephFS, LKL and wireguard, and sprinkles some io-uring on top. My objectives are:

Uyuni is an heterogeneous and giant project (actually it is a beast) made of many pieces, many languages, many internal architecture structures, and also very old and new technologies live in it. Said that, and based on the fact Uyuni delivers tons of features/functionalities not all the end users use, it is not trivial at all to understand

Based on an old customer feature request: zypper history command options so that it can show the security patches installed on a server and when they were installed, during a defined period of time.

There is always something to do if you run the infrastructure for such a big project like openSUSE.... Our Admin wiki currently lists over 80 machines - and while we already "salted" some of them, there is always room for improvement and room to learn something new just by making your hands dirty and diving into the administrator role for a machine.

Simplify the codebase by using a more modern toolkit to accelerate maintenance and future development. Enjoy Hakkaweek!

There is a number of annoyances and pending improvements when working with the Salt Formula for provisioning Prometheus Exporters in Uyuni: - Fix issue with cleanup in case the monitoring entitlement is removed.

Recently, ConnMan got support for iwd and WireGuard. The current support is only a starting point and it needs some more changes in the core code base to support the cool features:

Continue improving my personal project, bard. Bard is a music manager for your music. It stores all information about your music collection in a Postgresql database . The current release can be used from a terminal and has the following working features:

Idea is to write FF plugin which would process raw autoinst log and display it in more readable form .

I started Standford's machine learning course but after getting stuck in one assignment (ex4, Week5), it fell of the table due to lack of time and focus. I will use this Hack Week to make some progress on it.

Summary Using K8s for managing VMs is a requirement in many environments, as not all applications are designed to be cloud-ready. Some projects like Kubevirt[1] and Virlet [2] aim to address this requirement. However, they introduce their own complexity, creating a parallel control plane for VMs. RancherVM [3] has a different approach, launching VMs as pods, but requires custom-built images.

I would like to learn and play with RL/ML and Go ( gorgonia for example). The lack of Reinforcement Learning library in Golang makes me very sad, so I wanted to implement a RL algorithm and alongside create a small library for RL and go in general. On the other hand, I would like also to expand and add features on a project that I'm working on: https://github.com/mudler/luet . It's a package manager based on containers, focused on cloud/OTA-alike update delivery. It would be nice to combine the two ideas, for e.g. to achieve one feature.

https://gitlab.suse.de/l3ms/RES-weather/ needs some improvements, e.g. manual generation of statistics and reports.

• Check and verify SGML tools
• Parse and validate mostly markup-less files with SGML tools

Very often people find themselves wanting to store secrets in a way that either they can recover even if (for instance) their house burns down, or allow friends and family to recover if they pass away. Existing solutions to this problem are: * Too complicated to use for ordinary people.

GNOME Software supports distribution upgrade, that only requires a few clicks for upgrading your system. But it's not integrated into Leap. So this is that I plan to do this Hack Week.

Involved components

Zero-ish downtime deploy on da cheap!

This project aims to get a 0-ish downtime deployments (very easily achievable with Kubernetes) just using:

At present it is our practice to "vendor" all dependencies for a Golang package. This has the advantage that everything is in one nice package and self contained but it has the disadvantage that dependencies are hidden and therefore security issues may slip through the cracks. The idea is to investigate and create automation "go2rpm" that generates a spec file with the necessary "BuildRequires:" such that the dependencies can be broken into golang- packages and we get rid of the implicit dependency inclusion via "vendor". The potential problem is scale, with some golang applications having thousands of dependencies.

Mash is a Python based CI/CD pipeline for automated testing and publishing of public cloud images. Currently the production and development deployment for the package is inconsistent, slow and manual. This is a barrier to rapid development, deployment and testing. It also means the development workflow is different than production. This can lead to production issues which were not seen during development. In order to modernize the Mash workflow I plan to spend the week digging into a plethora of tools to first learn then build out a new workflow. The goal is to simplify deployment by choosing tools that provide consistency, modularity and repeatability. By leveraging the best tools available we can harden the code and accelerate the release cycle.

Future of tools supporting editors in dealing with particular languages is in my opinion in the LSP protocol. Therefore I look with a bit of worry on the fact that there is no good LSP server based on the top of rope. python-language-server uses it a bit internally, the Microsoft Language Server for Python is in C#, so it is completely something different. The goal of this project is to write a very simple nucleus of the LSP server based solely on rope for the language analysis and actions, which would be at least able to do “jump to the definition of a symbol”.

Well, we often stuck in YaST team with knowledge what users really use and how much. But we have yast logs in many bug reports. And from those logs we can see which modules users use the most. So goal of this project is to write script that analyze given tarballs with logs and print result about usage of yast clients.

There are various home assistant solutions out there but all of them transfer your voice to some server for processing. This is a no-go for sane people although the technology is interesting and could be useful. There are various open source tools out there to achieve the same result but there is no turn key open source self hosted solution. The goal of this project is to implement a way to have a home assistant running locally - ideally with one command. The project that is closer to the desired result is Mycroft (https://mycroft.ai/). It is very easy to run the client side components using one docker command but their backend is running remotely. All the tools they use though are open source so it only needs one to do the work and package them in a nice little docker-compose file (https://mycroft-ai.gitbook.io/docs/about-mycroft-ai/faq#can-mycroft-run-completely-offline-can-i-self-host-everything).

Finglonger is an internal tool used by the SUSE Manager team intended to make the life of the Round Robin Bug Guy easier. It was originally written by @fkobzik in Clojure. This is an attempt to learn some Go by reimplementing Finglonger.

define data types to collect informations about cameras and lenses to have a shared data store for lensfun and photo editors. Current state:

Libyui REST API

In the previous hack week project I was focused on implementing a REST API for testing the YaST modules.

****The motivation is create a open source solution, base on this business astronomy products: AZWO Asiair

I recently bought a Lioncast LK200 RGB keyboard which is a nice piece of hardware and has exactly the look and feel I want. All basic functions work well under Linux. Unfortunately the manufacturer only provides user software to upload/download profiles and control the LEDs for Windows. The device can be configured and operates autonomously from any OS but color setup is a PITA and it's very easy to factory-reset, and lose all config. I approached them but Lioncast seems neither interested to support native Linux nor to provide protocol specs so one can implement it. I thought to take this as an example to learn about reading and reverse-engineering USB device software.

SUSE CaaS Platform is a Cloud-Native Computing Foundation (CNCF) certified Kubernetes distribution. - Family with SUSE CaaS Platform

Overview

uMEC (aka MicroMEC, or Micro-MEC) is a project under the Akraino Edge umbrella. SUSE joined in 2019 and together with partners we managed to create the 1st prototype infrastructure.

DevOps teams face double sided challenges: development tasks should be planable and maintenance tasks should maintain their flow to provide maximum value through the queue. Build a prototype JIRA project to help them organize their workload with a Scrum board for their development tasks and a Kanban board for their maintenance work, all fed from a common backlog.

SUSE is using OBS as a build system and openQA for automated testing purposes. The goal of the study is to find out the strengths and weaknesses of these systems and compare them to other open source alternatives in a structured way.

The plan is to start working towards a rewrite of xdg-utils in python, focusing on the really bad bits such as dealing with desktop files and mime handling. In this hackweek, I want to split python-xdg into multiple libraries such as python-mime and python-desktop file and prepare them to be used in helper binaries to handle some of the more complex tasks currently done in shell.

The Maintenance Coordination, Security and Quality Assurance department documentation is organized and handled on Confluence and there are several pages and how-to available for new team members or other colleagues searching for more information. The processes and workflow documentation is a key asset for on-boarding quickly new employees and for improving existing workflows.

As per the title I am aiming to investigate a much nicer conky default, I have a short list, but it depends on asking people nicely to license there work, if I have to create something from scratch it probably won't happen this hackweek. Now that themes such as Polycore are licensed so they are useable the aim is to build from there.

Working with some of the Linux modding communities I am aiming to make the ultimate guide / knowledge base for modifying the look and feel of your Linux install. The scope of this hackweek project is to get the initial framework set up using Jekyll with some basic content added. Further content will be added in the future.

openSUSE Leap 15.2 is currently under development and it will be released soon. We would like to bring Kubernetes support for it and offer kubeadm deployment on it. As Kubernetes cluster container images we can use images from kubic project.

I plan to summary exist knowledge in filesystem part during hackweek. And learn some more feature about btrfs/xfs/ext4. The motivation is to speed up test result review in the future.

Have a play with SUSE CAP on AWS during this hackweek.

I want to study the knowledge of openQA I will read the online documents and do some experiment in virtal-machine.

Description

Firecracker is an open-source virtualization technology that is purpose-built for creating and managing secure, multi-tenant container and function-based services.

Create a tool which will make it possible to monitor the lifecycle of pods in a kubernetes cluster (as well as other types of tabular or structured data), and provide a convenient user interface for viewing and interpreting that data. This will be useful in development and testing of our kubernetes-based container platform (Cloud Application Platform), as it will allow us to better understand where things are going wrong when we encounter component failures. * Github

GitLab provides a bridge to connect to Gitter using an IRC client. The source code is at https://gitlab.com/gitlab-org/gitter/irc-bridge/

Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

I tried to work blockchain into this, just so we could cover the trifecta of buzz words. Sadly I could not maintain saintly and do this. What do I plan on doing? a few things, so please reach out if you would be interested in any one of them. I will update with a list later.

Let's pick some old classic game, reverse engineer the data formats and game rules and write an open source engine for it from scratch. Some games from 1990s are simple enough that we could have a playable prototype by the end of the week. Write which games you'd like to hack on in the comments. Don't forget to check e.g. on Open Source Game Clones, Github and SourceForge whether the game is ported already.

The goal is to find a way for developing and simple testing an IONIC based multiplatform app with REST API on openSUSE. The focus is to find a way to secure token handling for SSO.

I'm hearing impaired. Where others have no issues following talks or dicussions, I often fail even grasp the bottom line what it's about. I've got hearing aids, but they help only so much. I also have an add-on device for my hearing aids that acts like a bluetooth headset. Unfortunately, making this thing work under my Linux desktop has been an ongoing, frustrating struggle. On the contrary, it works flawlessly with Android devices of different generations, and even with my lowly Gigaset phone. Actually, the thing works better with older kernels/Linux versions than with current TW. While I've little hope to solve the bluetooth audio issues on Linux for good, I hope at least to be able to understand better what's going wrong, and be able to slow down or even stop the deterioration I've observed lately.

ABF is a buildsystem developed by ROSA (rosalab.com) and OpenMandriva (https://www.openmandriva.org/) currently being used for their distribution. The build system is FOSS and is available to be deployed anywhere. (https://github.com/rosa-abf) (https://github.com/OpenMandrivaSoftware/docker-builder)

Take the oportunity to learn Kubernetes, to play with AWS and compare performance and availability of openQA and OBS instances and openSUSE Mirrors running on AWS. - https://aws.amazon.com/

Debian

• https://wiki.debian.org/Apache

I got a Raspberry pi 4 not long ago, I'd like to install openSUSE Leap 15.2(Alpha) on it, and set up hass - Home Assistant, a open source home automation assistant on rpi4, then have some fun with it! Update: hassio dropped py3.6 support in Dec 2019, since Leap 15.2 stays with python 3.6 rather that python 3.7, I've to use Tumbleweed instead.

The Gameshell is a small game console based on AllWinner R16 (Cortex-A7, IIRC the same CPU that the RPi2). Currently is supporting Debian, and some community member ported ArchLinux on it. The goal of the project is to port the openSUSE MicroOS distribution into the device, providing a transactional upgrade process for a canonical IoT architecture. In the process I expect to learn about ARM7, uBoot and some kernel hacking.

Many cases are Client-Server testing or Multi-Machine testing in FIPS area, I plan to hack and learn more deeply about Multi-Machine test automation in openQA. Refer to:

Create DevOps automation for testing PTFs prior to delivering to customers, that will be available to each of the team members using standard L3 tools.

Investigate possibilities for the distributed builds for Ceph to speed up builds. This task could have 2 scopes.

Learn and use tools to build/deploy SUSE/openSUSE to the KVM environment for developing kernel CVE patches and testing automation Steps :

I started 3 years ago creating a CNC, but soon last past 6 monts I realized that I could use it as a 3D printer. The software was good enough, the hardware and firmware had evolved. And now I could print 200x200x300 pieces with 0.1mm precision. But at soon I had this one finished, I decided to create a new compact, silent, light 3D printer.

Solid Ground is an essential software tool for the daily tasks of an L3 agent. A continuous integration/continuous delivery (CI/CD), and even more a continuous deployment, approach is currently missing from its development ecosystem slowing down its release cycles. Current project aspires to sketch the design principles of such approach and if possible to end up with a functional CI/CD mechanism that will be utilized in the next software releases of Solid Ground.

Put together a collection of ideas and resources to mentor people managers on how to make better decisions: - Useful mental models and how they work together

Diagnosing issues with stalling desktop application (or a whole desktop environment) is difficult these days as the application often requires multiple processes interconnected with sockets, pipes, futexes, etc. to work and often it is not clear which process is the one responsible for blocking the whole ecosystem. The idea of this project is to write a tool that gathers information about processes in the system and for each process that is sleeping display the resource (file, socket, futex) it is waiting on as well as the process that is likely responsible for unblocking (feeding pipe, sending data to socket, unlock futex, ...). Once the information is gathered, we can also plot it for graphical displaying with tools like graphviz.

This issue has been blocked for a while due to time constraints so I want to take Hackweek 19 to work on it.

Currently AWS uses a SMT solver to decide on public/non-public policies https://aws.amazon.com/blogs/security/protect-sensitive-data-in-the-cloud-with-automated-reasoning-zelkova/ Learn about SMT solvers & see how feasible using a smt solver is for supporting the more minimal policy set in ceph object storage RGW

Avahi is (among others) a domain names auto-configuration system for Linux compatible with Bonjour. The project is to dig into avahi source code to modernize it if possible and fix bugs.

transactional-update, the application to update read-only systems such as openSUSE MicroOS and openSUSE Kubic and the Transactional Server installations of openSUSE Leap, openSUSE Tumbleweed and SUSE Linux Enterprise Server, evolved from a POC to a fully fledged solution - and is currently completely written in Bash. This has been working really well in the past, but is gradually reaching its limits, especially when thinking about supporting additional file systems or ports to other Linux distributions - yes, we have a huge interest in other distributions adopting our technology. A C++ version would simplify those abstractions, but would it also make maintenance of the complete application easier? Check that as part of a POC and refresh C++ knowledge on the way there.

The idea is to hack os-autoinst-distri-opensuse infrastucture and explore design patterns that can fit. The end point of this is to restructure the framework in such a way that the main-common.pm is more efficient, functional and readable.

Once more mailprocessing has developed some bitrot, namely this recent crash: ```

Testing GUIs is hard: unit tests require a tremendous amount of mocking and often don't capture the exact user input anyway, integration tests on the other hand are difficult to setup as they often require a dedicated infrastructure with virtual machines. libuitest should become something like the image recognition part of openQA: it receives a video or image stream from some source and searches for matches (e.g. button found, sound played). It should also be able to send clicks, key presses, strings, etc. back via an abstract API to a backend.

Motivation

Running async actions in SUSE Manager lacks a user-friendly feedback. For instance, running a salt highstate on a system:

For years we have been discussing the idea to modularize SUSE Manager. This would enable developers to create their own extensions to SUSE Manager without needing to touch the core repository. There are several frameworks that could be helping in that direction. The goal here is to create a Proof of Concept with the virtualization features moved into an add-on.

Salt is moving towards a plugable architecture using POP and Idem. This project is about experimenting with those new concepts by applying them to a real life case: the virt execution and state modules. The goals of this project are:

Thinking about extending the typical Twitter app that let's a user bulk-delete their tweets (with a limit of 3200 each time). The main extension is to allow subscribers to this service to add a hashtag to their tweets that will put a time-to-delete

Why is it nice?

Learn the inner workings of TCP as implemented in the Linux kernel. This will involve * reading textbooks and IETF docs

It's not always straightforward to open a core dump originating from customer's environment, since there's a wide variety of versions of all the binaries involved - usual workflow is to install a VM with the SP that the customer is using, enable debuginfo repositories and then follow the buildid hints that gdb is providing. However this sounds like a bit of an overkill. Lately, there has been a debuginfod project announced:

Problem description Jira is used inside SUSE to track various process/workflows.

This is kinda continuation of my last hackweek project - learning python3 the parcical way. The goal is again to replace existing bash script which will generate 3 node KVM HA cluster on my workstation and automate quite a boring part of HA regression testing.

Since SUSE Manager doesn't scale out and stacking it into another pyramid of susemanagers won't help here, the real architectural changes needs to be done to achieve true scale-out of this product. This hackweek project is about how to Turn SUSE Manager into a cluster. Areas to be tackled:

Last hackweek filtra was created – a tool to extract information like lead and cycle times from Github repos for (but not limited to) projects that are doing Kanban. The collected metrics can then be visualized with Grafana. Currently there are two problems with filtra:

Features I'd like to implement: * Built in search on obs, with one-click branch checkout,

I own a 3D printer / Anet AM8 / and after 1,5y its time to upgrade the electronics, mainly the stock motherboard and get it ready for multi-color printing. Also the time has come where I would like to not only download 3D models from thingiverse but also create or customize the models for my usage. Plan is to:

The project aims to port openSUSE to the ROCKPro64. The ROCKPro64 is the most powerful Single Board Computer released by Pine64. It is powered by a Rockchip RK3399 Hexa-Core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-Bit Processor with a MALI T-860 Quad-Core GPU.

I'd like a way to have a device on my desk which lights up to indicate that I have something I should be paying attention to. Initially, I'd like this to be for Office365 calendar events and GitHub mentions, but ideally it should support arbitrary messages. The plan is to assign specific colors (ideally "patterns" consisting of a sequence of colors and time) to specific message types. I have a handful of raspberry Pi Zeroes, a couple of OLEDs, a strand of individually-addressable RGB LEDs, a power supply, and some misc electronics (like the 3.3-5v logic level shifter necessary for the 5v LED strand). I'm thinking Python is probably the way to go for the software. I'm hoping OpenSUSE actually works on the Pi zero. :D If not, there's an ESP32 with a built-in display and a few Pi 3s laying around barely used, maybe one of them will work.

Although CNCF projects are almost exclusively related to Linux containers, some ideas, like wrapping all the services into network proxies to create a distributed data-plane and enable true observability, could perhaps be explored for some kind of backport in complex legacy distributed systems, like... say... S4/HANA?! I don't even know if this is feasible, but trying won't hurt... just stand at a safe distance from the cluster!

Currently we have two sponsored 3D printers available in the Nuremberg office. Both are located in a lab - which makes it hard to access them. Both also need some (hardware) maintenance. This (hopefully short) side project should make the printers more usable and accessible for others.

This hackweek I will focus on improving my drawing/painting skills. I will do either some portrait for people I know at SUSE and this could be used as Github profiles or do something related to Linux/SUSE chameleon etc. ( without any precise goal).

The idea here is to study and understand how ephemeral storage for containers works and investigate if local storage could be avoided at all and Ceph used instead. Could new storage driver be developed to support Ceph storage:

• implement a POC deploying CaaSP v4 on top of AWS using: Spotinst's elastigroup
• "Spotinst Elastigroup predicts Spot Instances behavior, capacity trends, pricing, and interruptions rate. Whenever there’s a risk of interruption, Elastigroup acts accordingly to balance capacity up to 15 minutes ahead of time, ensuring application availability.

OSC is already available on Homebrew, but it is missing the integration with Staging as the openSUSE-release-tools are not available. In this Hackweek project I would like to get the openSUSE-release-tools running on macOS via Homebrew.

Using the camsource and vlc packages as an example. If camsource is configured to use a given dev/video[n] device with a choice of resolution in the width and height fields of a camsource conf file then if camsource is the first application to access the device captured images are as-expected. However, if an application like vlc is used for the same device (and exited) before starting camsource (e.g. to check the view from the camera before starting camsource) and if the camera supports higher resolutions than used in the camsource configuration what occurs is that camsource will not setup the camera to use the configured resolution and has a broken view of the camera output based on the vlc chosen resolution chopped to the camsource configuration. For example, with camsource configuration set to use 640x480 on a camera that supports 720x480 and vlc is used and exited before camsource is started then the captured camsource images contain two non-continuous partial image blocks with a horizontal border dividing them. I assume either vlc fails to fully reset the device configuration when exiting or camsource fails to initialize the device "from scratch" when starting. The two applications use different video device APIs but the setup and cleanup for the camera in each case is a very limited part of the application's functionality.

There's a long standing request to extend the output of dmidecode to something that would be machine-readable. Something like an XML or JSON-based format. Unfortunately this can't be implemented right now because the output of dmidecode is generated by open-coded printfs as the DMI table is being parsed, with no intermediate structures nor temporary buffers. While implementing a machine-parseable output is out of scope for a single hack week, let's remember that even the longest journey starts with a single footstep. I would like to try and rewrite the 5200 lines of code of dmidecode in such a way that printing the output would be somewhat separated from parsing the DMI table and done by a limited set of dedicated functions. Alternative output formats could later hook into such functions.

Termux is already bringing a terminal and debian package manager to Android. Let's see if we can reuse it and provide a base system with zypper and build openSUSE:Factory for it in OBS.

Background

Given the number of different demands on our time and attention, it becomes increasing hard to focus and find the 'flow state' where a developer can be most productive. Interruptions due to chat notifications, email, and updater applets all break focus. Additionally, the desktop metaphor has in most cases failed to evolve as the browser and other MDI interfaces have become the focus for many users, and increased performance has allowed us to keep more tasks running and present on the desktop at once, presenting a higher cognitive load to the user.

I would like to learn more about something outside of engineering. I have selected to learn more about marketing; something our overall team is doing more of...

Since Kubernetes already has a clear path of "in-tree" volume plugin to CSI migration. I would like to understand the concept of CSI with writing a simple driver for Kubernetes. Reference:

Simplify, modernize, and accelerate the process and tools for reviewing YES submissions from partners. Hopeful goals to accomplish:

Provisioning works with Autoyast/Cobbler for traditional clients, with profiles to enable major version upgrades. The goal is to offer that in a predictable way that can be scheduled and automated for salt minions. Salt minions pose a different challenge, and we would like to enable a reboot into the upgrade without needing PXE not traditional client to enable it.

Create a prototype of an agent on kvm hosts to control the distributen of master / worker nodes between different kvm hosts. No central control plane should be used - the main design goal should be: as simple as possible :-)

Whether it's building a newer, upstream UBoot, EDK II, or merely a SLE based rootfs, I want to make this platform a realistic possibility for desktop, digital signage, labs, etc.

Build and benchmark some smaller SES clusters (2 - 3 nodes) targetted at edge deployments. Evaluate the performance and configurations.

During the previous Hackweek [0], I have successfully implemented, tested and merged [1] an implementation of the entire C++ standard header <future>. This time, my aim is to modernize the C++14-esque standard library [2] of HelenOS [3][4] with a C++17 feature - the <filesystem> header. The <filesystem> header is much larger than the <future> header which I barely managed to implement and test in the allocated time for the previous Hackweek, but <future> was mostly OS-independent as it relied only on previously implemented features of the standard library. The <filesystem> header, however, is limited by the filesystem API of the OS and as such implementing of the entirety of it might not be possible, limiting the scope of the project (which is a good thing due to the time constraints). The primary features of the header [5] that should be implemented:

labgrid [0] is an embedded board control python library with a focus on testing, development and general automation. It includes a remote control layer to control boards connected to other hosts. My idea was to use this to be able to test my MediaTek boards remotely.

The USB controller (Via Labs 805 XHCI) on the RPi4 sits behind a PCIe bus which has no drivers at the moment in u-boot. After implementing it, we'll also have to make sure the USB HID is correctly connected with UEFI routines.

Picotm is a system-level transaction manager. It provides transactional semantics to low-level C operations, such as modifying data structures, (some) file I/O, memory access. Picotm also handles error detection and recovery. It's fully modular, so new functionality can be added. For the Hackweek, I want to dedicate some time to picotm. I want to finish some of the refactoring work that I have been working on. If there's time left, I'd like to investigate two-phase commits and how to support them in picotm.

This can be seen as a subproject of ethtool netlink interface but from the technical view it's independent. Every new piece of software is going to be buggy and with frequent changes and rewrites, new regressions are introduced. Automated selftests can help a lot but as ethtool deals with hardware devices, we do not want these tests to depend on a specific hardware. The netdevsim driver was created as a virtual device which (unlike e.g. dummy) cannot be used for actual network traffic but implements various configuration interfaces so that it can be used for their (automated) testing.

Video Recording of openSUSE Conference session which introduced the project

Core Project

The current GUI of FriCAS is ancient and difficult to use. I plan to improve that by using modern GUI frameworks, at least to make a working proof-of-concept demo to show this idea works.

We already tried to improve the Jangouts data model in the past and, although we made quite some progress, we did not finish it. I've been playing a bit with React and Redux lately, and I would like now to try a different approach replacing Angular with that combo. Using Vue.js might be another option too. Of course, we are not going to rewrite Jangouts in just one week, but let's see how far we can go. By the way, the redesign branch contains some interesting stuff from one of the GSoC that we should consider.

It ain't rocket science, it ain't thrilling, it's just useful. Quick Event is an established orienteering management software but it is still distributed in non-standard form for Linux distros. Package the software in standard packages for major distributions.

Currently, way we distribute ssh keys within QAM on our testing infrustructure is a bit cumbersome - maybe we should try to (ab)use existing salt used by our internal infra team.

We kinda need more flexible PXE in Prague office, UEFI would also not hurt - so lets check what we can do to make it better. EDIT (ggherdovich):

In the past, some customers ever complained that OCFS2 file system performance went down when listing a big directory (e.g. include 400k files). According to my preliminary investigation, this performance problem is related to file system block allocation algorithm. Then, I want to look at the current mainstream file systems (e.g. EXT4, XFS, etc) block allocation algorithms in this hack week, compare and analysis these algorithms advantages/disadvantages.

Hackweek 21?

Postmaster desperately needs a mail spool. I need to come up with a good way to store meta information about queued messages. An sqlite database seems like a natural fit because I might want to do some nontrivial queries in there to figure out which messages to deliver (and where). On the other hand, interfacing with sqlite is a bit unpleasant, so instead I might want to write one big JSON file that contains all relevant information. That would certainly suffice for the first version ...

To ease debugging cgroup relates issues this suggests to: - list cgroup hierarchy tree(s),

What is the VFX Reference Platform? https://www.vfxplatform.com/FAQ/

Join us in singing a capella — barbershop-style and others. Find us on RocketChat: #chameleon-harmonists

I have been known to talk anybody I held presentations with into using odpdown. That was always a little awkward, since it started off with pip install odpdown, rather than zypper install odpdown. I want to fix this awkwardness and package odpdown properly so it can be installed as a RPM package. I'll also include the auxiliary infrastructure I've added around it over the years (various Makefiles and scripts for generating transcripts from comments) to the package so others can benefit from that stuff, too.

Ai and Machine learning play important role in our life, I'd like to learn it. research to see is there any way of using DEEP learning on open source stuff.

I would like to learn Elixir, I plan to do some tutorial and look into books. I if I have time also start with Phoenix the framework for Elixir :smile:

RPMlint upstream milestone 2.0 is shaping up but there are still ticket that needs to be tackled to finalize the release and enjoy the freshness of awesome QA on Tumbleweed/SLE16. In this hackweek we plan to look on various problems as described at:

Idea is to have SUSE system with OpenZFS as root FS. Why ZFS

Lately the necessary patches to get rudimentary support for the Mediatek chromebook with a mainline kernel got posted. There are some hacks and I'll work on some good solution to get graphics go, at least.

Customers are using complex storage stacks such as LVM over dm-crypt over MD RAID over multipath over iSCSI and FC with LOTs of LUNs, and we're facing problems in that area which are usually very hard to reproduce. It's also hard to guard against regressions. Being able to quickly and reliably set up VMs with various types of storage / multipath is a key part of testing multipath. It's doable, but cumbersome and has a steep learning curve. I want to create easy-to-understand manual recipes plus scripts that are both easy to understand / customize and deploy.

Try to get back an automatic email notification about new or changed SAP Notes. Since SAP has closed down some of their internal servers, which hosted an unofficial database/API to the SAP Notes, the nice email notification service of the SAP LinuxLab is terminated.

There seems to be an overall consensus that the ioctl interface used by ethtool is a poor design as it's inflexible, error prone and notoriously hard to extend. It should clearly be replaced by netlink and obsoleted. Unfortunately not much actual work has been done in that direction until this project started. The project started in Hackweek 16 (fall 2017) and has been worked on since, both in Hackweek 17-19 and outside. First two parts of kernel implementation are in mainline since 5.6-rc1, first part of userspace implementation (ethtool utility) has been submitted to upstream at the end of Hackweek 19 (2020-02-16).

openSUSE Leap 42.3 goes for a rolling release model with automated openQA tests. That covers only so much though. We need manual testing too. In previous releases a google document spread sheet was used to coordinate and track the efforts.That's probably not the best method anymore. Come up with ideas and a prototype of how manual testing could be guided, tracked, visualized for a rolling development distribution with volunteers testing.

There are many fun peripherials that you can connect to a RPi but PC users are not left out either * attiny85 <a href="http://www.banggood.com/ATTINY85-Mini-Usb-MCU-Development-Board-For-Arduino-p-971122.html&quot;&gt;&lt;img height="48" src="http://img2.banggood.com/thumb/large/2014/xiemeijuan/03/SKU207366/SKU207366-3.jpg&quot;/&gt;&lt;/a> has SPI and i2c interface so could be possibly used as USB<->i2c or USB<->SPI bridge. Unfortunately, the USB support needs some non-standard timings so there is quite a bit of integration and debugging needed.

I've attempted this several times already and each attempt had different shortcomings. I'm kind of curious about how exactly will I fail this time. And it looks like I haven't failed this time.

I have several themes in progress, they all need lots of work before they could be used with openSUSE. * The gtk people keep changing things so the gtk theme I use to match my enlightenment theme also needs fixing.

The idea is about an easy way to allow users to make upgrades (e.g.: changing from one major version like 15.0 to version 15.1) using a GUI and as easy as they can in Ubuntu. Something like a notification with a button to perform the upgrade with just one-click, instead of having to deal with the terminal, that frights some new users and gives them the sensation of an outdated system.

Description

It can boot up from udisk/floppy.

The goal is to use the work from the debug-early GCC branch to generate better debug information for LTO compiled objects, especially with regarding to language specifics like classes and templates. This has now been achieved and openSUSE Factory

Make a final attempt to implement a graphical user interface for grub2 (gfxboot2).

It's quite some work, unfortunately. Here's what's done so far:

This is the tool I've been working on since HW11 and it needs more work. Actually, there's always something which could be done on it. It is basically an x86 instruction decoder with special emphasis on the kernel and decoding interesting pieces of it in order to help in the development of low-level patching techniques, among others. git repo: https://gitlab.suse.de/bp/x86d

New Development In previous hack weeks, the first few days ended up being wasted on just getting it working. I'm pleased to share that the code quality has improved dramatically since the last hack week and there are now extensive test cases for both unit testing and testing against real vmcores, and we'll use both mypy and pylint (if installed) to perform static analysis. Packages for those are available in openSUSE or as part of the crash-python OBS repo for SLE15. It has been tested with kernels from 3.0 to 5.1.