Hi. Jay brought up the state of Ceph's Python bindings in a conversation, and I wanted to share this reasoning with the whole list. Note, I'm talking about debs, rpm etc case is similar but separate. - The python bindings we have are not currently pip-installable. - We could make them pip-installable. The easiest way to that would be to split them out to a separate source package. This is not as useful as it seems, as they'll require the underlying librados / librbd / librgw etc libraries to be available. And if we find ctypes insufficient for the bindings, then "pip install" will start needing the -dev packages also installed. - If you can't just take a base OS and do "pip install rbd", but need to install the Ceph library packages, you might as well get the python modules from the "python-ceph" package at the same time. - We want to use the Python bindings internally, to test Ceph, as part of automated tests. Splitting them out to separate source is in conflict with this desire. For Debian-based systems, here's how to get usable Python libraries for Ceph: 1. Follow the installation guide at http://ceph.newdream.net/docs/latest/ops/install/mkcephfs/ 2. Run "sudo apt-get install python-ceph" You can quickly check that they work with python -c 'import rbd' API docs, as much as they exist currently, are at http://ceph.newdream.net/docs/latest/api/librbdpy/ and more will come as siblings of that document later. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
