PXEAT (stand for PXE Administration Tool) is a tool to easily deploy and manage PXE service. It's NOT a tool for automatic deployment. It can enable user to add their own PXE items by themselves, but of course, very limited for security reasons. The tool will be developed with the light-weight framework - flask, as well as a sqlite database.

Porting training labs to Python. This includes re-implementing the host side BASH scripts (which handle VirtualBox and KVM related tasks) to Python. For full details on this please follow training-labs project: git://git.openstack.org/openstack/training-labs.git

We want to improve translation of dependencies done by spec-cleaner (i.e. cmake(blah)) and so on - see github.

https://github.com/viccuad/gomoduino Gomoduino

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.

Why Knowledge is only useful if it is accessible.

At the suggestion of Hannes, I would like to try to make mhvtl work with tcmu-runner. Mhvtl is a tape-drive emulation package, which emulates various types of tapes drives and tape robot units (for loading drives). This package was originally based on the kernel debug SCSI driver, and still has a kernel component. This kernel component talks to user-space via a special character device. It would be nice to take away the kernel component, so that it's easier to compile and use this package, since the current mhvtl kernel driver has not been merged upstream so has to be supplied as a KMP. [And KMPs are evil.]

I'm planning to get basics of Reactive Programming and especially the documentation in ReactiveX and try some examples from RxPy Interesting links:

Following a FOSDEM presentation on Angr for binary analysis, I started packaging it in OBS. We've made progress on getting many missing Python dependencies into Tumbleweed already; remaining ones including claripy and angr itself.

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.

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.

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:

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.

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

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.

Project Description

When learning a new language, it's useful to read books in your target language. The trouble is, it's difficult and time consuming to look up the meanings of new words you encounter while trying to read. The purpose of this project is to create an ebook reader which allows you to highlight individual words and translate them quickly (similar to how duolingo stories lets you click on words to explain their meaning).

Project Description

The goal of the project is to implement a collection of top-level crash commands in drgn tool. The commands should provide a top-level overview for anybody who opens a kernel core dump. I plan to select a similar set of commands as seen in crash-python tool.