Git CI to automate the creation of product definition by gyribeiro

Description

Automate the creation of product definition

Goals

Create a Git CI that will:

• automatically be triggered once a change (commit) in package list is done.
• run tool responsible to update product definition based on the changes in package list
• test the updated product definition in OBS
• submit a pull request updating the product definition in the repository

NOTE: this Git CI may also be triggered manually

Resources

• https://docs.gitlab.com/ee/ci/
• https://openbuildservice.org/2021/05/31/scm-integration/
• https://github.com/openSUSE/openSUSE-release-tools

---

Learn about OSB and contribute to `kustomize` and `k9s` packages to add ARM arch by dpock

Description

There are already k9s and kustomize packages that exist for openSUSE today. These could be used as the source for these binaries in our rancher projects. By using them we would benefit from CVE fixes included in our distribution of the packages not in cluded upstream. However they are not providing arm package builds which are required.

Goals

• [ ] Update the kustomize package in OBS to use the newest version and send change request

Resources

• k9s: https://build.opensuse.org/package/show/openSUSE:Factory/k9s
• kustomize: https://build.opensuse.org/package/show/openSUSE:Factory/kustomize
• Learning Docs: https://confluence.suse.com/display/packaging/Training%2C+Talks+and+Videos

---

Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines. It also manages configuration, can run audits, build image containers, monitor and much more!

Currently there are a few distributions that are completely untested on Uyuni or SUSE Manager (AFAIK) or just not tested since a long time, and could be interesting knowing how hard would be working with them and, if possible, fix whatever is broken.

For newcomers, the easiest distributions are those based on DEB or RPM packages. Distributions with other package formats are doable, but will require adapting the Python and Java code to be able to sync and analyze such packages (and if salt does not support those packages, it will need changes as well). So if you want a distribution with other packages, make sure you are comfortable handling such changes.

No developer experience? No worries! We had non-developers contributors in the past, and we are ready to help as long as you are willing to learn. If you don't want to code at all, you can also help us preparing the documentation after someone else has the initial code ready, or you could also help with testing :-)

The idea is testing Salt and Salt-ssh clients, but NOT traditional clients, which are deprecated.

To consider that a distribution has basic support, we should cover at least (points 3-6 are to be tested for both salt minions and salt ssh minions):

1. Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
2. Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
3. Package management (install, remove, update...)
4. Patching
5. Applying any basic salt state (including a formula)
6. Salt remote commands
7. Bonus point: Java part for product identification, and monitoring enablement
8. Bonus point: sumaform enablement (https://github.com/uyuni-project/sumaform)
9. Bonus point: Documentation (https://github.com/uyuni-project/uyuni-docs)
10. Bonus point: testsuite enablement (https://github.com/uyuni-project/uyuni/tree/master/testsuite)

If something is breaking: we can try to fix it, but the main idea is research how supported it is right now. Beyond that it's up to each project member how much to hack :-)

• If you don't have knowledge about some of the steps: ask the team
• If you still don't know what to do: switch to another distribution and keep testing.

This card is for EVERYONE, not just developers. Seriously! We had people from other teams helping that were not developers, and added support for Debian and new SUSE Linux Enterprise and openSUSE Leap versions :-)

Pending

FUSS

FUSS is a complete GNU/Linux solution (server, client and desktop/standalone) based on Debian for managing an educational network.

https://fuss.bz.it/

Seems to be a Debian 12 derivative, so adding it could be quite easy.

• [x] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
• [P] Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator) --> Works from UI, need to test the rest.
• [P] Package management (install, remove, update...) --> Installing a new package works, needs to test the rest.
• [ ] Patching (if patch information is available, could require writing some code to parse it, but IIRC we have support for Ubuntu already)
• [ ] Applying any basic salt state (including a formula)
• [ ] Salt remote commands
• [ ] Bonus point: Java part for product identification, and monitoring enablement

---

Research openqa-trigger-from-obs and openqa-trigger-from-ibs-plugin by qwang

Description

openqa-trigger-from-obs project is a framework that OSD is using it to automatically sync the defined images and repositories from OBS/IBS to its assets for testing. This framework very likely will be used for the synchronize to each location's openqa include openqa.qa2.suse.asia Beijing local procy scc scc-proxy.suse.asia(although it's not a MUST to our testing) it's now rewriting requests to openqa.qa2.suse.asia instead of openqa.suse.de, the assets/repo should be consistent the format Beijing local openQA is maintaining an own script but still need many manually activities when new build comes, and not consistent to OSD, that will request many test code change due to CC network change

Goals

Research this framework in case it will be re-used for Beijing local openQA, and will need to be setup and maintained by ourselves

Resources

https://github.com/os-autoinst/openqa-trigger-from-obs/tree/master https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin

beijing :rainbow machine

---

Bootstrap openSUSE on LoongArch by glaubitz

Description

LoongArch is a new architecture from China which has its roots in the MIPS architecture. It has been created by Loongson and is already supported by Debian Ports, Gentoo and Loongnix.

Upstream support for LoongArch is already quite complete which includes LLVM, Rust, Golang, GRUB, QEMU, LibreOffice and many more. In Debian Ports, where the port is called "loong64", more than 95% of the whole Debian archive have been successfully built for LoongArch.

QEMU support is rather complete and stable such that packages can be built in emulated environments. Hardware can also be requested by Loongson on request for free. Access to real hardware is also provided through the GCC Compile Farm.

Goals

The initial goal should be to add LoongArch to OBS and build a minimal set of packages.

Resources

• Introduction to LoongArch: https://docs.kernel.org/arch/loongarch/introduction.html
• LoongArch community on Github: https://github.com/loongarchlinux
• Debian Ports repository for loong64: http://ftp.ports.debian.org/debian-ports/pool-loong64/main/
• Gentoo stage3 for loong: https://www.gentoo.org/downloads/#loong

---

Port git-fixup to POSIX shell script and submit to git/git by mcepl

Description

https://github.com/keis/git-fixup is an exceedingly useful program, which I use daily, and I would love to every git user could bask in its awesomeness. Alas, it is a bash script, so it is not appropriate for the inclusion in git proper.

Goals

Port the script to plain POSIX shell and submit for consideration to git@vger.kernel.org

Resources

---