Good news! After some fiddling and understanding the repository layout I finally have working OpenTelemetry Collector packages for @opensuse!

Packages for the "core" or "classic" collector, the contrib distribution and the otlp distribution are working fine in my tests and have been submitted to the server:monitoring devel project. This includes the packages required to build them.

Here is a vagrant-libvirt setup to play around with the packages (three branches currently).

https://codeberg.org/johanneskastl/opentelemetry-collector_opensuse_vagrant_libvirt_ansible
https://github.com/johanneskastl/opentelemetry-collector_opensuse_vagrant_libvirt_ansible

Once I find some information on how to use the ebpf-profiler distribution, I will test that package and add a branch for it.

#openSUSE #Tumbleweed #Observability #OpenTelemetry #OpenTelemetryCollector #metrics #Ttracing #DevOps #PackagersLife #HellYeah

Good news, my OpenCloud server package for openSUSE was accepted into the devel project and is on its way to openSUSE Tumbleweed. Hooray!

#OpenCloud #filesharing #openSUSE #Tumbleweed #PackagersLife #HellYeah

I think I have an installable package for #RedHat's microshift for #openSUSE. First step on the way to maybe get #OKD's micro version micro-okd to build for openSUSE, as that is based on microshift. They do funny patching in between. Not sure if I can get that working in our offline build environment.

And soon I will try to properly package the opentelemetry collector! We already have alloy packaged, but I want to understand how the hell their buils logic is. Three repositories and a special build tool were identified so far...

#openSUSE #RedHat #OpenShift #OKD #PackagersLife #HellYeah

One last thing: I find it really impressive how fast and efficient the review team at @opensuse is working.

For those unaware, packagers like myself care about keeping a distribution package working and up to date. For openSUSE, once I have a new version prepared, it is being "sent to Factory" to be included in the next snapshot (after is is tested to not cause any conflicts or even tested by openQA).

Before those updates are being accepted, the review team acts as a second pair of eyes and finds all of the mistakes I may make. Forgot to add the changelog? Did not remove the old tarball? They are my safety net, so if I am having a bad day or not enough coffee, they double-check and prevent mistakes from entering #Tumbleweed.

#Havealotoffun #openSUSE #Tumbleweed #linux #distribution #packagerslife #hellyeah

It is nice that one can be notified of new releases via mail or even via RSS feed (Github, Gitlab, Forgejo).

But having things tagged as pre-releases is unfortunately not visible in the RSS feed. You only know that there is a new tag (because a tag is a release, of course, why differ?) and need to check if it is stable yet.

Some projects use rc1 suffixes and the like, which is really nice. And visible in the RSS feed...

#packagerslife

Today I was in the mood and packaged #regal and #opa for @opensuse

Packages still need more testing, but the first steps are done. Found a glitch in the OPA ldflags handling and reported it upstream.

Should arrive in #Tumbleweed soon-ish.

#packagerslife #policyascode #OpenPolicyAgent #opensuse

OK, today I took some time and finally reworked the #semaphoreui package for @opensuse. I had it on my todo list for ages and never got around to it. It was already 90% finished but lacking some fine details.

Now I have properly cleaned it up and removed the "ansible-" from the name, as it is no longer just for executing #Ansible code. Apparently Semaphore can now execute #terraform #opentofu and #pulumi code as well.

I'll do more testing before I send it to #Tumbleweed.
In other words: new vagrant-libvirt setup incoming! :-)

Stay tuned.

#devops #IaC #InfrastructureAsCode #Ansible #Terraform #Pulumi #OpenTofu #packagerslife #opensuse