Support #23822
open
Added by Nayana Thorat about 6 years ago.
Updated almost 6 years ago.
Description
I could see s390x support is available in ceph source code ( v12.2.4).
https://github.com/ceph/ceph/blob/v12.2.4/ceph.spec.in
I could build ceph v12.2.4 on Ubuntu 16.04 on s390x using steps provided in README.
However on test execution and function test cluster I observed below issues:
1. Observed 16 test failures due to segfault/memory corruption or expected/actual value mismatch
2. On executing function test cluster observed auth failure
3. On RHEL platform, build itself failed due to few dependencies mentioned in ceph.spec.in are not available.
I am analyzing code to find the failure causes. Is s390x support not fully added to ceph?
Is s390x support not fully added to ceph?
Not fully, no. Ceph is known to builds on s390x for openSUSE and SLES build targets, but is not tested for actual functionality.
Regarding functionality, there are two primary usage modes: client and server.
Regarding server, so far we have not heard of anyone who seriously wants to run Ceph as a server on s390x.
The goal of the current s390x support is to enable (user-space) client functionality on s390x only. But this has not been seriously tested, either.
So, can you be more specific about what your end goal is? I.e. ceph as server, or ceph as client? If the latter, what type(s) of client functionality do you intend to use?
The goal of the current s390x support is to enable (user-space) client functionality on s390x only. But this has not been seriously tested, either.
So, can you be more specific about what your end goal is? I.e. ceph as server, or ceph as client? If the latter, what type(s) of client functionality do you intend to use?
We are currently building whole ceph code (https://github.com/ceph/ceph/tree/v12.2.4) on s390x platform. This will include all functionality.
We could build ceph source on Ubuntu 16.04 however while setting up functional test cluster, command
"../src/vstart.sh -d -n -x -l_" fails with an error:
/ceph/build/bin/ceph -c /ceph/build/ceph.conf -k /ceph/build/keyring -i /ceph/build/dev/mgr.x/keyring auth add mgr.x mon allow profile mgr mds allow * osd allow *
0 monclient(hunting): authenticate timed out after 300
Also, test failures are seen with make check or ctest -j$(nproc) command.
We are referring to guide: https://github.com/ceph/ceph/tree/v12.2.4
Nayana Thorat wrote:
The goal of the current s390x support is to enable (user-space) client functionality on s390x only. But this has not been seriously tested, either.
So, can you be more specific about what your end goal is? I.e. ceph as server, or ceph as client? If the latter, what type(s) of client functionality do you intend to use?
We are currently building whole ceph code (https://github.com/ceph/ceph/tree/v12.2.4) on s390x platform. This will include all functionality.
We could build ceph source on Ubuntu 16.04 however while setting up functional test cluster, command
"../src/vstart.sh -d -n -x -l_" fails with an error:
/ceph/build/bin/ceph -c /ceph/build/ceph.conf -k /ceph/build/keyring -i /ceph/build/dev/mgr.x/keyring auth add mgr.x mon allow profile mgr mds allow * osd allow *
0 monclient(hunting): authenticate timed out after 300
Also, test failures are seen with make check or ctest -j$(nproc) command.
We are referring to guide: https://github.com/ceph/ceph/tree/v12.2.4
Does anyone have any idea about this?
Also available in: Atom
PDF