On Wed, 8 Jan 2014 10:46:42 +0900 Christian Balzer wrote: > Hello, > > On Tue, 7 Jan 2014 08:35:44 -0500 Alfredo Deza wrote: > > > On Tue, Jan 7, 2014 at 7:47 AM, Joao Eduardo Luis > > <joao.luis@xxxxxxxxxxx> wrote: > > > On 01/07/2014 05:14 AM, Christian Balzer wrote: > > >> > [snip] > > >> So I grabbed the latest ceph-deploy, > > >> ceph-deploy_1.3.4-1~bpo70+1_all.deb, and tried that, but as I feared > > >> from its name this is expecting nothing newer than Wheezy: > > >> --- > > >> [ceph_deploy.cli][INFO ] Invoked (1.3.4): /usr/bin/ceph-deploy mon > > >> create irt03 > > >> [ceph_deploy.mon][DEBUG ] Deploying mon, cluster ceph hosts irt03 > > >> [ceph_deploy.mon][DEBUG ] detecting platform for host irt03 ... > > >> [irt03][DEBUG ] connected to host: irt03 > > >> [irt03][DEBUG ] detect platform information from remote host > > >> [ceph_deploy][ERROR ] UnsupportedPlatform: Platform is not > > >> supported: debian jessie/sid > > >> --- > > > > > > The problem here is that you are using a hybrid version of Debian. Is > > it sid? or is it jessie? > > > It is what it is. > As in, sid (unstable) and testing are named jessie/sid > in /etc/debian_version, including a notebook of mine that has been > "sid" (as in /etc/apt/sources.list) for 10 years. > This naming convention (next_release/sid) has been in place for at least > 2 generations, probably longer. > > > ceph-deploy needs to know what version, release, and codename is > > dealing with *exactly* because > > it will take decisions based on that information. If your host is just > > "sid" I think it should work since the > > repo does list it: http://ceph.com/debian/dists/ > > > This may well be, but is doomed to failure, because even if I were to > manually edit the version to sid, a future update will eventually revert > that change again. > The real solution is for ceph-deploy to parse the version correctly, if > it indeed is supposed to support unstable and testing. > To clarify this, I changed the version to "sid" which didn't work. Changing it to "7.2" (Wheezy) gets it past that check and the mon installed and running. However I'm fully expecting it to fail in subtle ways at some later point. So I guess this means exactly what I suspected, no supported way by native Debian distro tools (aka mkcephfs) or the inktank ceph-deploy to create ceph clusters in Debian sid (testing is still at Argonaut I think). Hopefully James Page will pipe up at some point. ^.^ Regards, Christian -- Christian Balzer Network/Systems Engineer chibi@xxxxxxx Global OnLine Japan/Fusion Communications http://www.gol.com/ _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |