PowerPC (ppc64le) / IBM Z (s390x) servers and CIs from Oregon State University Open Source Lab

[junaruga]

The following services are to use the PowerPC (ppc64le) and IBM Z (s390x) SSH servers and CI (in my memory it is by Jenkins).

https://osuosl.org/services/powerdev/

To request access to the POWER CI service, use our POWER CI request form.

https://osuosl.org/services/ibm-z/

To request access to the IBM Z CI service, use our IBM Z CI request form.

I may introduce you the services in the past. However, a situation around the SIMDe has been changed recently. I can see that SIMDe is recognized as more important component. Because SIMDe is used as a dependency of the WebAssembly/wabt.

https://github.com/WebAssembly/wabt/blob/e82833182a3362b26a2cbbfce15c279fbadd048c/.gitmodules#L19-L21

And I assume that that WebAssembly is one of the technologies that people want to focus on.

For example, I have seen below.

Red Hat and WebAssembly - December 13, 2022
https://www.redhat.com/en/blog/red-hat-and-webassembly

WASM (WebAssembly) SIG (Special Interest Group) was created in January 2023 in the Fedora project.
https://fedoraproject.org/wiki/SIGs/WASM

I was asked from maybe the maintainer of the WebAsembly/wabt RPM package to upgrade the simde RPM package to the newer version.
https://bugzilla.redhat.com/show_bug.cgi?id=2192076#c4

So, if you tell people at the POWER/IBM Z services that SIMDe is one of the dependencies of WebAssembly, with citing the links I introduced above, I believe that SIMDe project is sponsored for both the SSH servers and CI services.

What do you think?

[mr-c]

I submitted the form for POWER

Form submitted

Thank you for submitting your information via one of our forms. You should hear back from us within 2-3 business days. If you don't hear back from us by then, please contact us via IRC on Libera Chat in #osuosl. If you haven't heard from us within 5 business days, please email an email to [email protected] directly for more assistance.

[junaruga]

Thanks! Let's see how they response!

[mr-c]

@junaruga Our accounts are created on https://powerci.osuosl.org/; can you take over from here?

[junaruga]

Sorry, no. I don't intend to spend time to manage the servers.

[mr-c]

Sorry, no. I don't intend to spend time to manage the servers.

OSUOSL manages the servers, we just need someone to add a configuration to their Jenkins CI system. Sorry, I assumed you had volunteered to do that by opening this issue. I should have asked.

[mr-c]

@junaruga Now that we have the Fedora Packit CI running on s390x and ppc64le; do we still need this?

[junaruga]

OSUOSL manages the servers, we just need someone to add a configuration to their Jenkins CI system. Sorry, I assumed you had volunteered to do that by opening this issue. I should have asked.

Oh, sorry there was a miscommunication. First, I found a way of using the Packit CI practically with native ppc64le and s390x cases on Fedora rawhide after opening this issue ticket.

I was thinking that you submitted SSH servers for yourself. So, I said no to managing SSH servers. I am managing ppc64le and s390x SSH servers for other maintainers in the Ruby project. So I imagined the same situation for the SIMDe project too.

And I assumed you or other contributors (except me) want to use the native ppc64le SSH servers for your debugging purpose, not the Jenkins CI services. But you actually submitted for the Jenkins CI services. And as you think, I don't need Jenkins CI services for myself, because we have native s390x and ppc64le native cases with GCC (default and -O2 case) in Packit CI now.

I am sorry for wasting your time. You can cancel the Jenkins CI services from Oregon University, and close this ticket.