Hi Ard, On 6/18/20 1:28 PM, Ard van Breemen wrote: >> The biggest issue in maintaining ceph is to make it build on 32 bit >> architectures. This seems not to be supported at all by upstream anymore. > > First of all, I don't know what your goal is to support 32 bit.
Debian supports it, so it should be supported if possible. > I do have a goal: I have loads of armhf machines and only so many amd64 > machines that do not even have enough memory to properly support ceph > and being able to do something (as the MON uses 1GB of memory alone). > I have multiple sites with this situation, and for the foreseeable > future, we will still be building infrastructure on armhf. Getting a > decent AMD64 setup in any location is additional and probably > unnecessary costs. You'll either need to migrate to amd64 (or arm/whatever64) or pay somebody to fix ceph at upstream. > I think the stance of the ceph community in this is: as long as nobody > sends in patches they are not going to care. And they can't support it > themselves because they have a totally different target (clouds). Its the same: they support what they get paid for or what is needed. People rarely use 32bit these days. Even on cheap arm devices 64bit is the way to go. > I am willing to host the armhf releases and maybe the i386 releases on > my server, that way there will be 32 bit releases but not official ones. Doesn't matter, hosting is not the issue here. > But I do want your involvement. You can want that, but you won't get it. Send patches or people who will do the work. I'll happily accept patches, or even better, but reports with links to patches at upstream. > I've been trying to compile it for a time, using sources from ceph and > from proxmox, until I realised ceph nautilus is in backports. And it > worked. > So at least I want your guidance on how you build these... For now I've > used an armhf machine, and I needed to limit the number of threads to 1 > due to c++ compiler needing more than 1GB of RAM to compile a single > source. Upstream has a detailed readme, or you can use the basic way to build a debian package using dpkg-buildpackage, or similar tools. > Not only do I want to make support complete so I can use hardware, I > also think it's just bad programming not to use explicit sizes. And I am > also on the verge of investing in amd64 clusters, I don't want it to > depend on code that's depending on a lot of features. > Anyway: I don't know how you build and test on non amd64 systems, do you > also use armhf, or do you use a cross compile environment? You can just build it, if you are using the Debian source. Otherwise you'll need a lot of patches to make it build, and even more to fix those various 32bit related bugs. Bernd -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
