On Tue, 10 Jul 2012, Gregory Farnum wrote: > On Tue, Jul 10, 2012 at 4:25 PM, Sage Weil <sage@xxxxxxxxxxx> wrote: > > On Wed, 11 Jul 2012, Sz?kelyi Szabolcs wrote: > >> > >> The problem is that the mount.ceph command doesn't understand keyrings; > >> > >> it > >> > >> only understands secret= and secretfile=. There is a longstanding > >> > >> feature > >> > >> bug open for this > >> > >> > >> > >> http://tracker.newdream.net/issues/266 > >> > >> > >> > >> but it hasn't been prioritized. Sorry for the confusion! It will happen > >> > >> soon. > >> > >> > >> > >> In the meantime, you need > >> > >> > >> > >> -o secretfile=/path/to/secretfile,name=access_fs > >> > > > >> > > Is this also true for the FUSE client? I have obscure memories about big > >> > > differences between the kernel and the FUSE client, for example the latter > >> > > being able to read ceph.conf, and get the necessary info, including the > >> > > keyring file, from there. Maybe I didn't emphasize it, but that's what I'm > >> > > using. > >> > > >> > When using ceph-fuse, you want to specify the name with > >> > --name=access_fs ? no -o required. > >> > >> Okay, so I don't need the "client." prefix for the key name, but how can I > >> specify the --name= option in fstab? Or is it possible to specify it in > >> ceph.conf, so it can be read by ceph-fuse when called by mount? > > > > Er sorry, you actually want either --id foo or --name client.foo (they are > > equivalent) when dealing with ceph-fuse (or other userland daemons/tools). > > Nope ? I checked this locally before sending it out. --name foo worked > out fine. Although I certainly can't keep straight when we require the > type prefix versus when it's added for us. *sigh* Oh, I bet the code tries to be friendly and will behave without the 'client.' if you leave it off... but we shouldn't advertise that. Everyone, forget what you just heard! :) sage > > > > I'm not sure what the best way of putting fuse-based file systems in fstab > > is, though. One way or another, though, ceph-fuse needs to be told on the > > command line who to authenticate as (and which sections of ceph.conf to > > pay attention to). > > This is my concern, too. I don't think you can specify default IDs for > ceph-fuse right now. :/ > > > > > sage > > -- > > 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 > >
