This project is about advancing the tool you're currently browsing.
It got started back in Hack Week 9 to retire all the weird tools we've used in the past to track ideas. As you can see it has gone far but is still far from done. There are lots of features missing and bugs to be fixed on github. Get going!
It's 1.5yrs since we've launched the last Studio version. Customers are asking about a roadmap, a new version...
After discussions with AJ, Adrian, Alex, I want to create a draft plan/concept how such a Studio successor could look like.
Gems-status (http://github.com/jordimassaguerpla/gems-status) is a command line tool that creates a report about the gems used in an appliacation. The most import result is the security alerts.
However, this tool is being configured using a yaml file, which has to be updated with new information every time there is a security alert.
Learn more about network performance testing tools. I would like to get more fimilar with netperf and iperf. Try to find out what's different between netperf and iperf. And have a look at what's new in iperf3.
kGraft is SUSE Labs answer to the rising need for being able to patch the running kernel without rebooting the system. I think this kind of tool is very cool, so by this hackweek chance, I want to investigate it how it works and how it was implemented. And also by this chance, I hope I can improve my ability of kernel hacking. If you are also interested in kernel live patching, please join this project together.
There are more and more devices with no Adobe Flash plugin support in web browser (new Android and Apple phones and tables, etc.). The aim of this project is to replace Flash testdrive in SUSE Studio with HTML5 client.
So our current implementation bases on our project from a previous Cloud workshop which uses noVNC.
Gathering detailed information about hardware in an automated way with chef using an ohai plugin enhances transparency about the hardware being used in a datacenter.
The idea is to write a plugin for ohai that gatheres information from hard drives used in a node that runs chef-client.
SUSE currently consumes a lot of electricity for keeping servers up an running as well as workstations at the office rooms, air-conditions and so on.
The project is about to collect information where all the power is going to and to find sweet spots for saving power (and money).
This project is based on some hack of a mind flex toy containing a so called "neurosky eeg" chip. Having a sensor connected to your skull this system can meassure several waves emitting from the brain, also called brainwaves. The Idea is to combine this system with some camera based monitoring system that will watch a test subject while sleeping and recording the corresponding brainwaves for later analysis of brainactivity and body movement.
Other use cases do exist, this was the only one i could come up with that involves sleeping in the office ;)
over 4 years
9 hacker ♥️.
Has no hacker:
Current kGraft implementation allows to apply new patch only when the previous one is applied to the whole system. Every task is handled separately and it needs to wait for a safe place to switch. It might take a while, especially when the task is sleeping.
Therefore it would be great to allow to apply more patches in parallel. It is not trivial because different tasks might be in different world, so the slow stub has to be clever and choose the right one without taking any lock...
The idea is simple. Dice is a light weight build service for KIWI images with full control over the build power by the user.
At SUSE we have the buildservice which is the full professional version of a build service for packages, images and also products. As a normal user I can provide input and I get some output but I have no control what happens with my data, when it's being processed and where it's being processed. That's by design and works great, thus not meant negatively. I'm a 100% fan of the buildservice
One of the winning factors of Docker is the Docker Hub. This the a place where the Docker community shares their images.
Thanks to Docker's integrated build system it is possible to create new Docker images by just extending an existing one. That's why the Docker Hub is so useful.
Working remotely has many advantages, but you sometimes lack some infrastructure. Specially if you use several computers or you share space with other SUSE co-workers. We are 3 Susers in Gran Canaria and we plan to share an office. So we have bought a Cubietruck, a tiny device with minimum power consumption, an ARM processor, a SATA interface and a Gigabit ethernet.
The plan is to come-up with a set of recipes to configure such device to:
Currently the Open Container Initiative doesn't specify a distribution protocol or system, and the current "standard" format is the Docker registry protocol. Aside from technical reservations with Docker registry, it is also not an OCI-compliant system and will require a lot of work to integrate it into all of the openSUSE/SUSE tooling.
So, a very insane idea I came up with is to convert OCI images to RPMs and then distribute them as simple RPMs. The idea would be to use capabilities (Provides: oci(...)) to implement the different names of images and then also the dependency graph of blobs (which would naturally be de-duplicated).
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.
almost 2 years
7 hacker ♥️.
Has no hacker:
This is my attempt to catch up on the field of machine learning. In order to not "waste" time of exercising with dummy data the Security team came up with a couple of interesting questions:
1. Is a software mentioned in a bug or security issue relevant in incident management (Tagging as Not for us)?
There are many performance test historical data stored in QADB, we may process them to find some probably regular patterns, then utilize existing python data analysis library like pynum, pandas and scikit-learn to improve data analysis.
Goal of this project in hackweek18:
Bpfilter is meant to be a replacement for the current in-kernel firewall/packet-filtering code. Bpfilter is short for BPF based packet filtering framework. In this hackweek, I'd like to have a look at bpfilter since I am curious about why bpfilter, how does it work and its current status.