Learn about OSB and contribute to `kustomize` and `k9s` packages to add ARM arch
a project by dpock
Updated 5 days ago. 1 hackers ♥️. 1 follower.

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

Join this project

Looking for hackers with the skills:

obs

This project is part of:

Hack Week 24

Activity

  • 5 days ago: dpock started this project.
  • 11 days ago: hennevogel added keyword "obs" to this project.
  • 27 days ago: hennevogel liked this project.
  • 29 days ago: dpock originated this project.


    • Comments

    • dpock
      5 days ago by dpock | Reply

      The first thing I've learned about OBS revolves around the way packages are maintained and delivered. And unfortunately, that lesson largely causes the rest of the "exciting" parts of this hack week project to fizzle away.

      I assumed that because I couldn't do: zypper in k9s On the BCI images that this would work for all architectures after adding the right repo. This may still be partially possible, however the architecture for packages may cause the source to vary.

      For instance the k9s package for ARM on factor can be found here: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/k9s

    • dpock
      5 days ago by dpock | Reply

      In my testing to learn OBS, I enabled my project to have ARM published on 15.6 and 15.7. Then enabled the repo to build for those and it gave me the desired results: https://build.opensuse.org/package/show/home:dpock:branches:devel:kubic/k9s

      However, even this isn't strictly necessary as I once suspected. Since ARM builds/packages exist in a dedicated repo. So for the intent of my downstream project, we just add both repos into the image. The ARM ones will be used on arm and ignored on non-arm.

    • dpock
      5 days ago by dpock | Reply

      Ultimately it seems like the k9s package -which was the biggest concern- is ready to use. No notes needed to shift over to use that in our image. However, kustomize binary is very old so needs to be updated.

    • dpock
      5 days ago by dpock | Reply

      I've created an initial PR to switch k9s to this source for shell: https://github.com/rancher/shell/pull/294

    • dpock
      3 days ago by dpock | Reply

      I must admit - this project is a bit of a bust at this point.

      In hindsight, it was created with a clear assumption that "SLES is missing these packages due to missing repo sources". From my previous comments it should be fairly clear that this assumption was incorrect. There are multiple community-maintained packages that can be sourced for the development package, which in turn can feed into the repo which could be used in SLES (and there by BCI images).

      That said, the difficulties I found accessing these binaries via BCL images are more reflective of openSUSE/SLES packaging practices. To solve for that may still be possible, however it's not going to be a technical focused solution as I assumed I could attempt here.

    Similar Projects

    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.

    • [ ] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    • [ ] 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)
    • [ ] Package management (install, remove, update...)
    • [ ] 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

    Switch software-o-o to parse repomd data by hennevogel

    Currently software.opensuse.org search is using the OBS binary search for everything, even for packages inside the openSUSE distributions. Let's switch this to use repomd data from download.opensuse.org

    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

    Automation of ABI compatibility checks by ateixeira

    Description

    ABI compatibility checks could be further automated by using the OBS API to download built RPMs and using existing tools to analyze ABI compatibility between the libraries contained in those packages. This project aims to explore these possibilities and figure out a way to make ABI checks as painless and fast as possible for package maintainers.

    Resources

    https://github.com/openSUSE/abi-compliance-checker

    https://github.com/lvc/abi-compliance-checker

    https://sourceware.org/libabigail/

    obs-service-vendor_node_modules by cdimonaco

    Description

    When building a javascript package for obs, one option is to use https://github.com/openSUSE/obs-service-node_modules as source service to get the project npm dependencies available for package bulding.

    obs-service-vendornodemodules aims to be a source service that vendors npm dependencies, installing them with npm install (optionally only production ones) and then creating a tar package of the installed dependencies.

    The tar will be used as source in the package building definitions.

    Goals

    • Create an obs service package that vendors the npm dependencies as tar archive.
    • Maybe add some macros to unpack the vendor package in the specfiles

    Resources