Currently I am using astroberry server for all my astroprojects. I have a spare RPi 4, so will try to install opensuse leap on it and configure it so I could use it for my astro projects. Plan is:

terminal has it, git tool has it, so yast-devtools should also provide it for new rake tasks

The CRUSH algorithm determines how to store and retrieve data by computing data storage locations. CRUSH empowers Ceph clients to communicate with OSDs directly rather than through a centralized server or broker. With an algorithmically determined method of storing and retrieving data, Ceph avoids a single point of failure, a performance bottleneck, and a physical limit to its scalability. CRUSH requires a map of your cluster, and uses the CRUSH map to pseudo-randomly store and retrieve data in OSDs with a uniform distribution of data across the cluster. This project aims at creating graphs of the crush map, for better visualization of the Ceph cluster.

I have my favorite card game from childhood . Unfortunately description is available only in Russian https://uk.wikipedia.org/wiki/%D0%94%D0%B5%D0%B1%D0%B5%D1%80%D1%86%D1%8C . Currently my friends spreed across the globe and here in Germany no one except my wife knows the rules . I would like to to have ability to play this game with my friends like I did in school/univercity.

Project Description

If you are now thinking of Salt-SSH, this is not completely wrong, but also not right. What we are talking about here, is an other Transport for Salt, a replacement for ZeroMQ.

Why?

Project Description

Valgrind currently lacks support for 80-bit extended precision floating point arithmetic on x86_64 (long double). The current implementation uses 64-bit arithmetic instead, which means that programs running on x86_64 with "long double" give different results when running under Valgrind and natively. People were asking for support for this since like forever, but to date nobody went on implementing it. It's a project for a year, unless somebody has time to work on it full time, but one has to start somewhere. :-)

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.

Project Description

In January, we announced the D-Installer project, an attempt to build a web-based installer on top of YaST and Cockpit. Since then, the codebase has grown significantly, especially the JavaScript part.

<p>Rescue system has a lot of options , but most of them can only be set at boot time, first idea is too provide a way to configure them while the system is running.<p>

some ideas

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.

Cover more cornercases for spec-cleaner to allow the swap of formatspecfile due to its bugginess in comparsion.

This is about porting the old KDE 3 based KDirstat to the latest Qt 5. KDirStat didn't use that much KDE infrastructure to begin with, and KDE seems to be more and more a moving target. Project repo and web site with more details:

newburn is a system press testing tool. But it is out of maintained. And it is heavily integrated in ctcs2. So replace it with a new one.

Get openSUSE running in parallel to Android on a regular and rooted Android Smartphone. On top of this try to get a graphical desktop running using Xvnc available for Android.

While programming is occasionally a very rewarding activity, it's mostly a chore and the rest is filled with frustration. Let's teach an unsuspecting youngster program! To fulfill this nefarious goal I've set out to help my colleague without prior programming experience get hooked on programming, starting with python. The student finished an online tutorial and we pair programmed a tiny-fix-turned-massive-change in a tool used by our team.

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.

Project Description

The purpose of this question is first to research, if we already have a python API available to be used in scripts to query status and details in the running cluster. If not already available the first purpose is to get a draft version of such an API. If it is already available the second purpose is to implement some useful examples for SAP workloads.

Setup a patchew instance

patchew allows you to easily track patch series sent to a mailinglist and see the diff between the different series.

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.

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.

Project Description

Inspired by one of the proposals for GSoC and given that I'm usually working on maintenance updates for SUSE Manager - Uyuni I decided to translate it to Italian. :)

Apple has published the source code for their language swift. They also made the swift compiler available for Ubuntu users. Now it's time to port it to openSUSE! swift GitHub project: https://github.com/apple/swift

"salt-toaster" allows you to test multiple Salt package flavors across different operating systems via Docker containers. This project is heavily used on the SUSE Manager team to hardening the Salt package that is shipped on the openSUSE/SLE distributions. Link to GitHub repository The "salt-toaster" execution is divided on different steps (image building, container spinning, salt key acceptance, tests execution, etc) but currently we only get the global results for the entire testsuite execution.

Project Description

Update the physical KubeVirt+Kubernetes test cluster in Provo from SLES15 SP2 and CaaSP to SLES15 SP3 and Rancher's k3s. This will allow us to easily experiment and test Harvester.

Problem

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

Project Description

This first part of this project will build a moisture sensor using an ESP32 board and circuit python. I am hoping to implement a notification method using SMS or Email. Additionally, future plans include adding a Web based interface to view historical data as well as optionally adding some mini pumps that will water the plants once a specified moisture level (very little detected) has been reached.

Project Description

Now, when mikrotik supports WireGuard there is no need to stay with OpenVPN. Let's try to setup WireGuard and investigate it's options, test performance etc.

Project Description

The goal is to build a custom PCB and firmware for a smart meteostation with ESP32 at it's core. The board should have PoE available. Sparkfun Weather Meter Kit is used for the anemometer, wind vane and rain gauge.

It would be nice to have trendy and hip editor [0] in openSUSE. Currently however some nodejs dependencies are missing.

What needs to be done:

zypp-closure is a small helper tool making use of libzypp and the metadata of product repositories. The idea is to generate a dependency closure for a package or list of packages based on repositories metadata.

The SMBus standard specifies an address resolution protocol (SMBus ARP.) It has two key features : * Handle I2C slave address collisions. If two SMBus slaves would use the same I2C address, ARP lets one of them pick a different address to avoid the address collision.

Each of the core dump upload servers in Europe and USA could be improved if the shell scripts were combined so that the same tasks can be performed on each site, e.g. downloading of all packages needed for crash usage with a specified core dump by allowing for configurable (or even automated) selection of locations to obtain data packages from.

Sonnenhut is a simple Pythong web app that provides basic info useful for planning photographic activities. The current iteration does the job, but it can be improved and extended in a number of ways. If you are interested in photography and familiar with Python, you are welcome to join and contribute to the project.

Compared with traditional file systems (e.g. EXT4, XFS), log-structured file systems treat its storage as a circular log and write sequentially to the head of the log. I want to learn about this kind of file system via this hack week, to understand how it manages its data and metadata, to understand how it recover back from crash, to understand its advantages and disadvantages.

<https://showmethekey.alynx.one/> <https://github.com/AlynxZhou/showmethekey/>

There are several popular ways of controlling home automation with voice today. Amazon Echo and Google Home both allow users to control lights, speakers, etc. with a simple voice command. For this project, I want to replicate some of the simple voice commands supported by projects like those, but in a way that does all processing from within the local network, and doesn't upload any voice clips to a server outside the home. There's something that feels a little uncomfortable about Amazon or Google having the ability to listen in on all conversations, so I'm trying to eliminate that while still being able to turn my lights on or off by voice.

Read in a crash or oops-style backtrace and access DWARF information to output the current content of the stack and registers in term of symbols, and the the crash commands to dump/pretty print them. In other words, when looking at a crash dump, answer the questions "Which variable is currently stored in $rax? What is the structure of the stack? Which variable is stored at $rsp+16?"

Status at the end of hackweek 10

Using dynaname it is already possible to securely auto-update DNS records in a bind9, but this still needs a linux machine. This project is about building a CGI frontend for it that makes it a replacement for the discontinued dyndns.org service.

To say it's a review, it's better to say it's a good way to learn from others. I'll review test scripts in openQA project as much as I can, digest them and learn how to write Perl script more pretty. I'll make some notes for sharing.

Distributed teams, cultural differences, expectations and habits are a natural enemy of vibrant, productive meetings (yes, meetings can be productive!). In this project I'd like to work on a different format and targeted exercises to provide ideas and a resource library to anyone interested in spicing up stale meetings. I am looking for your ideas, problems and examples - Feel free to join!

The libvirt TCK provides a framework for performing testing of the integration between libvirt drivers, the underlying virt hypervisor technology, related operating system services and system configuration. The idea (and name) is motivated by the Java TCK. Currently the libvirt TCK is not fully packaged for SUSE and the test suite itself contains a lot of Redhat-isms. Mike Latimer and Jim Fehlig will work on properly packaging libvirt TCK (it has a LOT of perl dependencies) and patching it to work better with SUSE virtualization hosts and SUSE guest operating systems. It has traditionally focused on the KVM hypervisor, so there might be some progress made to make it work better with Xen too.

Air Pollution Forecast

Summary

After joined Gary's BCC workshop a few days ago. The BCC is interesting to me, so I'd like to look into it. - Go through the tutorial. https://github.com/iovisor/bcc/blob/master/docs/tutorial_bcc_python_developer.md

My previous knowledge about Python is small. I need learn more about python. Using a script write in shell script, andt this script already ported to python by a collegue team. I'm going to use a port of this script to understand and maybe collaborate with this code.

Project Description

Most of us remember a period of our lives when we had time to stay somewhat uptodate on the research and developments in our area of expertise. However, this often falls short during our day-to-day work, as we get bogged down in the engineering problems of the real world, and the struggle of explaining even basic concepts to laypeople :-)

Project Description

When zypper downloads many RPMs as part of an update, the download phase can be greatly sped up.

Since eBPF was introduced into linux kernel, the eBPF verifier keeps the eBPF programs from any wrong-doing. I would like to look into the verifier and see if it's possible to extend the check to avoid reading any sensitive data in the memory.

Project Description

We are currently at GHC-9.4.x, which a bit old. So I'd like to take a shot at the latest version of the compiler, GHC-9.6.x. This is gonna be interesting because the new version requires major updates to all kinds of libraries and base packages, which typically means patching lots of packages to make them build again. A significant part of the development effort will be live-streamed on Twitch so that others can collaborate easily.

goals

• learn general information about them

The idea is to create a fantastic robotic SUSE pet using cheap materials. It will be moved with you remote control of your TV. After building the prototype the schemes and Arduino code will be delivered for everyone to try building it at home.

Project Description

Crev [1] is a collaborative code audit idea. Since it's common that more security engineers can work on the same projects, or there can be a different person auditing a piece of code after some time, there is the need to keep track of the code audit notes in a non-repudiable way.

Last time I checked QEMU lacked support for >= z10 processors. Thus one cannot run SLE12 and newer in a virtual machine on non-s390x host. I'd like to improve the situation during Hackweeks.

The SLE15 development model follows the Factory First policy, where all submissions need to go first to openSUSE:Factory and then to SLE15 repos. This way more bugs are fixed, less patches get lost, less backporting is happening etc. Our openSUSE infrastructure is using salt for configuration management. This was working fine, but suddenly we had to split the openSUSE from the SUSE-DMZ services into separate VLANs, thus the salt codebase had to be split as well. The code itself is mostly formulas and quite similar states between the two set of services though. The only real difference was in the pillars, and even there there was a lot of duplication.

To make OpenQA work with real ARM devices, we need to control * Reset

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:

Use python "textgrocery" class to classify the webpage informaton . It's very interest to analyze the "focus" of a webpage .

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.

Learn about ALP

https://documentation.suse.com/alp/all/html/alp/index.html

Release v2.0 of the gem and dashboards TODO: https://github.com/influxdata/influxdb-rails/issues?q=is%3Aopen%20is%3Aissue%20project%3Ainfluxdata%2F118

VOVO is a server-client architecture to determine current abuild load on devel-network machines. The goal is to trigger machines on and off depending on build power. It is an attempt to reduce power consumption. Current status:

Learn the grub2 network stack and have fun with ipv6 network booting. :D

Smalltalk is an object-oriented, dynamically typed, reflective programming language and Pharo is a modern, open-source,

When we started brain storming a project for hack week, one of the floated ideas was to remake the 1983 film WarGames, and for lack of available space, a local lot with storage units was proposed. Over the course of the following years, while we planned, we realized that this whole idea would not be the most feasible, but it still felt like we were onto something. Eventually, we settled with keeping the name and changing the scope.

Spacewalk is the upstream project of SUSE Manager. Currently Spacewalk runs on RHEL, CentOS and Fedora, while SUSE Manager runs on SLES.

Currently there is support for TAP being added to OpenQA::Parser::Format However it has basic support, therefore the following is needed:

Logos Competition: openSUSE, Tumbleweed, Leap, Slowroll and Kalpa

The openSUSE Community is considering a new, distinct openSUSE logo to represent the project as well as four new logos for the following openSUSE distributions; Tumbleweed, Leap, Slowroll and Kalpa. There have been discussions of a new openSUSE logo over the years, but the timing to transition to a new logo wasn’t ideal, until now.

Feeling very comfortable with your (open)SUSE desktop? Don't get too comfortable; there's a lot of innovation out there. Try living in a different system for a few days, and see if you can find some innovative paradigms to bring back 'home' with you. Here's a few suggestions: * Feeling really crazy? Try Windows 8

Fresh air and motion helps your brain to come up with new and creative ideas. This hackweek project offers exactly this*. You can expect running exercises along the Nuremberg city wall. Running 25 to 50 meters sidewards, jumping, running stairs, etc. will give your brain new energy.

Project Description

Overall: Existing NFS-HA Consulting solution exists (for SLES15 SP1 and SP2+) and is in production at customers. Goal is to improve this solution, enhance the documentation and make it more robust.

Overview: We're building a mobile to-do list app using React Native and connecting it to a self-hosted Elixir backend. This project aims to create a user-friendly, cross-platform app for task management, with data syncing across devices.

The evfilter project (https://github.com/lhc4/libevfilter/) isn't able to substitute multiple events to one event or vice versa. I want to improve that and repair some other bugs.

YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table Many YaST developers will be at openSUSE Conference, that overlaps with Hackweek. The plan is to lock them all in a room with a blackboard and reach agreements on how the code should be organized in the future. Then use Hackweek to iron the details, document everything in some kind of style guide and, if time permits, even do some experiments about how to adapt the existing code to the new conventions.

For testing Hawk, we're currently using a Vagrant configuration, and for testing HA releases we've been using a set of scripts originally authored by Antoine Ginies as a Hackweek project. My vague idea is to combine Terraform, Salt and a custom web frontend to make a tool that can be used by us as developers but also for others that want to try Hawk or play around with a cluster, for example for the UX team when testing modifications to the Hawk UI. I would base this on the work done by the SUSE Manager team:

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.

Sometimes you search for a package, and you don't find it because you're not typing it right. Of course there's regex support behind the scenes but it requires conscious effort to make use of.

Motivation

Right now, every time a new team wants a new room in our Jangouts instance, they have to ping me and I have to manually create the room. That means: * Adding some lines to the corresponding config file

Now we are lack of using internal wiki page to solve problem. One of the reason is that we don't know if it contain the solution we need, and it's not convenient to search it manually in wiki page. It's much more slower than using google. In one group, we are most likely facing the same problem during work. So keeping the best solution, which we got from searching engine, in internal wiki is an efficiency way to collect standard workflow.

The current Jangouts UI is limiting us when thinking about adding new features. Some examples: * This (using the whole thumbnail to pin a participant) was implemented, but the result is far from optimal (I have not even deployed it in production).