Uyuni/SUSE Manager: Windows client support
I'll continue the effort I started at last Hackweek to support Windows clients in Uyuni/SUSE Manager using Salt. When this is done, SUSE Manager would act as a WSUS server to Windows clients.
https://hackweek.suse.com/20/projects/suse-manager-windows-client-support
https://github.com/uyuni-project/uyuni/issues/1937
Status as of end of Hackweek 19
- Windows added to database, Java side, etc
- Ported Microsoft update protocol server-server and client-server reference implementations to Linux, so it's possible to download updates and CVE information from Microsoft to the Uyuni Server
- Salt packages for Windows built (locally, not in OBS)
- Bootstrapping clients from the WebUI does not fully work: client is bootstrapped, Salt key arrives to the Uyuni Server but after accepting it, system does not finish registration. Apparently, some grains are missing on the client, or enablement is missing something on the Java side. Same happens when initiating registration from the Salt minion (i. e. minion contacts the master).
Missing, maybe doable in one hackweek (depends a lot on the first item: fixing the Java enablement)
- Fix Java side so that client finishes registration to Uyuni Server
- Bootstrap repository
- Add updates and CVE information to the channels and database after synchronizing them
- Call Microsoft Update server-server from spacewalk-reposync / mgr-sync
Missing, not doable by me in one hackweek
- Virtualization. Should be easy if using KVM or Xen on Windows. Support for Hyper-V Virtualization Hosts depends on libvirt supporting Hyper-V (it does on Leap, it should on SLE starting with SLE 15 SP3)
- OpenSCAP. Should be easy, mainly providing the OpenSCAP tools and content in some channel and deploying them to the clients. Tricky part is not really OpenSCAP but how to add content from outside Microsoft Update to a Windows channel.
- Autoinstall Windows using Cobbler (http://cobbler.github.io/blog/2020/12/04/wingen.html)
- Building Salt packages for Windows in OBS. Building Windows software on OBS is cumbersome (requires using mingw), and Salt has its own building mechanism for Windows.
- Build Windows images
How to join?
I will be in the uyuni-devel Gitter channel during Hackweek, ping me there if you want to help, provide feedback, or just are curious: https://gitter.im/uyuni-project/devel
Looking for hackers with the skills:
uyuni susemanager windows systemsmanagement server linux salt microsoft wsus
This project is part of:
Hack Week 20
Activity
Comments
-
over 4 years ago by juliogonzalezgil | Reply
No promises that I will perform miracles, but as a former Windows sysadmin, maybe I can provide some help with some stuff.
-
over 4 years ago by pagarcia | Reply
Same information, in a nicer way (slide deck) https://www.slideshare.net/pgquiles/hackweek-20-open-door-support-windows-clients-in-uyunisuse-manager
-
Similar Projects
Move Uyuni Test Framework from Selenium to Playwright + AI by oscar-barrios
Description
This project aims to migrate the existing Uyuni Test Framework from Selenium to Playwright. The move will improve the stability, speed, and maintainability of our end-to-end tests by leveraging Playwright's modern features. We'll be rewriting the current Selenium code in Ruby to Playwright code in TypeScript, which includes updating the test framework runner, step definitions, and configurations. This is also necessary because we're moving from Cucumber Ruby to CucumberJS.
If you're still curious about the AI in the title, it was just a way to grab your attention. Thanks for your understanding.
Goals
- Migrate Core tests including Onboarding of clients
- Improve test reliabillity: Measure and confirm a significant reduction of flakynes.
- Implement a robust framework: Establish a well-structured and reusable Playwright test framework using the CucumberJS
Resources
- Existing Uyuni Test Framework (Cucumber Ruby + Capybara + Selenium)
- My Template for CucumberJS + Playwright in TypeScript
pudc - A PID 1 process that barks to the internet by mssola
Description
As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:
- The backend is written in a mixture of C and RISC-V assembly.
- The backend is actually PID1 (for real, not within a container).
- We poll and parse incoming HTTP requests ourselves.
- The frontend is a mere HTML page with htmx.
The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.
I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.
Goals
- Have a better understanding of different Linux features from user space down to the kernel internals.
- Most importantly: have fun.
Resources