FWIW, an easily buildable libcrush would be fantastic for simulation
purposes (and things like avalanche analysis!) as well.
Mark
On 05/08/2015 12:40 PM, James (Fei) Liu-SSI wrote:
Hi Yuan,
Very interesting. Would be possible to know why application needs to access
the cursh map directly instead of accessing through ceph tool?
Regards,
James
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Zhou, Yuan
Sent: Thursday, May 07, 2015 6:29 PM
To: Ceph Development
Cc: Cohen, David E; Yu, Zhidong
Subject: libcrush.so
Ceph use crush algorithm to provide the mapping of objects to OSD servers. This
is great for clients so they could talk to with these OSDs directly. However
there are some scenarios where the application needs to access the crush map,
for load-balancing as an example.
Currently Ceph doesn't provides any API to render the layout. If your
application needs to access the crush map you'll going to rely on the command
'ceph osd map pool_name obj_name'. With this libcrush.so we could let the
application to choose which nodes to access. The other advantage is we could
provide some other bindings(python, go) based on this also.
From the git log we find libcrush was there before but removed out since
Argonaut. Can anyone kindly share us the background of this change?
Thanks, -yuan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the
body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
