Every time we went to UEFI Plugfest, one of the frequently asked questions is how to setup a PXE/HTTPBoot server. Besides, we also have to setup and test the server before the event. Although we already have the document(*), it may be easier to deploy with a container image.
My goal is to learn how to package a container image in SLE/openSUSE and create a flexible image for the fast deployment of PXE/HTTPBoot server.
The current geekos install at http://geekos.prv.suse.net/search is not reachable for employees outside of engineering.
We want to move it to the SUSE IT maintained EKS cluster to make it available for all.
SUSE dissolved an old warehouse, containing lots and lots of boxes with old SUSE / SuSE / S.u.S.E software. All of those boxes were originally going to be dumped in March 2021, which could be prevented. They are now stored in the SUSE Event Area in Nuremberg.
A few months ago, the YaST team released cockpit-wicked. Compared to YaST, this module contains a pretty simple data model, but there is still some duplication with YaST logic.
The idea for project starts on LEO workshop. The main goal is to provide UI for local configuration that allows easy transition to 1:N management. So here is vision:
I run openSUSE TW and FF with i7-5600U Intel CPU. Calls with ~4 (video) participants work but my CPU load is approaching number of cores. In slightly bigger calls (>=6 participants) the CPU load was insufficient and audio packets were being dropped. I'd like learn more about webrtc video streams in order to reduce the client's CPU work or make it more adaptive when running with limited resources.
The aim of the project is to run a sample microservice app in Kubernetes. A simple app will be written in Python and work as an online store comprising of frontend, orders, and products services. (could be more!!)