Build multi-arch images about piraeus HOT 19 CLOSED

I meant the architecture(s). I'd say we open them up gradually, starting with arm64, as I'd assume this is the one most people are interested in. If we have that one, adding new ones is trivial.

After we put the packages in the repos I'd assume the PR is small and easy enough to review, so perfectly fine it is then just one PR. Speaking of the packages we need to put in place: For $reasons this has to wait till Monday. I will ping you as soon as they are there. The only challenging container will be drbd-driver-loader, as we need one container per supported distribution and I'm not sure if all the base images exist for all architectures. But that is fine as well, the drbd-driver-loader is not strictly necessary and having only a subset of distributions it can be used with on non-amd64 is fine as well.

from piraeus.

@jukie We now have the packages in place. I did successful arm64 test builds for piraeus-{server,client} on one of my arm64 boxes. Guess you can now start adding this architecture.

from piraeus.

I am currently looking at piraeus-operator -- that's the next image that fails on my cluster. Is that a reasonable next step?

A local build is now running and creating a number of further pods that fail; I will debug that in the next hours.

from piraeus.

I found it under workflows, can use c694efc as a guide and submit a PR later.

from piraeus.

Hi!

Thanks for taking the initiative. Don't hesitate to ask here if you have any questions.

One problem you'll likely encounter is that we currently use the Linstor and DRBD packages distributed by LINBIT, which are only free to download on x86_64

from piraeus.

also see #71

from piraeus.

Ah damn, so I guess this isn't even possible then right?

from piraeus.

Unless you mean only the pre-built packages are an issue. Is the source code still available somewhere? I could alternatively use multi-stage builds.
Looks like it is - https://github.com/LINBIT/linstor-client
This has turned into more of an endeavor than expected but I'll still work on it haha

from piraeus.

after some internal discussion we decided that we want to open up Piraeus for multiple architectures. Which one would be the one you would want to work on? Then we can add the packages for that to the public repos and then you/we can work on the rest

from piraeus.

Do you mean the architecture or docker image?
If the former it'd be nice to add support for all the "typical" architectures used in other public repos.
K8s dashboard for example supports amd64, arm, arm64, ppc64le, and s390x. I personally would only have a use for the first three but could validate all. I imagine the majority of users were already covered by amd64, and the next biggest subset would be covered with arm/arm64 support so that'd be a good starting point.
If the latter, I can start with the piraeus-client but initially planned on adding a PR for all anyways.

from piraeus.

Sounds reasonable, thanks for the update!

from piraeus.

Awesome, thanks for the update!

from piraeus.

@rck please take a look at #76

from piraeus.

I added #84 to keep this going forward.

from piraeus.

Currently we have:

• piraeus-client #84
• piraeus-operator piraeusdatastore/piraeus-operator#207
• piraeus-csi/linstor-csi piraeusdatastore/linstor-csi#130
• piraeus-server (copy&paste from piraeus-client) #85
• drbd9-* loader (copy&paste from piraeus-client)
• drbd-reactor (copy&paste from piraeus-client)
• piraeus-ha-controller piraeusdatastore/piraeus-ha-controller#9
• piraeus-init (does anybody use that anymore? I don't think so @alexzhc?)

from piraeus.

See above: I think that are all the core images required for piraeus.

from piraeus.

@toelke I think that's it 🥳

Thank you so much for your efforts!

from piraeus.

Sure thing.
My cluster (hybrid amd64+arm64) is running.

from piraeus.

I think we forgot to close this issue. piraeus-init isn't used anymore. So all done.

from piraeus.