On Wed, Sep 21, 2011 at 8:39 PM, Atish Kathpal <atish.kathpal@xxxxxxxxx> wrote: > On Wed, Sep 21, 2011 at 8:05 PM, Wido den Hollander <wido@xxxxxxxxx> wrote: >> >> Hi, >> >> On Wed, 2011-09-21 at 18:30 +0530, Atish Kathpal wrote: >> > I am referring to the "rados" command line tool in my question. >> > >> > Regards >> > Atish >> > >> > On Wed, Sep 21, 2011 at 3:14 PM, Atish Kathpal <atish.kathpal@xxxxxxxxx> wrote: >> > > On Tue, Sep 20, 2011 at 2:20 PM, Wido den Hollander <wido@xxxxxxxxx> wrote: >> > >> >> > >> Hi, >> > >> >> > >> On Tue, 2011-09-20 at 13:14 +0530, Atish Kathpal wrote: >> > >> > Hello friends >> > >> > >> > >> > Since there is no Ceph User's mailing list, I am posting my doubt here. >> > >> > >> > >> > I want to use the Ceph object store capabilities. I have already >> > >> > installed and setup a Ceph cluster. >> > >> > >> > >> > As a first step, I want to be able to GET/PUT or read/write to the >> > >> > object store of my cluster. I would prefer a HTTP/REST interface but >> > >> > please let me know of other interfaces that exist for performing >> > >> > read/writes to ceph object store/RADOS. >> > >> >> > >> You mean the radosgw? See: http://ceph.newdream.net/wiki/RADOS_Gateway >> > >> >> > >> That should give you a nice HTTP interface to your RADOS objects. Almost >> > >> fully S3 compatible. >> > >> >> > >> There is also a command-line tool "rados" which you could use, but you >> > >> can also write something against librados (C/C++). >> > >> >> > > >> > > I tried using rados. But it does not seem to work. >> > > >> > > atish@atish-virtual-machine:/etc/ceph$ rados ls >> > > 2011-09-21 15:13:32.030505 b7795b50 monclient(hunting): >> > > MonClient::init(): Failed to create keyring >> >> Does the user atish have read access on the ceph.conf? And does it also >> have access to the keyring.bin file? >> >> I assume you have cephx enabled? >> >> Wido >> > > I have given write privileges now to ceph.conf and the ceph.keyriing > files. Getting a different error now:- > Hi *I meant read and write privileges. Infact given 777 privileges. Please guide. Regards Atish > atish@atish-virtual-machine:/etc/ceph$ sudo rados put object1 bitmapsppt4.bin > 2011-09-21 20:33:40.833509 b78d0b50 monclient(hunting): authenticate > timed out after 30 > 2011-09-21 20:33:40.834096 b78d0b50 librados: client.admin > authentication error Connection timed out > couldn't connect to cluster! error -110 > > In case it helps, I got the following output while setting up the > cluster using mkcephs (no errors here):- > > atish@atish-virtual-machine:/etc/ceph$ sudo mkcephfs -a -c ceph.conf > -k ceph.keyring > temp dir is /tmp/mkcephfs.zuS8L1yaTI > preparing monmap in /tmp/mkcephfs.zuS8L1yaTI/monmap > /usr/bin/monmaptool --create --clobber --add alpha 10.72.147.207:6789 > --print /tmp/mkcephfs.zuS8L1yaTI/monmap > /usr/bin/monmaptool: monmap file /tmp/mkcephfs.zuS8L1yaTI/monmap > /usr/bin/monmaptool: generated fsid 75fdccda-038b-70aa-ed47-04aaa539aedf > epoch 1 > fsid 75fdccda-038b-70aa-ed47-04aaa539aedf > last_changed 2011-09-21 20:32:47.522913 > created 2011-09-21 20:32:47.522913 > 0: 10.72.147.207:6789/0 mon.alpha > /usr/bin/monmaptool: writing epoch 1 to > /tmp/mkcephfs.zuS8L1yaTI/monmap (1 monitors) > === osd.0 === > ** WARNING: Ceph is still under development. Any feedback can be directed ** > ** at ceph-devel@xxxxxxxxxxxxxxx or http://ceph.newdream.net/. ** > 2011-09-21 20:32:49.740368 b77d26e0 created object store > /ceph_data/osd.0 journal /ceph_data/osd.0.journal for osd0 fsid > 75fdccda-038b-70aa-ed47-04aaa539aedf > creating private key for osd.0 keyring /etc/ceph/ceph.keyring > creating /etc/ceph/ceph.keyring > === mds.0 === > creating private key for mds.0 keyring /etc/ceph/ceph.keyring > creating /etc/ceph/ceph.keyring > Building generic osdmap > highest numbered osd in /tmp/mkcephfs.zuS8L1yaTI/conf is osd.0 > num osd = 1 > /usr/bin/osdmaptool: osdmap file '/tmp/mkcephfs.zuS8L1yaTI/osdmap' > /usr/bin/osdmaptool: writing epoch 1 to /tmp/mkcephfs.zuS8L1yaTI/osdmap > Generating admin key at /tmp/mkcephfs.zuS8L1yaTI/keyring.admin > creating /tmp/mkcephfs.zuS8L1yaTI/keyring.admin > Building initial monitor keyring > added entity mds.0 auth auth(auid = 18446744073709551615 > key=AQCa/HlO0AivCRAARY3sVWxwtiOUAupoBsc6yw== with 0 caps) > added entity osd.0 auth auth(auid = 18446744073709551615 > key=AQCZ/HlOoKS4NBAAeVAKe/nSZJy2xPM4Z7BvIw== with 0 caps) > === mon.alpha === > ** WARNING: Ceph is still under development. Any feedback can be directed ** > ** at ceph-devel@xxxxxxxxxxxxxxx or http://ceph.newdream.net/. ** > /usr/bin/cmon: created monfs at /ceph_data/mon.alpha for mon.alpha > placing client.admin keyring in ceph.keyring > > -Atish > >> > > >> > > Any fixes? >> > > >> > > Thanks >> > > Atish >> > > >> > > >> > > >> > >> > >> > >> > Final goal: Besides normal read/writes, I also want to be able to have >> > >> > some objects, which point to no data. That is, I want to have a >> > >> > special flag, which if set, would mean there is no data pointed to by >> > >> > this Object ID. If its unset, it means its like a normal object >> > >> > pointing to some data file(s). I want to have the freedom to be able >> > >> > to set/unset this flag and hence be able to delete/re-insert the >> > >> > corresponding data file(s) against the same object ID. Do we have an >> > >> > API which could allow me such functionality? >> > >> >> > >> No, RADOS is a pretty straight forward API. You have pools where you >> > >> place objects in. Objects can have xattrs and that's about it. >> > >> >> > >> If you want these kinds of logic you'd have to write your own layer over >> > >> librados. >> > >> >> > >> You could set xattr telling a object is empty. >> > >> >> > >> RADOS is pretty low-level and straight forward. There is not much logic >> > >> in it, no locking or other fancy stuff. Just store objects in pools and >> > >> make sure they are safe. >> > >> >> > >> Any other logic should be done by yourself. >> > >> >> > >> Wido >> > >> >> > >> > >> > >> > Please point me to suitable links/starting points. >> > >> > >> > >> > Thanks >> > >> > Atish >> > >> > -- >> > >> > 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 >> > >> >> > >> >> > > >> >> > -- 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
