There is a ramdisk block device (brd), and there is a null multiqueue device (nullblk). The one can do I/O, but doesn't use multiqueue, and the other does multiqueue but cannot do I/O. So the idea is to have a new multiqueue ramdisk block device (ramblk?), which can do both. Would be most useful for testing multiqueue.

During the last CSM workshop I started to refactor zypper-docker in a way that: - The CLI code and the "library" part got split.

Alexa understands you. Jessy is the same, but you also understand her! :-)

Everyone loves to talk to the computer. Especially if it understands you. :-) So the Amazon Alexa is a hype right now. However, it requires your marriage to Amazon and signing contract to sell your soul in the afterlife: Alexa is nothing but a fancy microphone that sends everything you speak to ̶F̶B̶I̶ ̶a̶n̶d̶ ̶C̶I̶A̶ Amazon cloud so it will access your public API. Yes, and give them your access rights, of course...

Description

Play with raspberry pi to get high availability through load balancing and containers.

Oficina, a mechanical workshop application developed in Qt/C++ Hackweek 17: Work on TODO - Test. Make it very stable, after that, insert it in openQA.

Sometimes - I just miss an important IRC message or a beginning meeting, which is not good :smile: So I decided to play around with the following stuff:

I want to get an openSUSE based image working on Samsung DEX: https://www.linuxondex.com/

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.

Project Description

We know that Kubernetes clusters need control planes but running them in dedicated VMs might not be always efficient, instead, we can run them as pods within the management cluster.

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.

Project Description

The openSUSE Project has a problem, not enough people are engaged in the development. In order to fix this, we need a less obscure way to learn about contributing. One of the ways to do that is enabling people to discover various open meetings that happen for planning of various areas of project progress.

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.

Project Description

Improve the gnome-shell extension Screen word translate and Switch Workspace

/media was a very comfortable thing standardized by FHS. After introduction of desktop based udisks mounts, the directory became empty. Paths like /run/media/me/directory or /run/user/1000/gvfs are used nowadays. When used from a terminal, it is very uncomfortable. As mounts are private to users, the old style of /media use cannot be returned back. But with a kernel namespaces feature, it is possible to make private mounts, and each user can see a different contents of /media.

Learn about ALP

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

Hikey is a development board with HiSilicon Kirin 620 eight-core ARM Cortex-A53 64-bit SoC. The original firmware is based on Tianocore EDK II, and I'd like to port coreboot to this board. Challenges:

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.

Project Description

Not a Hack Week project per se, but I am trying to connect with a few like minded people - I like playing Texas Holdem poker and am tired of playing bots/strangers online. I am hoping to gather a few fellow players for a game.

Intel Chen Yu developed a user land utility: Introduce the in-kernel hibernation encryption

Linux From Scratch (LFS) is a project that provides you with step-by-step instructions for building your own customized Linux system entirely from source. Build the customized linux step-by-step is good way to understand linux system deeply. (Include cross compile TEC which I have interest )

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.

Build an open-source appliance editor for SUSE Studio that interacts only with the API, using modern JS web frameworks. For users, this provides an opportunity to influence, or create unique tailored editing experiences for Studio appliances. For Studio maintainers, this provides a road towards a modern appliance editor, and a chance to remove tens of thousands of lines of brittle legacy code. For hackers, this provides a chance to get your feet wet with modern client-side web technologies, like

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.

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.

Project Description

Sometimes open source products lack of a good and inspiring documentation. So my idea is to brush up my Blender skills to a level that I'm able to do some tiny 3D animations to explain workflows and procedures better.

In case any of the source files changed, openSUSE Build Service rebuilds the dependent packages regardless of whether that particular modification affects the dependency. This makes our resources footprint bigger (and the electrical power bills higher). It also affects users, because every new package build causes the package manager to include that package in the next update thus consuming network bandwidth and resources of users' computers.

Current OBS controls for package rebuild triggers

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.

Using docker as a development platform for nontrivial development environments sounds interesting. This project is about learning basic docker handling, about exploring how to use it for simplifying development, and maybe (but just maybe) about providing ready-made docker containers for new team members.

While normally data is passed to linuxrc (including an AutoYaST profile), modern auto-install tools like Ignition from CoreOS support a very interesting method: the QEMU Firmware Config device. This allows to read from inside the VM a blob by reading /sys/firmware/qemu_fw_cfg/by_name/opt/keyname. The driver is included in recent Linux kernels.

See Jonathan Dieter's chunk project. https://github.com/zchunk/zchunk